Why Banks Return Crypto Settlements, and How to Stop It Happening

A returned settlement is not a rejection of you. It is usually a field mismatch, a policy flag, or a missing piece of context that a human would have resolved in thirty seconds if anyone had asked them. Here are the causes in order of how often they actually occur. The reference implementation, for want of a better term, is a crypto to fiat exchange.

Name mismatch

The single most common cause. The name on the receiving account does not exactly match the name registered at the crypto platform.

This catches companies constantly, because the trading name and the registered name differ. The bank account is in the registered name. The platform account was opened under the trading name. The payment arrives for a beneficiary the bank cannot match and it is returned.

Fix: register the exact legal name, character for character including the legal form suffix, at the platform. Not the trading name, not an abbreviation.

Missing or wrong reference

Some banks require a structured reference for inbound payments above a threshold, particularly for business accounts with reconciliation rules configured. A payment arriving without it goes to a suspense account and may be returned after a holding period.

Fix: ask the bank whether a reference format is required and configure it at the platform side if the platform allows a fixed reference.

Correspondent bank policy on the SWIFT path

For non-SEPA payments, the money passes through correspondent banks. Any of them can decline. You will usually not be told which one or why, only that the payment was returned and a fee was deducted.

This is the most frustrating category because it is invisible and not under your control. It is also the most avoidable: use a rail that does not involve correspondents. SEPA within Europe, a domestic rail elsewhere. Where client money is involved the requirements change entirely, which is what a platform set up for client account handling is built to satisfy.

Fix: settle in a currency and country where the platform has a direct or domestic connection. If that means opening a euro account for European settlements, open one.

Inbound crypto policy at the receiving bank

Some banks decline inbound payments from crypto asset service providers as policy, regardless of amount or documentation. They will not always tell you this is the policy, and front-line staff frequently do not know it exists.

Fix: establish this in writing before the first settlement, at relationship manager level rather than through a branch or a call centre. If the answer is no, the solution is a second banking relationship with an institution that has an explicit crypto policy, not an argument with the first one.

Amount inconsistent with the account profile

An account that normally sees ten thousand a month receiving four hundred thousand triggers a review irrespective of source. This is not crypto-specific and applies equally to any large inbound payment.

Fix: tell the bank in advance. A short email stating that a payment of a stated size is expected on a stated date from a stated source removes the entire problem. Banks rarely refuse something they were warned about.

Source of funds not evidenced

The bank asks where the crypto came from and the answer is not documented. For a business this means: which client paid, under which contract, for what.

Fix: keep the chain of documents. Client invoice, the crypto payment received against it, the conversion record, the settlement. Four documents, filed together, answer every question that will be asked.

What good looks like

A company that has done this properly has: the exact legal name at both ends, a euro account for euro settlements, a written confirmation from the bank that inbound crypto settlements are acceptable, a habit of pre-notifying large amounts, and a document set filed per conversion.

Setting that up takes an afternoon. Not setting it up costs a frozen payment at the worst possible time.

Working with a regulated crypto to fiat gateway helps on the other side of this, because the bank’s first question is which provider sent the money and whether it is licensed. A recognisable licensed counterparty shortens that conversation considerably.