SEPA Transfer Rejected by a Crypto Exchange: Causes and Fixes

Reviewed on August 21, 2026. Fees, product availability, tax and regulatory rules can change. Verify live platform screens and official sources before acting.

Short answer: if a euro transfer to a crypto platform came back to your bank account, the money is safe and the cause is almost always one of six things: a name that did not match, a joint or third-party account, a missing reference, a payment routed as SWIFT instead of SEPA, an account that is not verified or not eligible, or a compliance decision. Your bank's return reason code tells you which — and it is the fastest diagnostic available to you.

A returned transfer and a missing transfer feel identical for the first day and then diverge completely. If the money is back in your account, stop looking for it and start reading the return message. If it is not back and not credited, you have a different problem, and SEPA deposit pending is the guide you want instead.

First: confirm it was actually returned

Before diagnosing anything, establish which of three states you are in.

The windows worth measuring against: instant transfers settle in seconds, standard SEPA takes up to the next business day or three, and a platform's stated ceiling (24 hours for instant, up to three business days for standard, on Binance) covers its own review on top. A rejection normally surfaces within a few business days — under the SEPA rulebook, the beneficiary's bank returns a credit transfer within a short fixed window, commonly up to five banking business days.

Read the return reason code

This is the step most people skip, and it is the one that saves the afternoon. When a euro transfer is returned, the message carries a standard ISO 20022 reason code. It is usually visible in your banking app's transaction detail, and always available from your bank on request.

That last row matters more than its obscurity suggests. SL01 and similar sender-side rejections mean your bank refused, not the exchange. No amount of arguing with platform support will fix it, and the fix is a different conversation entirely — see when your bank blocks a crypto transfer.

The six causes, in order of likelihood

1. The name did not match

The bank account holder must be the same verified person as the platform account holder. Not a spouse, not a parent, not "the same household". This rule is universal across European crypto platforms and is enforced automatically.

Since 9 October 2025, euro-area banks also run Verification of Payee on outgoing transfers under the EU Instant Payments Regulation: your bank compares the beneficiary name you typed against the name registered to that IBAN and warns you before you confirm. If you clicked through such a warning, that is very likely your answer.

Fix: re-send from an account in exactly your verified name. If your legal name has changed, update your platform verification first — a mismatch you create by marriage or a spelling variant is still a mismatch.

2. Joint account

Most platforms, Binance explicitly, refuse SEPA transfers from joint accounts even when you are one of the named holders. There is no appeal and no exception.

Fix: use a personal account in your sole name.

3. Missing or wrong reference code

Where the deposit screen shows a reference or payment ID, it is the only thing linking your money to your account. A transfer without it cannot be matched. Depending on the platform, the money is either returned after a delay or held pending a manual claim.

Fix: re-send with the reference pasted exactly as displayed — and read the screen fresh each time rather than reusing a saved template.

4. Routed as SWIFT instead of SEPA

A euro payment sent as an international SWIFT transfer does not travel the SEPA channel and cannot be processed as a SEPA deposit. Some banking apps make this choice for you, especially for a beneficiary they classify as international.

Fix: ask explicitly for a SEPA credit transfer in EUR. If your app offers both, choose SEPA before confirming.

5. Account not verified or not eligible

An unverified account cannot receive euro transfers. Neither can an account under an entity that does not offer euro rails to your country — which is why the deposit option is missing from the menu in the first place. Binance's SEPA channel, for example, covers 36 SEPA countries but excludes the Netherlands entirely.

Fix: finish verification (KYC rejected: causes and fixes if that is where you are stuck), or use a platform whose euro rails cover your country. The OKX walkthrough is in the OKX SEPA guide.

6. A compliance decision

Sometimes the transfer is refused because a review concluded it should be, and no detailed reason will be given. This is frustrating and it is also normal in regulated finance.

Fix: open a support ticket with the payment reference, provide what is asked for, and do not re-send the same transfer repeatedly in the meantime. Repeated identical attempts after a refusal make the file look worse, not better.

The one case where the money does not come back

Binance does not credit and does not refund SEPA transfers below 2 EUR. A 1 EUR test transfer is not returned; it is simply gone. This is the single mistake in this entire subject that costs real money, and it happens precisely to the careful people who send a small test first.

If you test, test with at least the platform's stated minimum. Never below it.

What to do, in order

1. Confirm the money is back. If it is not, you have a pending deposit, not a rejection.
2. Read the return reason code in your banking app, or ask your bank for it.
3. Decide which side refused. A sender-side code means your bank; anything else points at the platform or the details you entered.
4. Fix the specific cause — do not change five things at once, or you will not know what worked.
5. Re-send once, from a personal account in your verified name, with the reference copied fresh from the deposit screen.
6. If it is refused again with no clear reason, open a ticket with the payment reference and the return code. That code is what support needs and what most users never provide.

FAQ

How long does a rejected SEPA transfer take to come back? Usually a few business days. Under the SEPA rulebook the beneficiary's bank returns a credit transfer within a short fixed window, commonly up to five banking business days, after which your own bank credits you.

Do I lose the fee on a returned transfer? Your bank generally does not charge for a return on a standard euro transfer, but practice varies. A platform fee is not charged on a deposit that was never credited.

My transfer was returned twice for no stated reason. What now? Stop re-sending. Two unexplained rejections almost always mean a decision on one side that a third attempt will not change. Open a support ticket with the payment reference and the return code, and ask which side refused.

Can I just use a friend's bank account? No — and it is worth being blunt: that is the exact pattern anti-money-laundering rules exist to catch. It will be refused, and repeated attempts can get your platform account reviewed or frozen.

The money came back but my platform account is now restricted. Those are separate events that sometimes share a cause. Work through the platform's verification flow first; securing your crypto account covers what to have ready.

Affiliate disclosure: this article contains referral links. If you sign up on OKX (code OK6669) through our links, you get a 20% discount on trading fees and this site earns an affiliate commission, at no extra cost to you.

Risk warning: cryptocurrencies are volatile, high-risk assets; you may lose your entire capital. This content is educational and informational only and is not financial, legal or tax advice. Do your own research before trading.

Regional notice: this site is aimed at French-speaking markets (Europe and francophone Africa). It is not directed at residents of mainland China, the United States, the United Kingdom or Canada. Check and comply with the regulations in force in your country.