SEPA Direct Debit: SEPA area (36 countries)'s direct debit
The pan-European direct debit scheme — the default rail for euro-denominated recurring collections.
How the SEPA Direct Debit flow works
SEPA Direct Debit (SDD) lets a merchant pull euro-denominated payments from a consumer or business bank account across the 36-country SEPA area under a signed mandate (SDD Core for consumers, SDD B2B for businesses).
The consumer provides IBAN and mandate authorisation at checkout or during onboarding. The merchant stores the mandate reference and can initiate collections against it.
Collections are batched and submitted to the merchant's bank, which routes them through SEPA clearing. Funds settle on the requested collection date (T+1 to T+several).
Under SDD Core the payer has an 8-week no-questions-asked refund right, and 13 months for unauthorised debits — which is the main operational risk vector.
Typical use cases
- Any euro-denominated recurring collection: SaaS, telco, utilities, insurance, media subscriptions, gyms, memberships.
- B2B recurring where SDD B2B (no consumer-style refund right) is available.
- One-off higher-ticket euro invoices where card interchange erodes margin.
Consumer reach
Every euro-area bank account holder is reachable — hundreds of millions of consumers and businesses across the SEPA zone.
Who should accept SEPA Direct Debit
- Any subscription business collecting in euros.
- European B2B invoicing operations that can move recurring collection off cards onto SDD B2B.
- Utilities, telcos, insurers — SDD is the incumbent rail.
Operational detail
The operational half of every method profile — settlement, refunds, disputes, PSP coverage and licensing — is reserved for Payment Methods List founding partners. It's the part vendor sites won't publish and the part that actually decides whether SEPA Direct Debit works for your stack.
Settlement time
How fast SEPA Direct Debit funds land after the payer confirms, behaviour outside scheme hours, whether the rail settles gross or net, and the realistic T+n to sweep to USD/EUR — plus the PSPs where the advertised timeline actually holds in SEPA area (36 countries).
Book a founding-partner call →Refund mechanics
How SEPA Direct Debit refunds are executed end-to-end when the rail has no scheme-level reversal — payer-initiated pulls, credit transfers, or PSP-fronted refunds — plus partial-refund support, time limits, and the API surface each PSP exposes.
Book a founding-partner call →Chargeback exposure
Whether SEPA Direct Debit has any dispute construct at all, which recall/return/indemnity vectors actually exist on the rail, how consumer-protection rules in SEPA area (36 countries) route claims back to merchants, and observed loss rates versus cards.
Book a founding-partner call →PSP coverage matrix
Which acquirers and aggregators run direct rail connections to SEPA Direct Debit vs. reselling a partner, coverage depth and reliability, effective pricing bands, and who to pick when SEPA area (36 countries) volume is your primary use case.
Book a founding-partner call →KYC & licensing notes
Requirements to accept SEPA Direct Debit — local entity vs. cross-border MoR, licensing regime governing the rail in SEPA area (36 countries), KYC obligations at onboarding and per-transaction, and FX/reporting rules for foreign merchants.
Book a founding-partner call →