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 SRTP 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 SRTP 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.
- The SEPA Request-To-Pay (SRTP) scheme rulebook V4.0
- Clarification document on SEPA Request-to-Pay scheme rulebook
- SEPA Request-To-Pay Inter-SRTP SP API Specifications
- SEPA Request-to-Pay Implementation Guidelines Version 4.0
- API Security Framework V2.0
- The SEPA Request-to-Pay (SRTP) scheme: the first participant shares their experiences and views
- Toolkit for new SEPA Request-to-pay (SRTP) scheme participants
- Link to Register of Participants
- EPC Default API Specifications
- Clarification document on 'Federated Approach'
Previous versions
SRTP Scheme evolution calendar:
- 1 February – 30 April 2026
Homologation wave 1-2026 - 1 April to 30 June 2026
Homologation wave 2-2026 - 1 September to 31 November 2026
Homologation wave 3-2026 - End of September 2026
EPC Directory Service (EDS) open to the SRTP scheme participants