SEPA Request-to-Pay (SRTP) Scheme Homologation  

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 Benelux & Galitt have 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

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: https://www.europeanpaymentscouncil.eu.

SEPA Request-to-Pay Scheme

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

Scope SRTP process

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.

 

SRTP process: Request-to-Pay and Acceptance or Refusal of the Request-to-Pay

 

Homologation

An Applicant, who wishes to participate in the SRTP scheme, needs to be homologated. The Homologation Body 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 of a Technical Solution Provider). 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 a RTSP will be eligible to a more limited homologation (see chapter 2 : Homologation types).

Homologation types

Different types of homologations have been defined. The number of requirements to be verified might vary accordingly. The testing efforts are equal for all types of 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.

Standard Homologation

The Standard Homologation is applicable to Applicants that have not gone through any valid formal authorization/licensing process, nor are subject to any regulatory/supervisory requirements, nor have been tested by a recognized testing entity, nor are relying on a Referenced (homologated) Technical Solution Provider.

Simplified Homologation A

Simplified Homologation is applicable to Applicants that have already gone through a valid formal authorization/licensing process, and/or are subject to specific regulatory/supervisory requirements. This applicant is not relying on a Referenced (homologated) Technical Solution Provider.

Simplified Homologation B

Simplified Homologation B is applicable to Applicants that are using a Referenced Technical Solution Provider and have not gone through any valid formal authorization/licensing process, nor are subject to any regulatory/supervisory requirements, nor have been tested by a recognized testing entity.

Simplified Homologation A+B

Simplified Homologation applicable to Applicants that are using a Referenced Technical Solution Provider and have already gone through a valid formal authorization/licensing process, and/or are subject to specific regulatory/supervisory requirements.

Homologation of a Technical Solution Provider

Homologation of a technical infrastructure, offered by a Technical Solution Provider (TSP), that can be used by the SRTP scheme Applicants to send/receive SRTP messages in accordance with the rules of the scheme. This homologation can be asked by any Technical Solution Provider at their discretion.

The EPC publishes a list of Referenced Technical Solution Providers (RTSP) on its website.

Confirmation Homologation

A Confirmation Homologation must be considered as an extra verification step in addition to any initial homologation mentioned above. As the SRTP services are not yet in production, the Applicant/TSP might not be able to effectively demonstrate some of the homologation requirements within the range HP-R14 to HP-R30. Any non-compliance of SRTP system related requirements HP-R1 to HP-R13 is out of scope as the Confirmation Homologation is not blocking the adherence to the SRTP scheme and the start-up of services.

Re-Homologation

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.

Complementary Homologation

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.

Homologation process

Apply for adherence to the SRTP scheme

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 applying for a homologation must first announce its compliance with the SRTP scheme by addressing a disclosure letter to the EPC.

Initiate the homologation

The identified Applicant or TSP will receive a mail from the HB with instructions to connect to a secured online tool supporting the homologation process and the exchange of information. Once access is created, the Applicant/TSP is requested to fill in general information and a self-assessment. A Lead Assessor appointed by the HB will take contact and coordinate the Homologation process.

Contract & Billing

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.

Kick-off

The HB Lead Assessor organizes an online kick-off meeting with the Applicant/TSP. The main purpose of the meeting is to clarify the homologation process, approach and 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 one month approximately after receipt of all required information during the period of six months after the identification. 

Deliver information

As agreed during the kick-off meeting, the Applicant/TSP delivers the requested information to the HB by the planned date (+/- 1 month). 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.

Review of information

On receipt of the correct information, the HB reviews information and and supporting documents. Depending on the type of homologation, the potential subjects are:

  • Performance and availability of the infrastructure
  • Fraud
  • Testing capabilities
  • Educating customers (Payees & Payers)
  • Educating staff members
  • Documentation
  • Business Continuity Plan (BCP)
  • Subcontractor management
  • Monitoring (Service Level Agreements)

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”.

Execution of testing

The HB executes several tests in line with the specifications provided by the EPC. These tests include:

  • Technical and functional testing
  • Penetration testing

For testing purposes, the Homologation Body 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”.

Reporting & certification

When assessments and tests are completed, a report is delivered. There are two conclusions possible:

  • “Pass” – the Applicant/TSP is conforming to the requirements of the SRTP rulebook. In this case, the report and certificate are addressed to the Applicant/TSP.
  • “Fail” – the Applicant/TSP is not conforming to some of the requirements of the SRTP rulebook and should initiate a new homologation request. In this case the report is addressed to the Applicant/TSP.

The HB also shares the report and certificate with the EPC. Testing reports are delivered to the Applicant/TSP only. Only the overall conclusion will be mentioned in the homologation report.

Finalize the onboarding to the SRTP scheme

The Applicant, who successfully passes the homologation, 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”.

Roles and Responsibilities

The main responsibilities of the actors in the homologation process

Homologation Body

The Homologation Body is officially mandated by the EPC to:

  • Perform the necessary reviews, assessments and testing to ensure that a SRTP Applicant/TSP has the technical, operational, security and business continuity capabilities to conform with the SRTP scheme requirements as defined by the SRTP Rulebook.
  • Validate that the SRTP Applicant/TSP complies with the SRTP scheme Rulebook and the related Implementation Guidelines.
  • Be the primary contact for the SRTP Applicant/TSP for homologation purposes.
  • Set up and maintain the homologation framework and process.
  • Ensure effective communication with the Applicant/TSP and the EPC.
  • Deliver a Homologation Report and in case of successful Homologation a Certificate of Homologation.

    European Payment Council (EPC) 

    The EPC as Scheme Manager is responsible for:

    • The overall adherence process, from processing the initial adherence request of an Applicant to its inclusion in the Register of Participants.
    • Decision about the type of homologation to be applied for the Applicant.
    • In case of a TSP, collect the disclosure letter of intent to become an SRTP scheme compliant TSP.
    • The final decision on whether an Applicant can be included in the SRTP scheme.
    • Register the accepted scheme Participants in the Register of Participants.
    • Publish the list of Referenced Technical Solution Providers on the website.

    The SRTP Applicant or Technical Solution Provider

    The SRTP Applicant/TSP undertakes the following tasks:

    • Makes itself familiar with the SRTP scheme Rulebook and related documents and take the appropriate measures to ensure compliance with the SRTP scheme Rulebook requirements.
    • Contact the EPC to kick-start the adherence process. (Applicants only)
    • Once initially identified by the EPC, proceed with the homologation as instructed by the EPC. (Applicants only)
    • Provide a self-declaration of compliance with the SRTP scheme. (TSP’s only)
    • Sign Applicant/TSP contract with the HB and execute payment to the HB before the start of the assessments or testing.
    • Provide all the information/documents/evidence requested by the HB for the Homologation Process, complete and in a timely manner.
    • Provide the requested conditions to allow the execution of tests.
    • Identify and inform the HB on confidential information.

    Homologation types and fees

    Types of homologations

    The homologation types are described in chapter 2. 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.

      Homologation fees 

      The fees, excluding any applicable taxes, are:

      Applicable for SRTP Applicants

      • Standard Homologation: € 25.111
      • Simplified Homologation A: € 21.161
      • Simplified Homologation B: € 22.741
      • Simplified Homologation A+B: € 20.108
      • Confirmation Homologation (included in homologation fee): -

      Applicable for Technical Solution Providers

      • Homologation of a Technical Solution Provider: € 21.858
      • Confirmation Homologation (optional) : € 1.411

      Applicable for SRTP Applicants and Technical Solution Provider

      • Re-Homologation: Case-by-case
      • Complementary Homologation: Case-by-case

      Documents and links

      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.

      Documents: 

      SRTP Homologation Process Guide - (pdf, 1 Mo)
      Homologation types & requirements (v2.0) - Excel (38 kb)
      Detailed SRTP scheme homologation requirements (2024.02.15) - Excel (267 kb)
      Technical & Functional Testing Homologation Guide (v3.1) - pdf (559 kb)
      Technical & Functional Testing Readiness CheckList (v2.0) - Excel (26 kb)
      Technical & Functional Test Plan (v5.0) - Excel (105 kb)
      Penetration Testing Homologation Guide (v1.0) - pdf (400 kb)
      Penetration Testing Homologation Checklist (v1.0) - Excel (22kb)

      Links:

      Contact Details

      For any further information about the adherence to the SRTP scheme, please contact the European Payments Council.

      For homologation request or for information related to the homologation process, address your mail to:  SRTPHomologation@soprasteria.com.

       

      European Payments Council