SEPA (Single Euro Payments Area) is the euro-denominated payment scheme that replaced Europe’s patchwork of domestic bank transfer systems with a single standard. Any business accepting payments from customers in Germany, France, the Netherlands, or 38 other countries can collect funds using one API, one IBAN format, and one set of rules, rather than integrating separately with each country’s legacy infrastructure.
This article covers what SEPA is, how its two main instruments work, what developers need to know about SCA and the Instant Payments Regulation, and how accepting SEPA fits into a broader payment acceptance strategy for European markets.
What is SEPA?
SEPA is a payment integration area created by the European Union and the European Payments Council (EPC) to make euro-denominated transfers work the same way across member countries. Before SEPA, a payment from a Dutch bank account to a Spanish supplier used a different transfer system than a domestic Dutch transfer. SEPA replaced those country-specific rails with two interoperable instruments: SEPA Credit Transfer (SCT) and SEPA Direct Debit (SDD).
The scheme covers 41 countries as of the ECB’s most recent published status (22 May 2025):
- The 27 EU member states
- The UK
- Four EFTA members: Iceland, Liechtenstein, Norway, Switzerland
- Four microstates: Andorra, Monaco, San Marino, Vatican City
- Five EU-accession countries added to SEPA’s scope by EPC Board decision in November 2024: Albania, Montenegro, Moldova, North Macedonia, Serbia
Most published guides still cite “36 countries,” a figure that predates the 2024 accession-country addition (European Central Bank, “Single Euro Payments Area (SEPA),” status 22 May 2025, https://www.ecb.europa.eu/paym/integration/retail/sepa/html/index.en.html).
Scale: euro-area non-cash payments reached 77.7 billion transactions worth €116.0 trillion in H1 2025, up 7.7% in volume year-on-year (ECB, “Payments statistics: first half of 2025,” https://www.ecb.europa.eu/press/stats/paysec/html/ecb.pis2025h1~36edd636c8.en.html).
SEPA Direct Debit vs. SEPA Credit Transfer
The two instruments handle different payment directions.
| SEPA Credit Transfer (SCT) | SEPA Direct Debit (SDD) | |
|---|---|---|
| Who initiates | Payer (customer or business) | Payee (merchant or platform) |
| Direction | Push: sender moves funds | Pull: collector pulls funds |
| Requires mandate | No | Yes, signed before first collection |
| Settlement | 1 business day (standard), seconds (instant) | Longer cycle with pre-notification window |
| Common use | Supplier payments, B2B transfers, customer refunds | Subscriptions, recurring billing, SaaS |
| Refund window | Not applicable | 8 weeks (authorized), 13 months (disputed as unauthorized) |
For a platform building subscription billing in Europe, SDD is the relevant instrument. For payouts, B2B settlements, or one-time bank transfers, SCT handles it.
How a SEPA payment works: mandates, IBANs, and settlement
SEPA Credit Transfer flow
- Payer provides their IBAN (and BIC for cross-border transfers, though BIC is no longer required for intra-SEPA transfers since 2016).
- Payer’s bank submits the transfer through the SEPA clearing and settlement mechanism (operated by the EBA CLEARING or other scheme-compliant operators).
- Funds arrive in the payee’s account within one business day for standard SCT, or within seconds for SEPA Instant Credit Transfer where both banks support it.
SEPA Direct Debit flow
- The payer signs a mandate, a legal authorization giving the merchant the right to pull funds from their account. Mandate data includes the payer’s IBAN, the merchant’s creditor ID, and a unique mandate reference.
- Before each collection, the merchant sends the payer a pre-notification (typically 14 days in advance under the Core scheme, though shorter periods can be agreed).
- The merchant submits the collection to their bank, which routes it through SEPA clearing.
- Funds are debited from the payer’s account and credited to the merchant on the agreed settlement date.
Mandate lifecycle matters for your data model. A mandate must be stored and referenced on each subsequent collection. If no collection is presented against a mandate for 36 months, it becomes invalid and a new one must be obtained (European Payments Council SDD rulebook, as summarized by Twikey, “SEPA mandates,” https://www.twikey.com/guides/sepa-direct-debit-mandates.html). Building a SEPA integration without tracking mandate state (active, expired, revoked) will produce collection failures that are hard to diagnose.
Which countries and currencies SEPA covers
SEPA applies to euro-denominated transfers. All 41 member countries can send and receive SEPA payments in euros. For countries whose domestic currency is not the euro (the UK, Switzerland, Sweden, etc.), SEPA applies to euro-denominated transactions only, not to transfers in GBP, CHF, or SEK.
Practical implication: a UK business paying a German supplier in euros can use a SEPA Credit Transfer. The same UK business paying a German supplier in GBP cannot.
SEPA Instant Credit Transfer and the Instant Payments Regulation
SEPA Instant Credit Transfer (SCT Inst) is a variant of the standard credit transfer that settles in seconds, 24 hours a day, 7 days a week, across participating banks. Adoption has accelerated:
Instant credit transfers made up 23% of the number and 7% of the value of all credit transfer transactions in euro-area retail payment systems in H1 2025, up from roughly 15% of total credit transfers in 2023 (ECB, “Payments statistics: first half of 2025”; Celent/ClearBank/Plaid, “SEPA Instant adoption in Europe,” 2026, https://clear.bank/learn/report/sepa-instant-adoption-in-europe).
The EU accelerated this through the Instant Payments Regulation (Regulation (EU) 2024/886), which requires payment service providers in the euro area to receive SEPA Instant Credit Transfers by 9 January 2025 and send them by 9 October 2025 (ECB, “Instant Payments Regulation (IPR),” https://www.ecb.europa.eu/paym/retail/instant_payments/html/instant_payments_regulation.en.html). This makes instant settlement a baseline expectation for euro-area PSPs, not an optional premium feature.
For developers building settlement logic: if your PSP supports SCT Inst and the payer’s bank does too, you get seconds-level settlement instead of next-day. But if either bank does not support the instant scheme, the transfer falls back to standard SCT. Your reconciliation logic needs to handle both settlement timings on the same instrument.
PSD2, SCA, and SEPA: what developers need to know
This is where SEPA diverges from card payment integration in ways that matter to how you build.
SEPA Credit Transfer: SCT is a push payment; the payer initiates it. PSD2 Strong Customer Authentication applies when the payer authenticates with their bank to authorize the transfer. You do not build an SCA challenge flow on your side; the payer’s bank handles it.
SEPA Direct Debit: SDD is payee-initiated, which puts it outside PSD2 SCA scope at the point of each individual collection. Each recurring debit does not require a 3DS challenge. At mandate setup: if the payer’s PSP is involved in the mandate creation step (as with some e-mandate flows), SCA may apply there. If the mandate is signed via a paper form or a simple online form not touching the payer’s banking session, SCA does not apply (European Banking Authority Single Rulebook Q&A 2018_4359, https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2018_4359).
The practical difference: card subscription billing requires SCA on initial authorization and may require it again on the recurring charge depending on how it is flagged. SEPA Direct Debit subscriptions do not require SCA on each collection. For a platform building European subscription billing, SDD avoids the ongoing SCA overhead that card-based recurring billing carries.
Refund and chargeback mechanics
SEPA vs. cards and other local payment methods
A card is always an option for European customers, but SEPA Direct Debit has structural advantages for specific use cases.
| SEPA Direct Debit | Card | |
|---|---|---|
| Authorization rate | High; bank accounts don’t expire | Cards expire; numbers change; issuer declines vary |
| SCA overhead per recurring charge | None | Variable; depends on exemptions applied |
| Refund risk | 8-week no-fault refund window | Chargeback timelines vary by scheme |
| Customer reach | Anyone with a SEPA-zone bank account | Requires a card; some demographics underrepresented |
| Integration complexity | Mandate management required | Token/subscription handling required |
SEPA Direct Debit processes over 21 billion transactions per year across the SEPA zone (European Payments Council, “SEPA Direct Debit,” https://www.europeanpaymentscouncil.eu/what-we-do/sepa-direct-debit), which suggests the infrastructure behind it is well-tested at scale.
For SEPA versus other European local payment methods: iDEAL (Netherlands), Bancontact (Belgium), and others address different markets and different use cases. They are not substitutes for SEPA; they are different rails. A platform accepting payments across Europe needs SEPA and is likely to need at least one or two of the country-specific APMs alongside it, and each can be a separate bespoke integration or all can route through a common abstraction layer. See the infrastructure cost of adding market-specific payment methods for more on that tradeoff.
Accepting SEPA through a payment orchestration platform
Connecting to SEPA directly requires scheme membership and mandate management infrastructure that most platforms do not have and do not want. The practical integration path is through a bank, PSP, or orchestration platform that already holds SEPA scheme membership and has built the mandate lifecycle tooling.
The same PSP integration problem that applies to cards applies here. Integrate SEPA directly with one PSP and you are tightly coupled to:
- That PSP’s API
- Their error codes
- Their webhook format
- Their mandate data model
When a PSP goes down, SEPA collections stop. When you want to add a second SEPA-capable PSP for redundancy or cost reasons, you are writing a second integration.
An orchestration layer sits between your code and the PSPs. Your backend sends transactions in a normalized format; the orchestration platform routes to the appropriate PSP, handles SEPA-specific requirements per provider, and returns consistent responses. If a PSP is unavailable, routing can fall over to another that supports SEPA without your code changing. New PSP or payment-method connections are added without you writing new integration code.
This is the same framing that applies to cards, wallets, and other APMs; the maintenance problem for SEPA is not meaningfully different. The complexity of maintaining multiple PSP integrations compounds as you add rails. A platform that needs cards, SEPA Direct Debit, iDEAL, and Bancontact is maintaining four separate integration surfaces if each is bespoke.
Orchestra’s global payment acceptance infrastructure routes transactions across PSPs in its network, including those with SEPA scheme membership. PSD2/SCA support for European markets is part of the platform’s compliance coverage. New payment-method connections are added at no additional cost.
For questions about cross-border settlement and currency handling in a SEPA context, see the cross-border payment FAQs.
Frequently asked questions
What is a SEPA payment?
SEPA (Single Euro Payments Area) is a euro-denominated payment scheme that lets banks and payment providers move money across 41 European countries using one IBAN-based standard, instead of separate domestic transfer systems per country.
What is the difference between SEPA Direct Debit and SEPA Credit Transfer?
SEPA Credit Transfer is a push payment: the customer or business initiates and sends funds. SEPA Direct Debit is a pull payment: the merchant collects funds from a customer’s account under a signed mandate, common for subscriptions and recurring billing.
Which countries does SEPA cover?
41 countries as of the ECB’s most recent published status (22 May 2025): the 27 EU member states, the UK, four EFTA members (Iceland, Liechtenstein, Norway, Switzerland), four microstates (Andorra, Monaco, San Marino, Vatican City), and five EU-accession countries added to SEPA’s scope in November 2024 (Albania, Montenegro, Moldova, North Macedonia, Serbia). The commonly cited “36 countries” figure predates that addition.
Is a SEPA payment the same as an IBAN payment?
No. An IBAN is the account identifier a SEPA payment uses to route funds; SEPA is the payment scheme itself. Any transfer using an IBAN within the SEPA zone can be processed as a SEPA payment, but IBAN is the address, not the payment method.
Does SEPA require Strong Customer Authentication?
SEPA Direct Debit collections are payee-initiated, so PSD2 SCA does not apply at the point of each individual collection. Mandate setup may require SCA if the payer’s own bank or PSP is involved in that step.
How long does a SEPA payment take to settle?
SEPA Credit Transfer settles within one business day. SEPA Instant Credit Transfer settles in seconds, 24/7, where both the sending and receiving banks support it. SEPA Direct Debit collections run on a longer cycle to allow for the mandate pre-notification window.
Can a customer reverse a SEPA Direct Debit payment?
Yes. Under the SEPA Direct Debit Core scheme, a customer can request a no-questions-asked refund within 8 weeks of the debit date, and up to 13 months if the collection is disputed as unauthorized.
How do I add SEPA to an existing checkout?
SEPA is integrated through a bank, PSP, or orchestration platform that already holds SEPA scheme membership and mandate-management infrastructure, rather than connecting to the SEPA clearing and settlement mechanism directly.
