Payment Initiation Services Under PSD2: A Practical Guide
How payment initiation providers are authorised in the EU and UK, how consent and strong authentication work, who refunds a failed payment, and what PSD3 changes.
Key takeaways
- A payment initiation provider needs a payment institution authorisation, EUR 50,000 of initial capital if it offers payment initiation only, and professional indemnity cover sized by an EBA formula
- Payment initiation triggers strong customer authentication every time; the 90-day relief in the RTS covers account information access, not moving money
- The payer's bank owes the refund on an unauthorised transaction, normally by the end of the next business day, while the payer's exposure on a lost instrument is capped at EUR 50 unless fraud or gross negligence applies
- In the agreed PSD3 and PSR package the licensing layer stays in a directive while conduct rules become directly applicable regulation, with application dates fixed only after publication in the Official Journal
What payment initiation is — and what it is not
A payment initiation service provider (PISP) builds a payment order on the payer's behalf and passes it to the bank that holds the payer's account. PSD2 defines the activity as initiating a payment order at the user's request in respect of a payment account held at another payment service provider (Directive (EU) 2015/2366, Article 4(15)). The directive has applied across the EEA since 13 January 2018 (Article 115 of the same directive).
That legal definition drives the operations. A PISP never holds or settles money: it constructs the order, transmits it, and the payer's bank moves the funds. In the euro area these flows run on SEPA Credit Transfer or SEPA Instant Credit Transfer, and instant credit transfers in euro now sit alongside the SEPA Regulation under Regulation (EU) 2024/886, which obliges providers of standard euro credit transfers to offer instant payments and to verify the beneficiary.
Two consequences follow immediately, and both shape product design:
- There is no chargeback right. A credit transfer can no longer be revoked once the payee's bank has received it (Article 80).
- Refunds are new payments. A merchant refund is a fresh outbound credit transfer, not a reversal of the original, so reconciliation and refund engineering must be built deliberately.
Payment initiation is a different service from account information (AIS). An AISP reads balances and transaction history; it cannot move money. The two are often held by the same firm, but they carry different capital, consent cycles and liability. For how the access layer is evolving, see our overview of open banking APIs in the EU and UK.
The licence: what a payment initiation provider must show
Payment initiation is a regulated payment service in the EU, so a firm must be authorised as a payment institution in its home member state. The core requirements are laid down in the directive itself.
- Initial capital of EUR 50,000 where the firm provides only the service listed at point (7) of Annex I (payment initiation). Money remittance sits at EUR 20,000 and the wider payment services at EUR 125,000 (Article 7, read with Annex I).
- Registration, not authorisation, for account information alone. An AIS-only firm registers and faces no initial capital requirement (Article 5(3)), which is why many providers pair a payment initiation authorisation with an AIS registration.
- Professional indemnity insurance or a comparable guarantee, which is a precondition of authorisation rather than an afterthought. It must cover the firm's liabilities under Articles 73, 89, 90 and 92 of PSD2 (EBA/GL/2017/08, Guideline 1.2(a)). The guidelines apply from 13 January 2018 (EBA press release).
- Passporting. Once authorised at home, the firm can serve the rest of the EEA through freedom of services or establishment and appears in the EBA register.
How the insurance amount is actually calculated
There is no flat euro figure. The EBA guidelines require the minimum cover to be built from a formula: the amount reflecting the risk profile criterion, plus the amount reflecting the type of activity criterion, plus the amount reflecting the size of activity criterion, expressed as a figure per year (Guideline 3.1 and 3.4). The indicators feeding those criteria include the value of refund requests and the number of payment transactions initiated by the provider, and the values are expressed in euro, with non-euro member states allowed to convert to their national currency (Guidelines 3.3 and 5 to 7).
The practical reading for a product team is blunt: the policy limit is a hard ceiling on how much payment value the firm can safely process, and a volume-driven formula means an ambitious growth plan raises the cover you must buy and fund.
What the authorisation file contains
Applicants describe a programme of operations, a business plan showing how capital requirements are met, governance and internal controls, risk management, anti-money laundering procedures, security policies, incident reporting and outsourcing or ICT contracts (Article 5 of the directive). Payment institutions also sit inside the EU's digital operational resilience rules, including incident reporting and third-party risk management (Regulation (EU) 2022/2554); our DORA explainer covers what that means in practice.
The UK route
After Brexit the UK framework is separate. Authorisation runs under the Payment Services Regulations 2017, and Part 1 of Schedule 3 to those regulations reproduces the same tier structure: the table in the regulations as in force sets the payment initiation tier at EUR 50,000, money remittance at EUR 20,000 and the wider services at EUR 125,000, with the amounts expressed in euro (SI 2017/752, Schedule 3). Where a firm offers more than one service, the higher figure applies rather than the sum. The FCA sets out how it assesses applications in its payment services approach document. An EEA authorisation no longer reaches UK customers and vice versa, so firms serving both markets need both permissions.
Consent, authentication and the 90-day exemption
Strong customer authentication (SCA) applies to every payment initiation, not just to the first one in a session. Article 97 of the directive requires SCA where the payer initiates an electronic payment transaction, and for remote transactions the authentication code must be dynamically linked to the amount and the payee, so that changing either invalidates it (Delegated Regulation (EU) 2018/389, the RTS on SCA and secure communication, which applies from 14 September 2019).
The relief widely called the "90-day exemption" is narrower than the phrase suggests. Article 10 of the RTS allows banks to skip SCA only where a user or an AISP accesses the balance and the transactions of the last 90 days of an account, with SCA applied on first access and again once more than 90 days have elapsed since the last authentication (RTS Article 10). Regulation (EU) 2022/2360 then aligned how banks apply that 90-day boundary, because practice had diverged. Nothing in Article 10 exempts a payment; moving money from an account always needs fresh authentication, even inside a session opened to read data.
A well-built payment initiation journey therefore looks like this:
- Consent capture. The user chooses pay by bank and gives explicit, service-specific consent that is recorded and revocable.
- Redirect and authentication. The user authenticates on the bank's own domain; the provider never sees bank credentials.
- Order transmission. The provider sends the payment order, unaltered, to the bank.
- Execution and confirmation. The bank executes the credit transfer and both sides receive the status and the end-to-end identifier used for reconciliation.
On the bank side, the provider depends on non-discriminatory treatment of requests that identify the service as payment initiation (Article 67(3)(b)). On the provider side, the limits are strict: it must not hold user funds, must not modify the amount, payee or other feature of the transaction, must not store sensitive payment data, and must not use data for purposes beyond the requested service (Article 66). Real-time monitoring of conversion and bank errors is the control that keeps a provider inside its licence.
Liability: who refunds when a payment goes wrong
Payment initiation produces a liability pattern that is more favourable to the payer than card processing, and that shapes the commercial case for merchants.
| Situation | Who is on the hook | Rule |
|---|---|---|
| Unauthorised transaction | Payer's bank refunds, and no later than the end of the next business day | PSD2 Article 73(1) |
| Lost, stolen or misappropriated instrument | Payer bears at most EUR 50 | PSD2 Article 74(1) |
| Payer acted fraudulently, or failed their own duties with intent or gross negligence | Payer bears all losses | PSD2 Article 74(2) |
| Provider alters the amount, payee or another feature | Provider is liable and must compensate the bank; the insurance is the backstop | PSD2 Articles 89 and 90, EBA/GL/2017/08 |
| Bank receives a correct order and executes it late or wrongly | Payer's bank | PSD2 Articles 89 and 90 |
| Customer wants money back after delivery | New outbound credit transfer; no reversal of the original | PSD2 Article 80 |
The design intent is that the account-servicing bank is the payer's front-line refund channel, while the provider's own exposure concentrates on order accuracy, security failures and the insurance it was required to buy. That makes the professional indemnity calculation above, not the licence fee, the real limit on how large a payment flow a provider can carry.
What merchants and product teams should build for
- Reconcile on bank identifiers. Capture the bank's end-to-end or transaction reference and the remittance information, not just your own order ID.
- Build refunds as outbound payments. There is no acquirer, no chargeback workflow and no settlement holdback to reverse (Article 80).
- Engineer for authentication friction. Every payment needs its own authentication, so timeout handling, retries and clear redirect UX are the main conversion levers.
- Cover multiple banks. Breadth of bank coverage, not one deep integration, determines what share of customers can actually pay this way; orchestration layers help route between providers (Payment Orchestration Platforms).
- Plan disputes as support work. Social-engineering losses on an authenticated transfer sit largely with the payer under PSD2, so they arrive as tickets rather than network claims. The UK has taken a separate route, with a mandatory reimbursement model for authorised push payment fraud run by the Payment Systems Regulator; it is not mirrored in the PSD2 liability regime.
The PSD3 and PSR roadmap
The replacement package is close to the end of the legislative process but not law yet. The European Parliament's legislative tracker records that Parliament and Council reached a provisional political agreement on PSD3 and the Payment Services Regulation on 27 November 2025, and that the text agreed in interinstitutional negotiations was approved in the ECON committee on 5 May 2026 (European Parliament legislative train).
Formal adoption and publication in the Official Journal still have to follow, and no application date is fixed until that publication happens; the rules then apply after a transition period. The direction of travel for providers is a single, largely directly applicable rulebook with the authorisation layer kept in the directive — which should narrow the interpretation gaps that today differ between member states. Until the regulation applies, PSD2 as amended remains the operative framework, and existing authorisations, insurance arrangements and interface integrations carry over in substance.
Risks and costs
- Capital and insurance. EUR 50,000 of initial capital is modest next to a banking licence, but the professional indemnity amount is formula-driven and rises with transaction volume and refund history, and the policy limit caps the payment value a provider can touch.
- Authorisation and supervision. Application and ongoing fees are set nationally and supervision intensity varies by member state; specialist legal, compliance and audit work is usually the larger cost line.
- Security and resilience. Authentication integrations, interface monitoring, incident reporting and DORA-aligned third-party risk management are permanent operating costs, not one-off projects.
- Thin economics. A SEPA credit transfer carries no interchange mechanism comparable to cards, where EU law caps interchange at 0.2% of the transaction value for consumer debit and 0.3% for consumer credit (Regulation (EU) 2015/751). Payment initiation pricing is negotiated rather than published as a scheme tariff and is typically charged per successful payment, so failed authentications and abandoned redirects cost money without generating revenue. We therefore describe the revenue model qualitatively: there is no centrally published, primary-source price list for this service.
- Fraud and liability. Authenticated push payments have no chargeback route, and merchant refunds are new outbound transfers that must be funded and reconciled (Articles 73, 74 and 80).
- Dependency risk. Conversion depends on bank-side availability and interface performance, and an outage at one large bank affects a disproportionate share of users; non-discriminatory access under Article 67(3)(b) is a legal right but a practical variable.
- Regulatory timing risk. PSD3 and PSR dates are projections until publication in the Official Journal, and supervisors will keep interpreting authentication exemptions differently in the meantime.
Bottom line
Payment initiation is a narrow, licensable activity: a firm registers to read account data, obtains a payment institution authorisation to move money, holds EUR 50,000 in initial capital where it offers only payment initiation, buys formula-sized professional indemnity cover, and then lives inside a strict prohibition set in which it never holds funds or alters the order.
Viewed as a complement to cards rather than a replacement, the trade-off for merchants is final, authenticated settlement against the loss of chargeback protection and the need to engineer refunds as outbound payments. For providers, the licence is the least of it: the insurance formula, bank-interface dependency and fraud operations are where the real cost sits — and the PSD3 package will reset parts of that framework once it is published.
Follow the shortlist
Following payments, banking and market-infrastructure change? Our global ETF and stock research watchlist is tracked daily. Premium members get the full list, the reasoning behind every entry and updates when entries change.
See premium accessInformation and education only, not investment advice.
Related
Stablecoin Regulation Compared: EU MiCA vs the US GENIUS Act
How MiCA and the GENIUS Act differ on who may issue payment stablecoins, what must back them, how redemption works and where depeg risk still sits.
FinTechTokenised Deposits vs Stablecoins: How Bank-Issued Money Differs
Tokenised bank deposits and reserve-backed stablecoins both move value on programmable rails, but they differ in legal claim, deposit insurance, balance-sheet treatment and risk.
FinTechInstant Payments for Small Business: FedNow, RTP, Zelle Compared
How FedNow, RTP and Zelle differ for US small businesses on speed, settlement finality, limits and cost, plus which emerging options fit SME cash flow.