SEPA direct debit

DEFINITION

SEPA direct debit is a payment method for processing euro-denominated one-time and recurring payments across the UK and EU, using a customer's name and IBAN bank account number instead of a card.

SEPA direct debit is a payment method for processing euro-denominated one-time and recurring payments across the United Kingdom and the European Union, using a customer's name and bank account number in IBAN format instead of a card.

SEPA stands for Single Euro Payments Area. Rather than authorizing a card for each payment, a customer authorizes a business to pull funds directly from their bank account for euro-denominated charges. Because it draws from a bank account rather than a card network, SEPA direct debit is asynchronous: the outcome of a payment attempt is not known instantly the way a card authorization usually is, and it can take longer to confirm whether a payment succeeded or failed. Under the SEPA Direct Debit rulebook, a business must notify a customer before every account debit.

Why SEPA direct debit matters for subscription businesses

SEPA direct debit is a common payment method across the UK and EU, so offering it can matter for any subscription business trying to reduce checkout friction and payment failures for UK and European customers who prefer paying from a bank account rather than a card. Because SEPA is asynchronous, invoices paid with it need to be handled differently in dunning and retry logic than invoices paid with a synchronous method like a card. A business that treats SEPA payments the same way it treats card payments risks retrying or flagging failures at the wrong time, since the confirmation timeline is different.

Refund timing also needs consideration and the general recommendation is to wait until SEPA payments have processed fully before refunding, while recognizing that SEPA regulations allow customers to receive unconditional refunds up to 8 weeks past the original payment date. Ensure refund policies are up to date to avoid any issues.

How to use SEPA direct debit

  1. Confirm which payment gateway will process SEPA direct debit for the business, since gateway support and setup steps vary.

  2. Set up the required mandate process so a customer's authorization to debit their bank account is captured and stored correctly.

  3. Make sure customers are notified before each debit, since this is required under the SEPA Direct Debit rulebook.

  4. Decide how failed SEPA payments should be handled, including whether chargebacks or late failures are processed automatically or reviewed manually.

  5. Avoid combining SEPA direct debit with a 100 percent discount coupon at signup, since e-mandate creation is still required for this payment method even when no payment is due immediately. Use a free trial instead if that limitation applies.

Benefits and examples

Supporting SEPA direct debit gives European subscribers a payment option many of them already use for recurring bills, which can reduce drop-off at checkout for that audience. For example, a subscription business selling into the United Kingdom, Germany, France, or other EU countries can let customers pay from their bank account with just their name and IBAN, rather than requiring a card, which some European consumers do not use for recurring payments as readily as customers in other regions.

Because SEPA-related declines are often due to insufficient funds rather than a rejected card, a retry approach built specifically for direct debit can recover more of those failed payments than a generic card retry schedule would.

How Recurly supports SEPA direct debit

Recurly automatically sends the customer notification required before each SEPA debit, so a business does not need to build that compliance step itself. Recurly's direct debit retries are also built around how SEPA actually fails: only transactions declined for insufficient funds are retried, since other decline reasons are not something a second attempt is likely to fix. Supported direct debit payments can be retried twice, in line with NACHA, SEPA, and EU and Australian regulations, and the retry timing is fixed at 24 hours after an insufficient funds notification. For chargebacks and late failures on supported gateways, Recurly supports both automated and manual handling modes, configurable in Invoice Settings. SEPA direct debit is supported on Adyen, Stripe through Third Party Checkout, GoCardless, and Worldpay.

Frequently asked questions

What information does a customer need to provide for SEPA direct debit? A customer needs to provide their name and their bank account details in IBAN format, rather than a card number.

Why does SEPA direct debit take longer to confirm than a card payment? SEPA direct debit is an asynchronous payment method, meaning the outcome of a debit attempt is not known instantly the way a card authorization typically is. Recurly receives status updates when the bank payment is processed, which can result in a success or a failure. This is part of why SEPA payments are handled with different dunning and retry timing than card payments.

How many times will a failed SEPA payment be retried? Supported direct debit payments, including SEPA, can be retried twice, in line with NACHA, SEPA, and EU and Australian regulations, and only when the original decline was due to insufficient funds.

Can I offer a free trial or discount at signup if a customer pays with SEPA direct debit? A 100 percent discount coupon at signup is not supported with SEPA direct debit because e-mandate creation is still required for that payment method. A free trial can be used instead where the gateway supports it.

Which gateways support SEPA direct debit? SEPA direct debit is supported through Adyen, GoCardless, and Worldpay.