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

Open Banking & Request to Pay / Learning brief

Request to Pay versus SEPA Direct Debit

Your notes

What this means in plain language

Two ways to collect a recurring bill that look similar and behave differently. A direct debit pulls money on a standing mandate; Request to Pay sends a message the payer must actively answer each time. Compares who initiates, the consent model, push versus pull, revocation and refunds, and the rails underneath.

Request to Pay and SEPA Direct Debit are two ways to collect a recurring bill that look similar and behave differently. A direct debit pulls money from the payer's account on a standing mandate the payer gave in advance, so the creditor initiates each collection and the payer's protection comes largely from a refund right after the fact. Request to Pay sends a message the payer must actively answer each time: the payee asks, and no money moves until the payer accepts and their own bank pushes a credit transfer. The trade-off is control versus convenience. A mandate is convenient and automatic but puts the arrow in the creditor's hand; a request keeps the payer in control and lets them confirm the amount first, at the cost of needing an answer every time and losing the automatic mandate refund.

Three things to remember

  1. 01

    A direct debit is a pull on a standing mandate: the creditor initiates, and the payer relies on an after-the-fact refund right.

  2. 02

    Request to Pay is a push the payer authorises each time: no mandate to police, and the payer confirms the amount before money moves.

  3. 03

    Direct debit favours automatic, unattended collection; Request to Pay favours payer control and cleaner consent, but needs a response every cycle.

Where you would use this

USE CASE 01

A biller with variable amounts uses Request to Pay so the payer confirms each charge, avoiding wrong-amount disputes.

USE CASE 02

A biller with stable, predictable charges keeps direct debit for hands-off collection where a missed response would break billing.

USE CASE 03

A disputes team notes that a direct-debit claim may trigger an automatic refund, while a Request to Pay dispute is argued with the creditor.

Put the idea into a real situation

(SYNTHETIC / TRAINING ONLY) Example Supplies Ltd bills Maya Chen EUR 45.00 each month. Under SEPA Direct Debit, Example Supplies pulls the amount on Maya's standing mandate; if she disagrees, she leans on her direct-debit refund right after the money has already left. Under Request to Pay, Example Supplies instead sends Maya a request every month; nothing is collected until she accepts and Bank Alfa pushes a credit transfer. When one month's bill is unexpectedly EUR 145.00, the direct debit would have pulled it and left Maya to claim it back, whereas the request lets her question the amount before any money moves — control traded for the effort of answering each time.

Evidence & review

REVIEWED 2026-07-18

Compares Request to Pay and SEPA Direct Debit as collection methods in a SEPA setting; the trade-offs generalise, but mandate rules and refund rights are scheme- and jurisdiction-specific.

What this brief simplifies: Contrasts one instalment pattern of each method. 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.

Sources for this brief2
  1. Scheme-specific rule2025 version 1.1 (EPC125-05)

    2025 SEPA Credit Transfer rulebookEuropean Payments Council

    Governs the SEPA Credit Transfer scheme: participant obligations, datasets, time cycles, and r-transaction rules for euro credit transfers. · Effective 2025-10-05 · Checked 2026-07-12

    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.

  2. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    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.

Learn this properly

Related briefs

Request to Pay, explained

Request to Pay flips the direction of a bill: instead of pulling money on a mandate, the payee sends a request and the payer decides to accept, defer, decline, or part-pay. Follows a pain.013 request and a pain.014 response, then shows the money still moving as an ordinary instant credit transfer.

READ BRIEF

Open-banking payment initiation, explained

How a payment-initiation service moves money: with the payer's consent, a licensed third party asks the payer's own bank to send a normal credit transfer. Follows one checkout end to end — consent, the bank's strong customer authentication, the debit, and a SEPA credit transfer that settles the way any other transfer does.

READ BRIEF

SEPA Direct Debit: B2B versus Core

The SEPA (Single Euro Payments Area) Direct Debit Business-to-Business scheme differs from the Core scheme: no no-questions refund right for authorised collections, a mandatory mandate check by the debtor's bank, and eligibility limited to non-consumer payers.

READ BRIEF
COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Public discussion

LOADING

Loading the discussion…