SEPA / Learning brief
SEPA Direct Debit core
Your notes
In simple terms / 01
What this means in plain language
Describes the pull-payment model of SEPA Direct Debit Core: how a signed mandate authorises collection, how a collection travels as a pain.008 and interbank pacs.003 message, and the roles the creditor and debtor banks play.
The Single Euro Payments Area (SEPA) has two sides. A credit transfer pushes money out; a direct debit pulls it in. SEPA Direct Debit (SDD) is that pull side: instead of the payer sending money, the party being paid — the creditor — collects it. The debtor authorises this once by signing a mandate, a standing permission that carries a unique reference and names the creditor. For each collection the creditor sends an instruction to its own bank, which passes it into the interbank system so that on an agreed due date the debtor's account is debited and the creditor is paid. Two schemes share this machinery. SDD Core is open to consumers and comes with strong rights to get money back. SDD Business-to-Business (B2B) is for companies only, where the debtor's bank checks the mandate and authorised collections are final. Because someone else reaches into the account, the scheme adds protections: the debtor must be told before each collection, and collected money stays provisional for a defined time.
Complete lesson / 02
Understand the full idea, step by step
Think about a subscription you pay every month. You never open your banking app to send it — the money simply leaves your account on roughly the same day each time, and you would only notice if it stopped. Someone is reaching in and taking it, with your blessing. How does a bank let that happen safely?
Reverse the arrow
In a credit transfer the payer pushes money out. A direct debit turns the arrow around: the party being paid — the creditor — pulls money in, and the payer — the debtor — authorised it in advance. Nothing else about the payment is exotic. The unusual part is only the direction and the permission that makes reaching into someone's account acceptable.
The mandate — the debtor's standing permission for a specific creditor to collect
A mandate is the authorisation Riya signs once and hands, in effect, to Asha Traders. It carries a unique mandate reference and the creditor's identifier — in the Single Euro Payments Area (SEPA), the creditor scheme identifier that names the collector across the whole area. Together they let every later collection be tied back to the exact permission the debtor gave, which is what makes any future dispute answerable.
This month's collection at a glance
- Debtor (payer)
- Riya — account at Bank Alfa
- Creditor (collector)
- Asha Traders — account at Nordbank
- Amount
- EUR 84.50
- Mandate reference
- ASHA-MND-0007
- Sequence
- Recurring — one of a series
- Scheme
- SEPA Direct Debit (SDD) Core
How a collection travels
- NOTIFICATION
Before each collection, Asha Traders pre-notifies Riya — an invoice or a schedule stating the amount and the date is enough. Riya is never surprised by what will leave her account.
- INSTRUCTION
Asha Traders sends its own bank, Nordbank, a customer-to-bank instruction: a pain.008 message ('pain' = payments initiation), one line per debtor it wants to collect from.
- MESSAGE
Nordbank presents the collection to Bank Alfa through the clearing mechanism as an interbank pacs.003 message ('pacs' = payments clearing and settlement). The mandate details ride inside it.
- VALIDATION
Bank Alfa checks the data presented — is the account live, is the reference well-formed — but under Core it does not verify the mandate itself.
- LEDGER
On the due date, Bank Alfa debits Riya's account EUR 84.50 and Asha Traders is paid through settlement between the two banks.
- NOTIFICATION
Riya sees the debit on her statement. The money is hers no longer — but for a defined window it is not yet beyond recall, as the next lessons show.
ISO 20022 — ILLUSTRATIVE, NON-PRODUCTION
<CstmrDrctDbtInitn>
<PmtInf>
<PmtMtd>DD</PmtMtd>
<DrctDbtTxInf>
<InstdAmt Ccy="EUR">84.50</InstdAmt>
<DrctDbtTx>
<MndtRltdInf>
<MndtId>ASHA-MND-0007</MndtId>
<DtOfSgntr>2026-01-15</DtOfSgntr>
</MndtRltdInf>
</DrctDbtTx>
</DrctDbtTxInf>
</PmtInf>
</CstmrDrctDbtInitn>Illustrative pain.008 fragment — the creditor's instruction to its own bank. Notice the mandate reference and signature date travel with the collection; the interbank pacs.003 that Bank Alfa receives carries the same mandate details plus a sequence type marking a one-off, first, recurring, or final collection. Neither message moves money — each asks a bank to post it.
| Account | Dr | Cr |
|---|---|---|
| Riya's current account | EUR 84.50 | |
| Settlement position owed toward Nordbank | EUR 84.50 |
Illustrative two-entry view on the due date. A real bank posts more entries — fees, control accounts, and its position with the clearing mechanism — and the exact account structure varies by institution.
You may be wondering: if Asha Traders can just pull money, what stops it taking the wrong amount?
Two things sit in the way. First, pre-notification: Riya is told the amount and date in advance, so a surprise figure is visible before it lands. Second, and more powerfully, SDD Core hands the debtor a strong right to get money back after the fact. Because Bank Alfa debits on the strength of the data presented rather than checking the mandate, the scheme balances that trust with a generous refund right — the subject of a later lesson. The permission to pull is always paired with a way to pull it back.
STRICTLY SPEAKING
Strictly speaking, the exact presentation window around the due date, how long a mandate may sit unused before it lapses, and the precise data elements are all set by the European Payments Council's SDD Core rulebook and its implementation guidelines, and they change between rulebook versions. Treat the mechanics here as the stable shape and check the edition in force before quoting any specific timing.
FOR NOW, REMEMBER
- A direct debit reverses the credit-transfer arrow: the creditor pulls, under a mandate the debtor signed once.
- The mandate — a unique reference plus the creditor scheme identifier — travels inside every collection so any dispute can be traced back.
- The creditor initiates with a pain.008 to its own bank; banks exchange the collection interbank as a pacs.003; the debtor's account is debited on the due date.
- Under SDD Core the debtor's bank debits on presented data without checking the mandate — which is why Core pairs the pull with a strong refund right.
TRY IT YOURSELF
Bank Alfa receives a pacs.003 to collect EUR 84.50 from Riya, referencing mandate ASHA-MND-0007. Under SDD Core, what does Bank Alfa do before debiting?
Riya is a consumer, and Core wraps her in a refund right. But when the debtor is a business paying a supplier, the scheme moves the protection somewhere else entirely. Meet SDD B2B.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
SEPA Direct Debit is a pull payment: the creditor collects from the debtor under a mandate the debtor signed in advance.
- 02
Each collection is sent by the creditor's bank as a pain.008 message and exchanged between banks as a pacs.003, aimed at an agreed due date.
- 03
SDD Core serves consumers with strong refund rights, while SDD B2B serves businesses and treats authorised collections as final.
Practical use cases / 04
Where you would use this
A utility or subscription business collects recurring bills automatically instead of waiting for each customer to pay.
A creditor's operations team monitors failed collections to find stale account data or expired mandates before a run.
A debtor's bank debits the account on the due date using the mandate details carried inside the collection message.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional gym, Northgate Fitness, holds a signed mandate to collect EUR 39.00 monthly from a member. On 3 July it sends its bank a pain.008 for a EUR 39.00 collection with a due date of 15 July; the banks exchange it as a pacs.003. The mandate reference and the creditor scheme identifier travel inside the message. On 15 July the member's bank debits EUR 39.00 and Northgate Fitness is credited. The collection is presented no earlier than 14 calendar days before the due date, so a 3 July send for a 15 July debit sits inside that window.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01ProcessingAsha 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.
- 02MessageAsha 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.
- 03MessageAsha 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.
- 04MessageNordbank 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.
- 05Clearing obligationThe 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.
- 06SettlementPositions 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
- 07PostingBank 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
- 08PostingNordbank 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
Evidence & review / 07
Evidence & review
SEPA Direct Debit Core scheme, euro area; ISO 20022 message names per the EPC implementation guidelines.
What this brief simplifies: Ledger shows two entries where a real bank posts more; presentation and mandate-validity timings are described rather than quoted; the refund right is named here and developed in later lessons.
Sources for this brief3
- Scheme-specific rule2025 v1.1 (EPC016-06)
2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · Mandate, pre-notification, presentation, debtor-bank obligations
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain.008; pacs.003
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.