Bank Transfers to an Exchange: Why They Get Held or Bounced Back

One transfer, two ledgers

A fiat deposit into an exchange is two independent events that the user experiences as one. The first is the bank’s payment: it either settles at the named beneficiary or it does not. The second is the exchange’s decision to credit an account: it either matches the incoming payment to a verified customer or it does not.

Almost every “my deposit didn’t arrive” case is a mismatch between those two ledgers, and the mismatch has a short list of causes. Binance documents the first three as rules, which makes them checkable before sending rather than after.

Cause one: the name does not match

This is the most common and the least negotiable. Binance’s SEPA guidance states it in one line:

“Your bank account name must match the name registered to your Binance account.”

The Latin America transfer guidance is more specific, and adds a second identifier:

“The account holder’s name and taxpayer number must match the name you used for identity verification in Binance.”

“Binance does not authorize payments with bank details that belong to third parties.”

That second sentence is a policy, not a preference. It exists because a payment from a third party is indistinguishable, at the receiving end, from a payment made to obscure who is funding the account — which is precisely what anti-money-laundering rules require venues to notice. A spouse’s account, a business account, a joint account and a friend paying on your behalf all produce the same problem: the money arrives from a name the exchange cannot match.

The consequence is not a fine. It is a return, and returns are slow.

Cause two: the wrong rail

The second cause is mechanical and entirely avoidable: sending through a network the venue does not accept for that currency.

The SEPA page is explicit about both halves of this:

“SWIFT transfers are not supported.”

“Any funds sent via SWIFT will be rejected and returned to the sender within 2 weeks.”

This is worth reading twice, because the mistake is understandable. SWIFT is the international standard; SEPA is the euro-area scheme. A euro transfer from outside the euro area will naturally be sent by SWIFT — and it will be rejected, held for up to two weeks, and returned. The same page directs deposits to “Bank Transfer (SEPA Instant)”.

The general lesson generalises to every corridor: the accepted rail is a property of the currency and the venue’s local partner, not of your bank’s convenience. The deposit screen names the rail; the transfer must use exactly that rail.

Cause three: the reference is missing or wrong

Many fiat rails carry a reference field, and venues use it to attribute an incoming payment to an account. When it is blank, the payment arrives with no way to route it, and someone has to match it manually — by amount, by name and by date — which is where a deposit becomes a support ticket.

This is the same class of mistake as a missing memo on a crypto deposit, which is covered in deposit memos and destination tags. The difference is that a crypto transfer without a memo is settled and stranded, while a fiat transfer without a reference may be returned by the receiving bank before it is ever credited.

Cause four: review

The fourth cause is different in kind. The deposit has arrived, the rail was right, the name was right — and the funds are not spendable because the venue is reviewing something.

What that review looks at is not published in detail, and it is worth being precise about the limit of what can be claimed. What is published is the route that exists when a deposit has not been credited: Binance’s fiat deposit appeal process. The page is titled “How to Submit a ‘Fiat Deposit Not Arrived Appeal’?” and asks for the deposit details, the bank details and the payment certificate.

That list is the practical takeaway. The payment certificate is the document you will not have if you did not keep it. A bank transfer receipt with the sender’s name, the beneficiary, the amount, the date, the rail and the reference is the evidence that resolves most of these cases, and it lives in the banking app for a shorter time than people assume.

What a return actually costs

A returned transfer is often described as if the money simply comes back. The arithmetic is worse than that.

Fees at both ends. The sending bank charges for the transfer whether or not it settles. An intermediary bank may deduct a correspondent fee. The receiving bank may charge for the return. None of these are refunded by the exchange, because the exchange never held the money.

Currency round trips. A transfer that left in one currency and returns in another pays the spread twice. On a small transfer, the spread can exceed the fee.

Time. Two weeks is the published outer bound for one specific case — SWIFT funds sent to a SEPA account. A normal return may be faster; a correspondent-bank chain may not be.

Opportunity. The rate at which the funds are finally credited is the rate of the second attempt, not the first. In a moving market, a two-week return is a two-week unhedged position in cash.

The sequence that avoids all of it

1. Read the deposit screen’s rail and use exactly that rail. SEPA Instant is not SWIFT; a local scheme is not a wire.
2. Send from an account in your own verified name, with the same identity details the exchange holds.
3. Copy the reference field from the deposit screen rather than reconstructing it.
4. Send a small first transfer, then the rest once it is credited. The same logic as a first self-custody transfer, for the same reason.
5. Save the payment certificate before closing the banking app.
6. Wait for the stated window before filing, then file with the certificate attached rather than describing the transfer from memory.

What is not a solution

Two workarounds appear constantly in forums and both make the situation worse.

Using someone else’s bank account to get around a local restriction, a name mismatch or a banking limit. Binance’s rule is explicit that it does not authorize payments with third-party bank details, so the transfer is likely to be returned — and if it is reviewed instead, the review now concerns the funding source as well as the deposit.

Re-sending while the first transfer is unresolved. Two identical transfers in flight produce two matching problems, and if both eventually credit, one of them looks like a duplicate that has to be reversed. The published process assumes one transfer and one appeal.

The cost side of the same deposit — what the exchange charges, and what the spread costs on the conversion — is in on-ramp fees versus spread. The other clock, the one that runs when the money has arrived but cannot yet be moved out again, is covered in Binance withdrawals: whitelists, network suspensions and the wait.

Risk note. Every rule quoted in this article comes from Binance’s own support pages — the SEPA deposit guide, the Latin America transfer limits page and the fiat deposit appeal page — all read on 2026-10-31. Accepted rails, name-matching requirements and timeframes differ by currency, country and payment partner, and change; the binding description is the one on the deposit screen at the time of sending. Nothing here is a way around an identity requirement, a regional restriction or a review.