Accepting SEPA Direct Debit as a merchant

SEPA Direct Debit lets you pull funds from a customer’s euro account under a mandate they have granted you. For recurring billing it is usually the cheapest instrument available in the eurozone, and it is the one most often left unexamined because the per-transaction cost looks trivial next to cards.

How to accept SEPA Direct Debit as a merchant

You do not contract with a scheme. You need a creditor identifier and a bank or PSP that supports collection, and you must hold a valid mandate for each payer. Two schemes exist: Core, used for consumers, with an eight-week no-questions refund right and thirteen months where a mandate is disputed; and B2B, restricted to businesses, without that refund right but requiring mandate confirmation by the debtor bank. Choosing the wrong one for your customer base is a common and expensive error.

Where the real cost sits, and it is not the fee

The collection fee is low. The cost is in failures. Returns, refusals and revocations each carry their own charge, each break a billing cycle, and each generate manual work that never appears in the payments line of your P&L. A direct debit programme with a poor mandate capture flow and weak retry logic can cost several times its nominal fee in operational handling and involuntary churn. That is the number worth measuring.

The Instant Payments Regulation and Verification of Payee

Regulation (EU) 2024/886 obliged eurozone payment service providers to be able to receive instant euro payments from 9 January 2025 and to send them from 9 October 2025, with fees no higher than for ordinary transfers. From 9 October 2025 those providers must also offer Verification of Payee, checking that a payee name matches the IBAN before a transfer is authorised. Providers outside the eurozone have until 9 July 2027. The precise point for merchants: Verification of Payee applies to credit transfers, not to direct debits, though the European Payments Council has indicated the principle could extend to mandate verification as the rules develop. The broader effect is that instant credit transfer is becoming a credible alternative rail for collections that direct debit has owned by default.

Finality

When a direct debit collection actually becomes final

A collection that settles is not yet a payment you can rely on. Under the Core scheme the debtor can demand a refund within eight weeks of the debit date for a collection they authorised, with no reason given and no opportunity for you to object. Where no valid mandate exists, that window runs to thirteen months.

The B2B scheme is a different risk position entirely. The debtor has no right to obtain a refund for an authorised transaction. The only exposure after settlement is a return by the debtor’s bank, and that closes three inter-PSP business days after the settlement date.

The same instruction therefore carries either eight weeks of unconditional reversal risk or three business days of it, decided solely by which scheme the mandate was written under. Merchants billing other businesses on Core mandates are carrying an exposure the scheme does not require them to carry.

Liability

There is no dispute process on a direct debit

A disputed card transaction gives you a defence. The chargeback arrives, you present evidence, and the scheme decides it. Direct debit has no equivalent mechanism.

Inside the eight-week Core window a refund is unconditional. The debtor instructs their own bank, the bank credits them, and the amount is recovered from you through your PSP. Nobody asks for the mandate, the pre-notification or your terms, because none of them bear on a refund of an authorised collection. Your only remedy is commercial, and it starts after the money has gone.

Past eight weeks the position inverts. A claim made up to thirteen months rests on the collection being unauthorised, and there the mandate is the entire case. If you cannot produce a valid mandate on request, you lose. Mandate storage is not an administrative detail, it is the only evidence you will ever be asked for.

Authorisation

There is no authorisation step, and no capture

Direct debit does not separate authorisation from capture, because there is no authorisation at all. Nothing is reserved, no balance is checked and no decision comes back before the due date. That rules out pre-authorisation, delayed capture, partial capture and split shipment, so any model that depends on holding an amount and taking it later cannot be built on this rail.

The timing is set by the rulebook rather than by your provider. The collection must reach the debtor’s bank at the latest one inter-PSP business day before the due date, and no earlier than fourteen calendar days before it. That window is the same for first, one-off and recurrent collections.

The obligation most often missed sits on you rather than on your PSP. You must pre-notify the debtor at the latest fourteen calendar days before the due date unless you have agreed a different timeline with them. A shorter notice period is available, but it has to be agreed in your terms rather than assumed.

There is no ceiling in the scheme either. Neither Core nor B2B sets a maximum collection amount, so any limit your customers run into comes from their own bank or from your PSP. It varies from one customer to the next, which means it cannot be designed around, only detected.

Refunds

A refund does not travel back over the direct debit

There is exactly one route back over the scheme and it is narrow. Where you conclude a collection should not have been processed, a reversal reimburses the debtor the full amount, and it runs from the settlement date and within the five inter-PSP business days following the due date. Full amount only, and inside that window only.

Everything else leaves as a SEPA credit transfer. Any partial refund, and any refund after those five business days, is a separate outbound payment carrying its own cost, its own reconciliation line and its own failure modes. The customer’s IBAN changes role, from the account you collect from to the account you pay out to.

Model direct debit as the mirror image of a card refund and this is where it breaks, which in practice means the returns process.

Confirmation

You are never told that a collection succeeded

The scheme sends failure signals, not success signals. A collection that works produces nothing at all. You infer success from the absence of a return message, across a window that does not close for eight weeks.

What can arrive instead is a reversal, and each kind carries its own deadline and its own decision-maker. Dunning, revenue recognition and any fulfilment you defer until payment therefore have to be built on the absence of a signal rather than the arrival of one, over a period measured in weeks rather than seconds.

What can still take the money back	How long you are exposed	Applies to
Their bank returns the collection	5 business days after settlement	Core, and 3 days under B2B
They ask for it back, no reason required	8 weeks from the debit date	Core only
They ask for it back and you cannot show a mandate	13 months from the debit date	Core only
You reverse it yourself	5 business days after the due date	Core and B2B

Mandate

The mandate is the asset, and it expires

Direct debit is mandate-based rather than token-based, and the mandate has a life of its own. Present no collection under a mandate for thirty-six months, counted from the date of the last collection presented even where that collection was rejected, returned or refunded, and you must cancel the mandate and may no longer collect against it. A dormant customer is not paused, the authority is gone and has to be taken again.

B2B adds a step before the first collection that Core does not have. The debtor’s bank must check, before debiting, that the mandate data in the first collection matches what the debtor confirmed to them directly, and that the mandate was duly issued and authorised. A B2B mandate is not live because you hold it, it is live once your customer has registered it with their own bank. First-collection failures on B2B are usually this rather than an error on your side.

B2B also cannot be offered where the debtor is a consumer under the law of the place their bank provides the service, so scheme choice follows who the customer is rather than which risk position you would prefer.

Migration

From 15 November 2026 an unstructured address is rejected

From 15 November 2026 the SEPA schemes accept only a structured or a hybrid address. An unstructured address leads to a reject. This applies to any collection executed or settled from that date that carries a debtor or a creditor address.

Whether it touches you turns on a detail most coverage skips. Under the direct debit rulebooks the creditor address is optional, and the debtor address is mandatory only where the creditor’s bank or the debtor’s bank sits in a SEPA country outside the EEA. For most eurozone collections the question is therefore not whether you can supply a compliant address, it is whether you are supplying one at all. If your submissions carry addresses and those addresses are unstructured, those collections will be rejected from that date. If they carry none, nothing changes for you on 15 November.

Hybrid is the lighter route to compliance. Country and town name have to be structured, while street, building number and postcode may stay in up to two unstructured address lines of seventy characters each. The structured format has been available since March 2024 and the hybrid format since October 2025, so neither is new.

The work sits in your own customer data rather than at your provider. The EPC expects creditors to upgrade the debtor records they hold so that those records can store a structured, or at least hybrid, address by 15 November 2026.

Which payment provider supports SEPA Direct Debit?

Unzer, PAYONE, Buckaroo and Saferpay all document SEPA Direct Debit, as do most other European PSPs and banks. The useful questions are what a collection costs, what each failure type costs, what your actual failure rate is, and whether your provider offers intelligent retry. That last one moves revenue rather than cost.

Reviewing what this costs you

What you pay is set in your PSP contract, not by the scheme. Start by establishing whether you are overpaying your PSP, or move straight to cutting your PSP costs, because a cheap method priced badly still costs more than it should.

Relevant markets: eurozone