What Is SEPA? Credit Transfers (pain.001) vs Direct Debit (pain.008)

SEPA — the Single Euro Payments Area — makes a euro payment between two countries in the area work exactly like a domestic one: same rules, same rights, same execution times, no distinction between sending money across the street and across a border.

It covers all EU member states plus several others, and it standardizes two fundamentally different instruments — one where the payer pushes money, one where the payee pulls it.

Credit transfer vs direct debit

	SEPA Credit Transfer	SEPA Direct Debit
Initiated by	The payer	The payee
Direction	Push	Pull
Message	pain.001	pain.008
Prior authorization	None needed	Mandate required
Typical use	Paying suppliers, salaries, tax	Subscriptions, utilities, recurring fees
Refund rights	Very limited once executed	8 weeks unconditional; 13 months if unauthorized

The refund column is the one that changes system design. A credit transfer is essentially final: you sent it, it is gone, and recovering it depends on the recipient's goodwill. A direct debit can be reversed by the payer for any reason at all within eight weeks — which is why a business collecting by direct debit must be able to handle a payment it already treated as settled coming back.

Credit transfers and pain.001

pain.001 — "payment initiation" in the ISO 20022 naming — is the file a business sends its bank saying make these payments. One file carries many payments: a payment run of supplier invoices, or a payroll.

Its structure is three levels:

• Group header — message ID, creation timestamp, total count and sum
• Payment information — the debtor (you), your IBAN, the requested execution date, and the payment method
• Transactions — per payment: creditor name, creditor IBAN, amount, and a remittance reference

The remittance information is the field that decides whether the recipient can reconcile the payment automatically. Putting the invoice number there is the difference between the supplier matching it in a second and someone emailing you to ask what the payment was for — the same signal, in reverse, that makes bank reconciliation work on the receiving side.

Variants exist: SEPA Instant (SCT Inst) settles in seconds, around the clock, and EU regulation now requires payment service providers to offer it.

Direct debits and pain.008

pain.008 is the collection instruction: take this money from these accounts. It only works with a mandate — the payer's documented authorization, identifying the creditor, the payer's IBAN, and whether collections are one-off or recurring.

Mandate management is the substance of direct debit, and it is where implementations get complicated:

• Each mandate has a unique reference (UMR) and a signature date, and both travel in every collection.
• The Creditor Identifier identifies you across the area.
• Sequence type matters — first, recurring, one-off, final — and getting it wrong causes rejections.
• Pre-notification: the payer must be told the amount and date in advance, by default 14 days unless otherwise agreed.
• Mandates expire after 36 months without a collection.
• Two schemes exist: CORE (consumers, with the full eight-week refund right) and B2B (businesses only, no refund right, and the payer's bank must confirm the mandate).

The eight-week refund right is not a dispute process — the payer's bank returns the money on request, no reason required, and you find out afterwards. Any system collecting by direct debit needs to handle returns as a normal event rather than an exception.

What Nordlet supports

SEPA Credit Transfer — implemented. POST /v1/bank/payments/export generates a pain.001 file for selected open purchase invoices: your account as debtor, each supplier's IBAN as creditor, the invoice amount, and the document number as remittance information. You upload it to your bank, the bank executes, and the resulting statement is imported and matched back against those invoices — closing the loop described in bank reconciliation.

Supplier bank accounts are held per partner, so payment details come from the partner record rather than being typed per payment run. IBANs are validated on entry.

SEPA Direct Debit — not implemented. There is no pain.008 generation and no mandate management. It is on the roadmap, and stating that plainly matters more than implying coverage: collecting by direct debit needs mandate storage, sequence tracking, pre-notification and return handling, and none of that exists today. Companies collecting by direct debit currently do so through their bank or a PSP, and the resulting settlements are reconciled through payment reconciliation.

Statement import — the other half of both flows — supports camt.053 and MT940.

FAQ

What is the difference between pain.001 and pain.008?

pain.001 initiates credit transfers, where the payer pushes money out. pain.008 initiates direct debit collections, where the payee pulls money in and needs a signed mandate to do so. Both are ISO 20022 XML messages sent to a bank.

Do I need a mandate for a SEPA credit transfer?

No. A credit transfer is initiated by the account holder paying, so no separate authorization exists. Mandates are only required for direct debits, where someone else takes money from your account.

How long can a SEPA direct debit be refunded?

Eight weeks unconditionally for the CORE scheme — the payer needs no reason. If the collection was unauthorized, the window extends to 13 months. The B2B scheme has no refund right, which is why it requires the payer's bank to confirm the mandate.

What is a Creditor Identifier?

A unique identifier assigned to a business that collects by direct debit, used across SEPA to identify the creditor on every collection and mandate. It is issued nationally, typically via your bank or central bank.

Can I send SEPA payments to any European country?

To any country in the SEPA area, which covers the EU plus several non-EU states, for payments in euro. The payment is treated the same as a domestic one in terms of rules, rights and execution times.