Request to Pay vs SEPA Direct Debit
Two ways to collect a recurring bill that look similar and behave differently. A direct debit pulls money on a standing mandate the payer gave in advance; Request to Pay sends a message the payer must actively answer each time, and no money moves until they accept and their own bank pushes a credit transfer.
| DIMENSION | Request to Pay | SEPA Direct Debit |
|---|---|---|
| Who initiates the money movement | The payer. The payee only sends a request; the payer's bank pushes the payment once the payer accepts. | The creditor. It initiates each collection and pulls the funds from the payer's account. |
| Consent modelThe request layer moves consent to the moment of payment; the mandate front-loads it. | Per-transaction. The payer gives an explicit answer to each request — accept, defer, decline, or in some rulebooks part-pay. | Standing mandate. The payer authorises once, in advance, and the creditor collects repeatedly under that mandate. |
| Push versus pull | A push. The payer's bank sends money out, so there is no debit the payer did not initiate. | A pull. The creditor draws money in from the payer's account under the mandate. |
| Revocation and refund | No mandate to revoke; the payer simply declines or ignores a request. Because settlement is a push the payer authorised, there is no automatic scheme refund — a dispute is argued with the creditor. | The payer can cancel the mandate, and SEPA Direct Debit carries a refund right for a period after collection, so money already pulled can be returned. |
| Rails underneath | A messaging layer (a pain.013 request, a pain.014 response) over a normal credit transfer, typically an instant SCT Inst that settles the way any transfer does. | The SEPA Direct Debit scheme itself, with its own collection messages, mandate handling, and settlement timing. |
Sources for this comparison2
- Scheme-specific rule2025 version 1.1 (EPC125-05)
2025 SEPA Credit Transfer rulebook ↗ — European Payments Council · SEPA credit transfer settlement leg; direct debit contrast
Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Request to Pay is treated as a general pattern; scheme-specific SEPA Request-to-Pay (SRTP) rulebook detail was not re-verified against a dedicated registered source. Direct-debit refund and mandate rules are summarised, not quoted in full, and use a synthetic cast.
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.