SEPA Direct Debit

SEPA Direct Debit lets you collect euro payments directly from a payer's bank account within the Single Euro Payments Area (SEPA). The payer authorises the collection by granting a SEPA mandate, which you must present at checkout and which the payer must accept before the payment is created.

This payment method supports both SEPA schemes:

• dd for the consumer (B2C) scheme
• dd_b2b for the business-to-business (B2B) scheme

There is no hosted page and no browser redirection. The transaction is submitted to the payer's financial institution during the next export cycle, so it stays in the started status until submission happens, and its final status is delivered asynchronously via postback.

Networks	Features	Integrations	payment_type
SEPA banks	Payment Authorize Capture Refund Partial refund Payout Recurring Reverse Register	Server-to-Server Checkout Page Pay by Link Payment Page Redirect	dd / dd_b2b

Payment workflow

The following diagram explains the SEPA Direct Debit payment workflow for the Server-to-Server integration.

SEPA Direct Debit — Server-to-Server

Scroll horizontally if the diagram is wider than your screen.

1. 1
   Payer→Merchant (Acceptor)

   1. Provides IBAN and accepts the SEPA mandate at checkout

2. 2
   Merchant (Acceptor)→OneAPI

   2. Create Direct Debit payment (Payment API, IBAN + mandate)

3. 3
   OneAPI→Merchant (Acceptor)

   3. Response with status started (1)

4. i
   OneAPI

   Queued for the next SEPA export cycle

5. 4
   OneAPI→Bank (Financial Institution)

   4. Submit direct debit collection (same or next business day)

6. i
   OneAPI

   Status changes to pending (2)

7. 5
   OneAPI→Merchant (Acceptor)

   5. Postback — pending (2)

8. i
   Bank (Financial Institution)

   Bank statement reconciliation (camt.053 / MT940 / CDZ)

9. 6
   Bank (Financial Institution)→OneAPI

   6. Debit settled, no reason code

10. i
    OneAPI

    Status changes to completed (3). On a return, status becomes chargeback (13), declined (6), or error (4) instead

11. 7
    OneAPI→Merchant (Acceptor)

    7. Postback — completed (3)

12. 8
    Merchant (Acceptor)→Payer

    8. Shows final order confirmation

The transaction moves through the following statuses (identical for B2C and B2B). The Status Code column is the transaction's status code:

Status	Status Code	When
started	1	Payment created; queued for the next SEPA export cycle
pending	2	Collection submitted to the bank via the export file. Treated as a successful state
completed	3	The debit settled and no return was received
chargeback	13	The collection was returned (a return with or without a reason code)
declined	6	Return with a decline reason code
error	4	Return with an error reason code

note

The started status in the synchronous response is not the final result. SEPA is processed asynchronously, so use the postbacks sent on each status change as the source of truth. A standalone mandate reference created with the Mandate Reference API stays in the registered (9) status.

Legal Implications

Before creating an initial SEPA Direct Debit payment you must display the SEPA mandate information to the payer and have them explicitly agree to the collection of the debited amount. The mandate text must include the creditor details, the mandate reference, the account holder, and the IBAN.

caution

For B2C, the payer has the right to demand a refund of a charged amount for up to eight weeks from the date of the charge. For B2B, there is no refund right for authorised collections after the debit. All examples of SEPA legal texts are provided for guidance only and are not guaranteed to be legally compliant.

For recurring collections, the payer must additionally receive a pre-notification announcing the amount and the due date before each collection.

Integration options

Choose how you want to accept SEPA Direct Debit:

Server-to-Server

Collect the IBAN and SEPA mandate in your checkout, then send the payment directly to OneAPI via the Payment API. No hosted page or browser redirect.

Start integrating

Checkout Page

Create a checkout session and redirect customers to the hosted checkout. SEPA Direct Debit is available among the configured payment methods.

Start integrating

Pay by Link

Share a Pay by Link with your customer. When enabled on the channel, they can pay with SEPA Direct Debit on the checkout.

Start integrating