TPP Directory 2026: Licensed Third Party Providers in Europe

A TPP (Third Party Provider) is a company authorized under Open Banking regulations to access bank accounts and/or initiate payments on behalf of customers. TPPs include AISPs (Account Information Service Providers) that can view account data, and PISPs (Payment Initiation Service Providers) that can initiate payments. All TPPs must be licensed by financial regulators.

To become a licensed TPP, you must apply to your national financial regulator (e.g., FCA in UK, BaFin in Germany). Requirements include demonstrating technical security measures, professional indemnity insurance, governance arrangements, and capital requirements. The process typically takes 3-12 months. Alternatively, you can use an agent or 'TPP-as-a-Service' provider.

AISP (Account Information Service Provider) licenses allow you to access and aggregate account data with customer consent—used for apps like budgeting tools or credit scoring. PISP (Payment Initiation Service Provider) licenses allow you to initiate payments from customer accounts—used for 'Pay by Bank' checkout experiences. Many TPPs hold both licenses.

If you're building an app that directly accesses bank APIs, yes—you need TPP authorization. However, you can avoid licensing by using an API aggregator (like Plaid, Tink, or TrueLayer) that already holds the necessary licenses. They act as the regulated entity, and you operate under their license through an agency arrangement.

You can verify TPP licenses through official regulator registers: the FCA Register (UK), EBA Register (EU-wide), or national regulator databases. Each licensed TPP has a unique registration number. The Open Banking Directory (UK) also maintains a list of enrolled participants. Always verify before sharing data with any third party.