ASPSP Definition: What It Means in Open Banking

An ASPSP (Account Servicing Payment Service Provider) is the regulated institution that holds the customer’s payment account — typically a bank, building society, or payment institution — and exposes access to that account for payments and data when the customer consents. In EU open banking under PSD2, ASPSPs are the “account side” of the API relationship; fintechs and aggregators that connect to them are usually TPPs (Third Party Providers). If you are evaluating open banking integrations, you rarely contract with ASPSPs one by one — you integrate a licensed provider that already connects to hundreds of them.

ASPSP (Account Servicing Payment Service Provider): A payment service provider that provides and maintains a payment account for a customer — for example a current account at a bank — and, under EU rules, must allow regulated third parties to access that account for payments or account information when the customer gives consent.

What does ASPSP stand for?

Account Servicing Payment Service Provider is the full phrase. “Account servicing” means the institution is where the account lives: it holds balances, executes transfers, and is responsible for that account under banking and payment rules. “Payment service provider” places ASPSPs in the same regulatory family as other licensed payment firms — but the defining job is custody of the account, not building apps on top of someone else’s bank.

In plain terms: when a user pays by bank or shares transaction data, the ASPSP is their bank (or the licensed firm that issued that account). Everyone else in the chain connects to the ASPSP’s APIs or channels.

Where the ASPSP definition comes from (EU PSD2)

The term is formalised in European payments law — the Payment Services Directive (PSD2) and related technical standards — as part of how regulators split roles in open banking.

The European Banking Authority (EBA) describes the framework: ASPSPs must offer secure interfaces so licensed third parties can provide payment initiation and account information only with the customer’s consent. ASPSPs do not “sell” open banking to merchants; they enable regulated access so customers can use other apps and services with accounts they already hold.

That split matters for product teams:

Role	Who	What they do
ASPSP	Bank, building society, many neobanks	Holds the account; provides access APIs
AISP	Licensed third party	Reads account information (with consent)
PISP	Licensed third party	Initiates payments from the account (with consent)
TPP	Umbrella term	Any licensed third party (AISP, PISP, or both)

Your company is usually neither an ASPSP nor a TPP unless you hold a licence. You integrate a TPP that already connects to ASPSPs in each country.

ASPSP vs TPP — who you actually integrate

ASPSPs are the thousands of institutions per country. TPPs (or the commercial “open banking providers” you shortlist) aggregate those connections behind one API.

Customer → consents in banking app (ASPSP)
         → ASPSP interface
         → TPP / aggregator (licensed)
         → Your product (payments, verification, data)

Implications for buyers:

• Coverage is always “which ASPSPs does my provider reach in country X?” — not “does open banking work in Europe?”
• Behaviour differs per ASPSP: redirect flows, name fields on verification, SEPA Instant support, error codes.
• Contracts are typically with the TPP; the ASPSP relationship is the provider’s regulatory and technical problem.

For a developer-oriented view of picking that layer, see best open banking API providers for developers. For how fintech products use the stack end to end, see open banking for fintech.

Is ASPSP only used in Europe?

Yes — as a formal regulatory label. ASPSP comes from EU and UK open banking rules (PSD2 and the UK implementation). Outside those frameworks, providers may still say “ASPSP” in API docs when they mean any connected bank that holds the account, but the legal obligations in the definition are tied to European payment services law.

The underlying role is universal: someone must host the payment account. In open banking product work, that institution is the ASPSP; your integration partner is almost always the TPP that reaches many of them.

Examples of ASPSPs

Any licensed institution that provides payment accounts to customers can be an ASPSP, including:

• Retail and business banks — current accounts used for salaries, invoices, and cards-linked DDA
• Neobanks with banking licences — they hold accounts even when the UX feels like an app-only brand
• Some payment institutions — where regulation treats them as account servicers for specific products

Usually not ASPSPs on their own: pure card networks, merchants, or your SaaS product — unless you hold a banking or payment institution licence and operate customer accounts.

Neobanks and challengers are ASPSPs when they are the account host; they become TPPs only when they also offer regulated third-party services into other banks’ accounts.

Why the ASPSP definition matters when you choose a provider

You will not negotiate separately with 400 ASPSPs. You will fail go-live if your provider’s ASPSP coverage misses your customers’ banks.

Concrete reasons teams keep this definition handy:

1. Onboarding and verification — name-and-IBAN checks depend on what each ASPSP returns after consent (instant account verification quality varies by bank).
2. Payments — Pay by Bank success rates and settlement speed are ASPSP-specific.
3. Support and incidents — outages are often “Bank X ASPSP degraded,” not “open banking is down.”
4. Roadmaps — entering France is not entering Germany; each country is a new ASPSP mix.

When you compare providers, ask for an institution list filtered by country and product (payments, data, verification), not a single global number.

Frequently Asked Questions

What is the ASPSP definition in open banking?

An ASPSP is a payment service provider that provides and maintains a payment account for a customer — usually a bank — and must allow regulated third parties to access that account for payments or account information when the customer consents, under EU PSD2-style rules.

What is the difference between ASPSP and TPP?

The ASPSP holds the customer’s account (the bank side). A TPP is a licensed third party that accesses that account on the customer’s behalf — for example to initiate a payment or read balances. Businesses typically integrate a TPP that connects to many ASPSPs.

Is a neobank an ASPSP or a TPP?

It can be either or both. If it holds customer accounts under a banking licence, it is an ASPSP for those accounts. If it also offers services that connect to other banks’ accounts, it acts as a TPP for those flows. Many neobanks do both.

What is the difference between ASPSP and AISP?

ASPSP is the account-holding institution. AISP (Account Information Service Provider) is a type of TPP licensed to read account information with consent. The AISP connects to ASPSPs; it does not replace them.

What is the difference between ASPSP and PISP?

ASPSP holds the account. PISP (Payment Initiation Service Provider) is a TPP licensed to initiate payments from that account with consent. The payment still moves through the ASPSP’s infrastructure.

Is ASPSP only used in Europe?

As a formal regulatory label, yes — ASPSP comes from EU and UK open banking rules. Providers may still use the term in documentation for any connected bank that holds the account, but the legal definition is tied to European payment services law.

Why do provider websites list “ASPSP coverage”?

It means how many account-holding institutions they can reach in each country for payments, data, or verification — and which products work per bank. Your evaluation should match that list to where your customers bank.

Conclusion

ASPSP definition, in one line: the regulated institution that hosts the customer’s payment account in open banking. TPPs and aggregators connect to ASPSPs so your product can pay, verify, or read data without building hundreds of bank integrations. When you move from glossary to vendor choice, filter providers by your ASPSPs (your users’ banks), not by geography labels alone.