SRTP will play a major role in the transformation of payments in Europe. The establishment of an efficient and reliable process for the onboarding of SEPA Request-to-Pay (SRTP) service providers is essential. The homologation of SRTP service providers is a cornerstone within this onboarding process.
Sopra Steria has been officially selected by the European Payments Council (EPC) as the Homologation Body (HB) to verify and certify the compliance of SRTP Service Providers with the SRTP scheme as defined by the SRTP rulebook.
European Payments Council (EPC) contributes to harmonized payments in the Single Euro Payments Area (SEPA). The EPC defines Payment and Payment-related schemes that cover a set of rules, practices, and standards published in rulebooks and makes it possible for an eligible SEPA service provider to join, participate and operate in the scheme.Further details are provided on the website of the EPC: www.europeanpaymentscouncil.eu
One of the key payment-related schemes is SEPA Request-to-Pay (SRTP), which allows a Payee to request initiation of a payment from a Payer in a wide range of physical or online cases.Further details are provided on the EPC website: The SEPA Request-to-Pay (SRTP) scheme
The scope of the SRTP process includes the sub-processes between the underlying transaction and the payment transaction itself: Request-to-Pay and Acceptance or Refusal of the Request-to-Pay.
An Applicant who wishes to participate in the SRTP scheme needs to be homologated. The Homologation Body (HB) checks the compliancy of the Applicant against the SRTP rulebook and the SRTP scheme Implementation Guidelines. In case of a positive result “pass”, a homologation certificate is granted. The homologation report and certificate are mandatory inputs for the EPC to finalize the adherence process.
To deliver SRTP services, an Applicant is free to arrange the way the messages will be exchanged with other scheme participants and may use a Technical Solution Provider (TSP) to this extent. Any TSP that wishes so may at its discretion, undergo a specific SRTP homologation (Type: Homologation E). A duly homologated Technical Solution Provider will become a Referenced Technical Solution Provider (RTSP) and feature on a list of RTSPs published on the EPC website. An Applicant making use of an RTSP will be eligible to a more limited homologation (see chapter: Homologation types).
Different types of homologations have been defined. The number of requirements to be verified might vary accordingly. If the homologation type requires testing, it will be the same for all homologation types
The document “Homologation types & requirements” defines which requirements are applicable for each type of homologation.
The EPC will, as part of the identification process, determine the type of homologation an Applicant is eligible for, based on the information provided by the Applicant.
Homologation A is applicable for the homologation of an Applicant that has not gone through any valid formal authorization/licensing process, nor is subject to any regulatory/supervisory requirements and will not use a Referenced Technical Solution Provider homologated by the HB.
Homologation effort: Full assessment, Technical & Functional Testing, Penetration Testing.
Homologation B is applicable for the homologation of an Applicant that has already gone through a valid formal authorization/licensing process, and/or is subject to specific regulatory/supervisory requirements, and can demonstrate that any of such requirements can be considered as equivalent to the fulfilment of any of the homologation criteria.
Homologation effort: Limited assessment, Technical & Functional Testing, Penetration Testing.
Homologation C is applicable for the homologation of an Applicant that has not gone through any valid formal authorization/licensing process, nor is subject to any regulatory/supervisory requirements and that will use a Referenced Technical Solution Provider that has been homologated by the HB.
Homologation approach: Limited assessment.
Homologation E is applicable for the homologation of a Technical Solution Provider (TSP) that wishes to become a Referenced Technical Solution Provider (RTSP). Homologation effort: Limited assessment, Technical & Functional Testing, Penetration Testing
A Confirmation Homologation must be considered as an extra verification step in addition to any initial homologation mentioned above. Homologation is not blocking the adherence to the SRTP scheme and the start-up of services.
The re-Homologation in case the EPC has sufficient reasons to believe that a Participant/RTSP that has been homologated in the past is not providing RTP services in a way that ensures continuous compliance with the SRTP Rulebook and related documents.
A Complementary Homologation can be asked by the EPC to the SRTP scheme Participants, in cases of e.g. substantial changes to the SRTP scheme, new versions of the Rulebook and/or related documents that would require a further assessment on the capacities of a scheme Participant to keep offering scheme-compliant services.
The initiation of homologation can only be done if the Applicant or Technical Solution Provider:
In case of non-respect of these starting conditions, the homologation process can be refused or stopped. This may result in additional costs to finalise homologation.
The Applicant or Technical Solution provider should subscribe for a homologation wave. Three waves are annually defined:
Once the HB has received the signed contract and payment, the subscription is confirmed. The subscription must be completed at least a month before the start of the wave.
To become participant of the SRTP scheme, an Applicant triggers the adherence process towards the EPC, as described in the SRTP Rulebook and detailed under the related Adherence Guide. The EPC initially identifies the Applicant and evaluates whether it could be eligible to participate in the scheme. The EPC confirms the identification to the Applicant including the EPC reference number and the type of homologation to be applied.
A TSP must also contact the EPC prior to homologation for identification.
The acceptance by the EPC of the applicant/TSP is the basic condition to start the homologation process consisting of 7 main steps:
The identified applicant/TSP contacts the HB and requests for homologation. A Lead Assessor appointed by the HB will take contact and coordinate the Homologation process. As a first step, the Lead Assessor collects some basic company information. The applicant is also requested to do a self-assessment of the implementation status of requirements in line with the homologation type.
The HB shares a standard contract with the Applicant/TSP for signature. Once the contract is signed, the billing process is initiated. The payment is required before the start-up of assessment and testing.
The HB Lead Assessor organizes an online kick-off meeting with the Applicant/TSP. The main purpose of the meeting is to check readiness for homologation. The HB will clarify the homologation process, the approach and the information (questionnaires and documents) to be provided.
The HB and the Applicant/TSP agree on planning considering that the HB is bound to perform the homologation process within the wave period.
As agreed during the kick-off meeting, the Applicant/TSP delivers the requested information to the HB before the start of the wave. Conform the type of homologation, questionnaires and supporting documents must be provided via the online tools to ensure security and confidentiality of the information provided.
All information and documents must be complete, accurate and relevant, provided in the English language.
The HB performs an initial check on the information delivered. The Applicant/TSP receives an acknowledgement of receipt or complementary requests if necessary.
If the information is accepted, the execution of the homologation can start.
On receipt of the correct information, the HB reviews information and supporting documents. Depending on the type of homologation, the potential subjects are:
In case of impediments or non-compliances the Applicant/TSP will be informed immediately to allow remediation which should be done before the end of the planned evaluation period to avoid a “Fail”.
The HB executes several tests in line with the specifications provided by the EPC. These tests include.
For testing purposes, the HB uses a dedicated platform and tools.
In case of impediments or non-compliances the Applicant/TSP will be informed immediately to allow remediation which should be done before the end of the 1-month period to avoid a “Fail”.
When assessments and tests are completed, a report is delivered. There are two conclusions possible :
Once the homologation process is finished, the successful Applicant, provides the homologation report and certificate of homologation to the EPC to continue with the adherence process. If all conditions are met, the Applicant becomes participant of the SRTP scheme.
The TSP who successfully passes the homologation, provides the homologation report and certificate of homologation to the EPC. The EPC will publish a list of TSPs, who successfully passed the homologation, on the EPC website as “Referenced Technical Solution Providers”.
In case of a negative outcome of the Confirmation Homologation the EPC might cancel scheme participation or remove the TSP from the list of RTSP.
The Homologation Body is officially mandated by the EPC to:
The EPC as Scheme Manager is responsible for:
The SRTP Applicant/TSP undertakes the following tasks:
The homologation types are described in chapter : Homologation types. The applicable homologation type is defined by the EPC and will be indicated in the contract to be signed between Applicant/TSP and the HB.
The fees 2025, excluding any applicable taxes, are:
Applicable for SRTP Applicants
Homologation A
Homologation B
Homologation C
We would like to emphasize that the content of the documents and links presented here is purely informative and intended for guidance purposes only. While we make every effort to ensure the accuracy and relevance of the information provided, it is essential to understand that these materials do not hold any legal binding.
For matters that involve contractual agreements or legal obligations, only the specific terms outlined in the official contract will be considered binding between parties.
Important: the documents below will be submitted to a review in October/November 2025
Documents:
Links:
All information related to the SRTP scheme is available on the EPC website. For any further information about the SRTP scheme or the adherence to the scheme, please contact the European Payments Council. Address your questions via mail to: srtp@epc-cep.euAll information related to the homologation is available on the Homologation Body website. For a homologation request or for information related to the homologation process, address your mail to: SRTPHomologation@soprasteria.com