SEPA Payment Account Access (SPAA) is a scheme managed by the European Payments Council (EPC) that sets common rules for the exchange of payment account data and the initiation of payments between the providers that hold payment accounts and third parties, for services that go beyond the minimum access required by law. Its rulebook defines the roles, the legal relationships, the business conditions and the technical requirements for so-called premium or value-added access to payment accounts through an application programming interface (API).
The second Payment Services Directive (PSD2) obliges an account servicing payment service provider (ASPSP) to give licensed third parties free access to payment accounts for account information and payment initiation, but only for a basic set of functions. SPAA covers the space beyond that floor. It lets the provider holding the account and a third party agree, under one multilateral framework, on additional services for which the account holder's provider may be paid. Participation is voluntary, and the scheme sits alongside PSD2 rather than replacing it.
Background
PSD2 applied from January 2018, and its technical standards on strong customer authentication and secure communication from September 2019. Banks across Europe built dedicated interfaces, mostly APIs, for account information service providers and payment initiation service providers. Access had to be free of charge and could not depend on a contract between the bank and the third party.
Market participants argued that this model gave banks little reason to invest in richer APIs, and left third parties facing a patchwork of bilateral agreements and different technical specifications for any feature outside the legal minimum. The Euro Retail Payments Board, chaired by the European Central Bank, set up a working group to define a SEPA API access scheme, and the ERPB then asked the EPC to take on the role of scheme manager. The EPC published the first SPAA rulebook, version 1.0, in November 2022, and an updated version 1.1 took effect on 30 November 2023.
Roles in the scheme
- Asset holder. The participant, typically a bank acting as ASPSP, that holds the payment account and exposes data and functions, called assets, through its API.
- Asset broker. The participant that uses those assets to serve its own customers, such as a third-party provider, a fintech or another bank.
- Scheme manager. The EPC, which maintains the rulebook, processes adherence and keeps a register of participants.
The account holder, a consumer or business, does not join the scheme directly but must give consent before data are shared or payments initiated, as under PSD2. Asset holders and asset brokers adhere to the rulebook, which gives them a common contractual basis, so that a broker connected to many holders does not need a separate contract with each one.
The rulebook describes a set of assets beyond PSD2 access, organised so that holders can choose which to offer. The kinds of service discussed for the scheme include initiating future-dated and recurring payments, richer account information such as longer transaction histories, checks on available funds and payment initiation with a stronger assurance of the outcome. Such features resemble the commercial variable recurring payments being developed in UK open banking.
The scheme does not fix prices. It establishes that holders may be paid for premium assets and sets out how charges and liability are handled, but the level of any fee is a commercial decision. On the technical side, the scheme sets functional and security requirements and relies on existing market API specifications rather than creating a single new standard, which allows banks to reuse the open banking APIs they built for PSD2.
Relationship with PSD3 and data access proposals
SPAA does not change any legal right. Third parties keep their free PSD2 access, and a provider that does not adhere is not penalised. In June 2023 the European Commission proposed a third Payment Services Directive (PSD3) and a Payment Services Regulation to replace PSD2, together with a regulation on financial data access covering data beyond payment accounts. The data access proposal relies on industry-run data sharing schemes in which data holders may be compensated, and SPAA is often cited as an early example of that model.
Adoption and criticism
The value of the scheme depends on whether enough holders and brokers join and build to it. Third-party providers have argued that paid premium access must not be used to weaken the free PSD2 interfaces, while banks have argued that without payment there is no reason to build beyond the legal minimum. The outcome also depends on how far national communities and existing API initiatives align with the SEPA-wide framework rather than keeping their own arrangements.
External links
Ref 1230000069