Why Did My Bank Send It as SWIFT?
A transaction can fall back to SWIFT for various reasons even when it could be made as SEPA. This guide explains the possible reasons and how to prevent it.
Published:
Updated:
Quick answer
The wrong screen, the currency, reachability or a non-SEPA recipient can push the transaction to SWIFT.
A transaction that falls back to SWIFT is usually more expensive (intermediary bank charge) and slower (1–5 days). Understanding the reason helps you move the next transfer onto a cheaper SEPA route.
You usually notice that a transfer was sent as SWIFT rather than SEPA only afterwards — because of an intermediary bank charge or a longer time. So why does a transaction fall back to SWIFT when it could be made as SEPA? In this guide we explain the possible reasons and how you can prevent it.
Possible reasons
- The wrong transfer screen: If you selected the "international transfer" screen, the bank may process the transaction as SWIFT. The correct screen is usually "SEPA" or "intra-Europe euro transfer".
- The currency is not euro: SEPA only carries euros; if the transaction was started in a non-euro currency, SWIFT comes into play.
- The recipient country is outside SEPA: If the recipient IBAN belongs to a non-SEPA country (for example, Turkey), the transaction cannot be SEPA anyway.
- The recipient bank is not reachable: If the recipient bank has not joined the relevant SEPA scheme, the sending bank may turn to SWIFT.
- The bank's default policy: Some banks use SWIFT by default on certain corridors.
How do you prevent it?
- Choose the right screen. Use the SEPA/intra-Europe euro transfer option.
- Send in euros. Make sure the transaction is in euros.
- Check the recipient country. Confirm that the IBAN belongs to a SEPA country; see SEPA country lookup.
- Assess the signals. Check the transaction type with the SEPA or SWIFT detector.
- Ask your bank. If you are not sure, ask directly whether the SEPA option is offered.
Specific to Turkey
Because Turkey is outside SEPA, euro transfers between Turkey and Europe cannot be SEPA anyway and go via SWIFT. So in this corridor the answer to "why SWIFT?" is structural: Turkey is not yet within SEPA scope. For the current status, see the Turkey SEPA status page.
Summary
A transaction can fall back to SWIFT due to the wrong screen, a non-euro currency, a non-SEPA recipient, a reachability problem or the bank's default policy. SWIFT is usually more expensive and slower. Choosing the right screen and sending in euros to a SEPA country helps keep the transaction on a cheaper SEPA route.
Frequently asked questions
Why did my bank send it as SWIFT instead of SEPA?
There can be several reasons: the wrong transfer screen was selected, the bank uses SWIFT by default on that corridor, the recipient bank is not 'reachable' for SEPA, the euro currency was not selected, or the recipient country is outside SEPA.
What changes when it is sent by SWIFT?
On SWIFT, an intermediary (correspondent) bank charge can arise, the time lengthens (1–5 business days) and the OUR/SHA/BEN charge sharing affects the amount reaching the recipient. So it is usually more expensive and slower.
How do I make sure it is sent as SEPA?
Make sure the currency is euro, that the recipient IBAN belongs to a SEPA country, and that you selected the correct (SEPA/intra-Europe) transfer screen. If you are not sure, ask your bank about the SEPA option.
Sources
Confidence is graded from A (official document) to E (unverified).
SEPA scheme rulebooks & geographical scope
European Payments Council (EPC)
- Document date:
- 2025
- Last checked:
- 2026-07-16