TPP Infrastructure-as-a-Service

This section provides comprehensive documentation for regulated Third-Party Providers (TPPs) such as Payment Initiation Service Providers (PISPs), Account Information Service Providers (AISPs), and Credit Institutions (i.e. banks) using or planning to use Enable Banking API relying on their own credentials when connecting to ASPSPs' PSD2 APIs.

When providing to regulated TPPs an Infrastructure-as-a-Service platform, Enable Banking acts as a Technical Service Provider (TSP) within the Open Banking ecosystem. In this scenario, Enable Banking is completely invisible for end-users (Payment Service Users - PSUs). While harmonising the data flow between a TPP and ASPSPs and providing unified authentication flows for PSUs, Enable Banking does not bing own terms of service to PSUs and does not interfere with the contractual relationship between them and the TPP. For the regulated TPPs Enable Banking offers a fully managed Infrastructure-as-a-Service platform that provides:

• Single-tenant dedicated environments ensuring complete isolation for each regulated TPP;
• Cryptography offloading for eIDAS certificates through the eIDAS Broker or HSM services;
• Onboarding to ASPSPs fully managed by Enable Banking;
• Monitoring and alerting for integrated ASPSPs;
• Analytics and reporting covering payment initiation and account information services;
• DORA compliance for digital operational resilience.

This documentation is designed to help TPPs understand and effectively utilise Enable Banking's infrastructure while maintaining the highest standards of security, compliance, and operational excellence.

If you are not yet authorised as a Third-Party Provider, we will be happy to assist you by providing the necessary guidance and support related to techological and information security aspects of TPP operations. We recommend that you first review our documentation on Operational Risk Management for TPPs.