Treezor Open Banking

Open Banking allows authorized third parties to securely access bank account data and initiate payments on behalf of users, with their explicit consent. It's regulated by PSD2 in Europe to promote competition and innovation in financial services.

Key Concepts

Account Servicing Payment Service Provider (ASPSP): The bank holding the account. Treezor acts as the ASPSP, providing APIs for secure data access.

Third Party Provider (TPP): External services that access account data or initiate payments through Open Banking APIs.

Payment Service User (PSU): The end user who owns the account and grants consent.

Reading – Glossary

Find out more about open banking actors in the Glossary.

Who Are You?

I'm a Third Party Provider (TPP)

You want to access Treezor account data to build financial services (budgeting apps, aggregators, payment services).

Start here:

1. TPP Introduction – Prerequisites and registration
2. Authentication – OAuth2 flow
3. AISP Implementation – Access account data

I'm a company using Treezor services

You're a Treezor client providing Open Banking services under your brand. You need to authenticate your users when TPPs request access.

Start here:

1. Client Introduction – Your role and responsibilities
2. Client Implementation – SCA authentication setup

API – API References available

• OAuth2 API – Authentication endpoints
• AISP API – Account information endpoints
• Consent API – Consent management