Common requirements for CIs, PIs and EMIs
Regardless of license type, all financial institutions must set up the right infrastructure and connectivity, while meeting a shared set of requirements to gain and retain their direct SEPA participant status.
1. Establishing the right infrastructure
Institutions seeking direct SEPA access must first ensure their infrastructure is equipped to meet the stringent criteria set by CSMs and their central banks. Core obligations include:
Settlement in central bank money: to guarantee finality of settlements and mitigate counterparty credit risks, direct SEPA participants must settle transactions exclusively in central bank money via systems like TARGET2 or TIPS. This process must comply with ECB policies and the Settlement Finality Directive (SFD). Participants must also maintain a main cash account (MCA) at their national central bank. While CIs already do this, it's new for PIs and EMIs.
Real-time reconciliation and status reporting: institutions must also ensure real-time updates of payment and settlement statuses with ISO 20022 messaging standards. Additionally, monitoring tools capable of detecting and flagging failed or delayed settlements instantly are required.
Anti-fraud and exception handling: although the EPC Rulebooks don't mandate specific tools, participants must have implemented real-time fraud detection, sanctions screening and exception handling procedures. This includes flagging or rejecting suspicious transactions according to AML/CFT requirements.
Contingency infrastructure: all financial institutions must establish geographically separate disaster recovery sites with live mirroring. To maintain access to TIPS/RT1 during outages, they will also need backup NSPs (e.g. SWIFTNet + SIA / NEXI) or have geographically separated connections with a single NSP (e.g. two independent Swift lines from different data centres). Furthermore, fallback protocols – predefined flows to reroute, queue, or cancel payments – are essential during major incidents.
2. Connecting via a certified NSP
Connectivity to central bank payment systems (e.g., TARGET2, TIPS) and certain CSMs (e.g., RT1) must be established through a certified network service provider. The NSPs currently in operation are SWIFTNet and SIA/Nexi.
Each provider has distinct onboarding lead times, technical documentation requirements and security compliance standards, which range from PKI infrastructure and hardware security module (HSM) integration to fallback obligations.
3. Applying to and onboarding with a CSM
Accessing SEPA schemes as a direct participant starts with aligning with both the EPC Rulebooks for all schemes (SCT, SCT Inst, and SDD) and CSM-specific rulebooks. Each CSM sets its own admission criteria, meaning both CIs and PIs / EMIs must undergo specific onboarding and technical certification tailored to that CSM.
For example, EBA Clearing’s RT1 demands a "Capacity Opinion”, which is a formal statement certifying that the institution's infrastructure can handle RT1 volumes. Applicants must also maintain continuous TARGET / TIPS access, and adhere to EBA Clearing's rulebooks. In the case of license revocation, insolvency, or serious operational breaches, RT1 can well suspend access and exclude the institution from its system.
Similarly, the Eurosystem’s TIPS has its own participation criteria, which include holding a TARGET-compliant dedicated cash account (DCA) and passing TARGET2-related technical prerequisites. Like RT1, and indeed all CSMs, participants must support instant payments around the clock, every day.