GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

GET IN TOUCH
07 / SEPA & INSTANT PAYMENTS13 MIN

SDD Core: payments that pull

Direct debits reverse the arrow: the creditor collects under a signed mandate — and the money can come back.

Contributor Shubham Mathure

NOT STARTED

L0 Explain simply

Your gym fee and electricity bill leave your account without you doing anything each month. That is a direct debit: instead of you pushing money out, the company pulls it in. You allowed this once, up front, by signing a form. As an analogy: it is a standing permission slip — you hand it to the gym, and the gym shows it to the banking system every time it collects. Because someone else reaches into your account, the scheme wraps the arrangement in protections: you must be told before each collection, and if something looks wrong you can get the money back. That safety valve is what makes pull payments acceptable to consumers at all.

L1 Core concepts

SEPA Direct Debit is the pull side of SEPA. The debtor signs a mandate — a standing authorisation carrying a unique mandate reference and the creditor's identifier. The creditor then sends each collection to its own bank as a pain.008, and the banks exchange it as a pacs.003 through a clearing mechanism, aiming at an agreed due date when the debtor's account is debited. Two schemes share this machinery: SDD Core, open to consumers with strong refund rights, and SDD B2B, business-only, where the debtor's bank must verify the mandate and authorised collections are final. The creditor gets paid on time; the price is that the money is provisional.

L2 Practitioner view

Operationally, a collection is a scheduled event. The creditor pre-notifies the debtor (an invoice or schedule counts), then presents the collection ahead of the due date — the Core rulebook defines a presentation window: no earlier than 14 calendar days before the due date and, for standard processing, no later than one interbank business day before it. Collections carry a sequence type distinguishing one-off from recurrent instalments. What operations teams actually watch is the R-rate: rejected, returned, and refunded collections signal bad account data, expired mandates, or unhappy customers — and every one of them takes back money the creditor had already counted. A mandate itself lapses if the creditor lets 36 months pass without collecting.

L3 Technical details

Technically, the mandate travels inside every collection. The pacs.003 carries mandate-related information — the mandate reference (MndtId), the date of signature, and an amendment indicator for changed details — plus the creditor scheme identifier that uniquely names the collector across SEPA. The sequence type element (SeqTp) carries codes such as OOFF for one-off and FRST/RCUR/FNAL across a recurrent series. In Core, the debtor's bank does not validate the mandate — it debits on the strength of the data presented, which is exactly why the refund right must be generous. In B2B the burden flips: the debtor's bank must hold and check a confirmation of the mandate before it may debit a business account.

L4 Standards & sources

The governing texts are the EPC's 2025 SDD Core rulebook version 1.1 (EPC016-06) and the 2025 SDD B2B rulebook version 1.1 (EPC222-07), both in force since 5 October 2025. The Core rulebook defines the mandate's content and the 36-month lapse rule, the collection time cycle and presentation windows, and the full R-transaction catalogue; the B2B rulebook adds the mandatory debtor-bank mandate check and removes the refund right for authorised collections. Implementation guidelines published alongside the rulebooks pin the pain.008 and pacs.003 usage down to element level.

Sources & standards2
  1. Scheme-specific rule2025 v1.1 (EPC016-06)

    2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · 2025 v1.1 — mandate, time cycle, and R-transaction sections

    Rules of the SEPA Direct Debit Core scheme: mandates, collection lifecycle, timelines, R-transactions, and refund rights. · Effective 2025-10-05 · Checked 2026-07-13

  2. Scheme-specific rule2025 v1.1 (EPC222-07)

    2025 SEPA Direct Debit Business-to-Business rulebook version 1.1 (EPC222-07) ↗ — European Payments Council · 2025 v1.1 — mandate checking and refund provisions

    Rules of the SDD Business-to-Business scheme, including mandatory debtor-bank mandate checking and the absence of a refund right for authorised collections. · Effective 2025-10-05 · Checked 2026-07-13

SEE THE PAYMENT MOVE

SEPA Direct Debit — Core — swimlane diagramA biller pulls a euro invoice from a customer under a signed mandate: the collection instruction flows from the creditor's side while the money moves the opposite way, from debtor to creditor. The full step-by-step description follows this diagram as text.
MESSAGECLEARING OBLIGATIONSETTLEMENTPOSTING
SEPA Direct Debit — Core. One CSM, one settlement cycle, direct participants only, with pre-notification shown as a single step. Real SEPA Core direct debits batch many collections, honour fixed pre-notification lead times, and may run through indirect participants. PLAY IT STEP BY STEP →
Read the steps as text
  1. 01Processing
    Asha Traders confirms the mandateAsha Traders (creditor / biller)

    Before pulling any money, the biller checks it holds a valid mandate that Riya signed authorising these collections. The mandate — not the invoice — is what permits the pull; no mandate means no right to debit.

  2. 02Message
    Asha Traders pre-notifies Riya of the collectionAsha Traders (creditor / biller) → Riya (debtor / customer)

    The creditor tells the debtor the amount and the due date in advance, so Riya can expect the debit and keep the account funded. This is a courtesy notice ahead of the pull, not the money movement itself.

  3. 03Message
    Asha Traders submits the collection to NordbankAsha Traders (creditor / biller) → Nordbank (creditor bank) · pain.008

    Here is the mirror image of a credit transfer: the instruction starts at the payee. Asha Traders sends a pain.008 collection request to its own bank, Nordbank, to go and pull the funds from Riya's account.

  4. 04Message
    Nordbank submits the interbank collectionNordbank (creditor bank) → STEP2-T (CSM) · pacs.003

    Nordbank converts the customer collection into an interbank pacs.003 and submits it to the clearing and settlement mechanism, which will route it toward the debtor's bank to be collected on the due date.

  5. 05Clearing obligation
    The CSM calculates obligationsSTEP2-T (CSM)

    On the due date the CSM validates the collection and includes it in a clearing cycle, calculating who owes whom. In a pull this obligation runs from the debtor's bank to the creditor's bank — the reverse of a credit transfer.

    Clearing produces obligations only. Nordbank does not have Asha Traders' money yet — that waits for settlement.

  6. 06Settlement
    Positions settle in central bank moneyBank Alfa (debtor bank) → Nordbank (creditor bank)

    The calculated positions settle across the banks' accounts at the central bank. Money moves from Bank Alfa (debtor side) to Nordbank (creditor side) — funds flowing debtor to creditor even though the instruction came from the creditor.

    • DR Bank Alfa settlement account — EUR 480.00
    • CR Nordbank settlement account — EUR 480.00
  7. 07Posting
    Bank Alfa debits RiyaBank Alfa (debtor bank)

    Bank Alfa books the debit against Riya's account for the collected amount. This is the customer-facing side of the pull: money leaves the debtor's account because the mandate authorised it.

    • DR Riya's current account at Bank Alfa — EUR 480.00
  8. 08Posting
    Nordbank credits Asha TradersNordbank (creditor bank)

    Nordbank credits the biller's account. The collection is complete end to end: debtor debited, banks settled, creditor credited — with the funds having travelled from Riya to Asha Traders.

    • CR Asha Traders' account at Nordbank — EUR 480.00
Sources for this topic2
  1. Scheme-specific rule2025 v1.1 (EPC016-06)

    2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council

    Rules of the SEPA Direct Debit Core scheme: mandates, collection lifecycle, timelines, R-transactions, and refund rights. · Effective 2025-10-05 · Checked 2026-07-13

  2. Scheme-specific rule2025 v1.1 (EPC222-07)

    2025 SEPA Direct Debit Business-to-Business rulebook version 1.1 (EPC222-07) ↗ — European Payments Council

    Rules of the SDD Business-to-Business scheme, including mandatory debtor-bank mandate checking and the absence of a refund right for authorised collections. · Effective 2025-10-05 · Checked 2026-07-13

Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.