The SEPA Request-to-Pay (SRTP) scheme covers the set of operating rules and technical elements (including messages) that allow a Payee to request the initiation of a payment from a Payer in a wide range of physical or online use cases.
The RTP is a messaging functionality. It is not a payment means or a payment instrument, but a way to request a payment initiation.
The scheme can be considered as a complement to the payment flow because it supports the end-to-end process and lies between an underlying commercial transaction and the payment itself. An RTP as such can be seen as an enabler for digital payments.
Eligible entities from all countries in SEPA shall be allowed to participate on the basis that the level playing field principle between payment service providers (PSPs) and non-PSPs is respected.
It is envisaged that the scheme will evolve further over time to support more elaborate functionalities.
- The SEPA Request-To-Pay (SRTP) Scheme Rulebook V3.2
- Clarification Paper on the SEPA Request-to-Pay scheme rulebook
- SEPA Request-to-Pay Implementation Guidelines Version 3.0
- The SEPA Request-to-Pay (SRTP) scheme: the first participant shares their experiences and views
- The SRTP scheme rulebook V4.0
- EPC Default API Specifications
- API Security framework V1.0
- API Security Framework V2.0
- Toolkit for new SEPA Request-to-pay (SRTP) scheme participants
- Link to Register of Participants
SRTP Scheme evolution calendar:
- November 2024
Publication of the SRTP Scheme Rulebook (version 4.0)
- April 2025
Publication of the SRTP Implementation Guidelines and API specifications (version 4.0)