What Is SEPA Request-to-Pay?
SEPA Request-to-Pay (SRTP) is a messaging scheme in which a creditor delivers a structured payment request to a debtor. It is not itself a payment instrument; it does not initiate the payment, it only carries the request.
Updated:
What exactly is SEPA Request-to-Pay?
SEPA Request-to-Pay (SRTP) is a scheme managed by the European Payments Council (EPC). Its core function can be summarised in a single sentence: it lets a creditor (payee) send a structured payment request to a debtor (payer).
The critical point to underline here is this: SRTP is NOT a payment instrument. It does not itself carry money, does not collect from an account and does not initiate the payment. SRTP is only a messaging layer — it carries the information "pay this amount, with this reference number, by this date" in a standard form. When the request is accepted, the actual movement of money is carried out with a separate SEPA transfer (for example, SCT, or SCT Inst for an instant payment). So SRTP is not the payment itself but the approved invitation that triggers the payment.
How does the SRTP flow work?
The process proceeds in a few clear steps between the creditor and the debtor:
- Sending the request: The creditor (for example, a merchant or an invoicing institution) sends the debtor a Request-to-Pay message containing the amount, reference and, if any, the due date.
- The debtor's decision: The debtor sees the request in their banking app and can accept, reject or defer it. Control is entirely with the debtor; no amount leaves their account without their approval.
- The payment taking place: If the debtor accepts, a separate SEPA transfer (SCT or SCT Inst) is triggered on the basis of this approval, and the money actually moves at this stage.
In this respect, SRTP can be thought of as an "approval bridge" that separates the payment request from the actual making of the payment.
Where is it used?
Request-to-Pay suits a wide variety of scenarios based on request and approval:
- E-invoice / digital invoice: A payment request tied directly to the invoice, approvable with one tap.
- E-commerce checkout: Approval of the basket amount via the debtor's bank.
- POS / in-store payment: Request-based payment at the physical point of sale.
- Recurring payments: An alternative flow open to the debtor's approval each time, for subscriptions or regular bills.
The difference between Request-to-Pay and Direct Debit (SDD)
The place where confusion arises most often is comparing SRTP with SEPA Direct Debit (SDD). Both serve the need to "collect an invoice", but they are fundamentally different in direction and control: in SDD the money is pulled by the creditor; in SRTP the debtor approves the payment and pushes it, keeping control in their hands.
| Feature | Request-to-Pay (SRTP) | SEPA Direct Debit (SDD) |
|---|---|---|
| Who initiates the transaction? | The creditor sends a request; the debtor initiates the payment | The creditor initiates the collection |
| Who has control? | The debtor (approves/rejects each request one by one) | The creditor (based on a mandate given in advance) |
| Flow of money | Push — a separate SCT/SCT Inst is triggered with the debtor's approval | Pull — the money is pulled from the debtor's account |
| Cancellation / dispute | Can be rejected before approval; no money leaves without payment | There is a refund/dispute route within a defined period after the payment |
In short: in SDD "you are made to pay first, and dispute if needed"; in SRTP "approval is taken first, then it is paid". The appeal of SRTP is that it gives the debtor full control at the moment of payment and on a per-request basis.
The status and adoption of SRTP
The EPC's Request-to-Pay scheme came into force in 2021. But adoption is gradual and not automatic: for a bank or payment institution to be able to offer SRTP, it must join the scheme separately. For this reason SRTP is not present at every bank in the SEPA area; participants are listed in the EPC's relevant records separately from SCT/SDD participants. Whether a specific institution supports it must be verified from the EPC participant record and the institution's own official information.
SRTP is positioned less as a stand-alone product and more as part of a broader payment ecosystem that works together with components such as instant payments (SCT Inst) and payee verification (Verification of Payee / VoP), aiming to improve the user experience and reduce fraud. The debtor seeing and approving each request structurally limits the risk of unauthorised collection.
The situation for Turkey
Turkey is not a member of the SEPA area; it is at the application/candidate stage. For this reason, Turkish banks cannot join the SRTP scheme and do not offer a Request-to-Pay service. SRTP works only between participating payment service providers within the SEPA area. Transfers from Turkey to the eurozone today generally proceed over SWIFT and do not fall within the scope of SRTP.
Important caveat
The specific features, pricing and availability of Request-to-Pay vary by bank, payment institution and national regulation. An institution having joined the scheme does not mean the service is offered to all customers or in all scenarios. For definitive information, consult your own bank's current statements and official EPC sources; the technical explanation on this page is for informational purposes and, where it is not verified, no definitive statement has been used.
Frequently asked questions
Is SEPA Request-to-Pay a payment method?
No. SRTP is not a payment instrument and does not transfer money on its own. It is only a messaging layer that carries the creditor's request to the debtor to 'pay this amount with this reference'. If the debtor accepts the request, the payment then takes place with a separate SEPA transfer such as SCT or SCT Inst.
What is the difference between Request-to-Pay and SEPA Direct Debit (SDD)?
In SDD, the money is 'pulled' from the account by the creditor based on a mandate the debtor gave in advance. In Request-to-Pay, the debtor sees and approves each request one by one and 'pushes' the payment themselves. So control stays in the debtor's hands; they can reject or defer the request.
Do Turkish banks have SEPA Request-to-Pay?
Because Turkey is not a member of SEPA, Turkish banks cannot join the SRTP scheme and do not offer this service. SRTP works only between participating payment service providers within the SEPA area.
Does every bank in the SEPA area support Request-to-Pay?
No. For a bank or payment institution to offer SRTP, it must join the scheme separately. Adoption is gradual and it is not present at every institution. Whether a specific bank supports it must be verified from the EPC participant records and the bank's own information.
Sources
Confidence is graded from A (official document) to E (unverified).
SEPA scheme rulebooks & geographical scope
European Payments Council (EPC)
- Document date:
- 2025
- Last checked:
- 2026-07-16
Register of Participants — official list of payment service providers that actually participate in the SEPA schemes (SCT, SCT Inst, SDD Core/B2B, VoP) (downloadable CSV/PDF/XML; SDD B2B register current as of 12 Jun 2026)
European Payments Council (EPC)
- Document date:
- 2026-06-12
- Last checked:
- 2026-07-16