Open banking in the Netherlands — AISP, PISP and PSD2 access
Open banking in the Netherlands is the right of a payment-account holder to let a licensed account information service provider (AISP) or payment initiation service provider (PISP) reach that account, a right Dutch law writes into Articles 7:522b and 7:522c of the Civil Code (BW) and backs with duties on the bank in the Besluit prudentiële regels Wft. The short answer to the most common question: a Dutch-based firm needs a DNB licence under Article 2:3a of the Wet op het financieel toezicht (Wft) for either service. There is no registration-only route and no small-firm exemption. AIS-only and PIS-only applicants get lighter prudential requirements, and DNB must decide within three months of a complete file. The Dutch rules have applied since 19 February 2019. Below: the statutory map, the licence, DNB’s unusually concrete rules on redirection journeys, the access-denial and liability mechanics, and where PSD3 and the Payment Services Regulation (PSR) stand.
Last reviewed: 8 November 2026
1. Where the Dutch open-banking rules sit
The Netherlands did not write a single payments act. It spread PSD2 (Directive (EU) 2015/2366) across four instruments, and a firm that only reads the Wft will miss half of its obligations:
| Instrument | Provision | What it does for AIS and PIS |
|---|---|---|
| Wft | Art. 1:1 | Defines betaalinitiatiedienst and rekeninginformatiedienst and the providers of each |
| Wft | Arts. 2:3a, 2:3b | Licence obligation, licence tests, AIS/PIS carve-outs, three-month decision period |
| Besluit prudentiële regels Wft (Bpr) | Art. 24(2)-(3) | Professional indemnity insurance or a comparable guarantee |
| Bpr | Arts. 26h-26k | Strong customer authentication, PISP and AISP conduct, the bank’s duties towards both |
| Bpr | Art. 26e | Explicit consent before a PSP accesses personal data (AIS-only firms excluded) |
| Civil Code, Book 7, Title 7B | Arts. 7:522a-c, 7:523(5)-(8) | Funds confirmation, user access rights, the bank’s right to deny a provider access |
| Civil Code, Book 7 | Arts. 7:528(4)-(5), 7:545a | Refunds and the PISP’s liability towards the bank |
| Besluit Gedragstoezicht financiële ondernemingen Wft (BGfo) | Arts. 59c(2), 71ba | What a PISP must tell the payer before and after initiation |
The access right belongs to the user: Article 7:522b BW lets a payer use a PISP and Article 7:522c BW lets a user use account information services, in each case only where the account is accessible online. The bank’s matching duties sit in Article 26k Bpr.
2. The DNB licence: one route, two lighter variants
Article 2:3a(1) Wft forbids anyone with a seat in the Netherlands from carrying on business as a payment service provider without a DNB licence. DNB’s own guidance on AIS is blunt: an AISP must hold a licence, and the activity cannot be carried out under an exemption. The Dutch exemption scheme for small payment firms does not cover payment services 6, 7 and 8, so money remittance, payment initiation and account information all need the full licence. Firms used to the PSD2 “registration” label for AISPs should note that in Dutch law this is a licence, and the holder becomes a betaalinstelling.
What changes is the content of the tests in Article 2:3b(1) Wft:
| Licence test (Art. 2:3b(1) Wft) | Full PI | PIS only | AIS only |
|---|---|---|---|
| Fit and proper management, integrity policy, two day-to-day policymakers, transparent control structure, sound operations (a-f) | Yes | Yes | Yes |
| Safeguarding of funds, Art. 3:29a (g) | Yes | No (Art. 2:3b(4)) | No (Art. 2:3b(5)) |
| Minimum own funds, Art. 3:53 (h) | Yes | Yes: EUR 50,000 initial capital under PSD2 Art. 7(b) | No (Art. 2:3b(5)) |
| Ongoing solvency, Art. 3:57 (i) | Yes | No (Art. 2:3b(4)) | No (Art. 2:3b(5)) |
| Professional indemnity cover (Bpr Art. 24) | Not as such | Yes, for liability under BW 7:528, 7:545a, 7:547 | Yes, for unauthorised or fraudulent access to account data |
Applications go in through DNB’s Digitaal Loket Toezicht. Article 2:3b(7) Wft gives DNB three months from receipt, or three months from the last missing document if the file was incomplete. Article 2:3b(2) adds that DNB licenses only if at least part of the business will be carried on in the Netherlands, so a letterbox entity will not pass. A bank or e-money institution can provide AIS and PIS under its existing licence (Art. 2:3a(2) Wft).
AIS firms may run other businesses, but DNB’s guidance asks the licence file to describe activities planned for the next three years, and DNB can require a separate entity under PSD2 Article 11(5). More on the full PI file is in our EMI licence in the Netherlands guide and the SIRA integrity risk analysis DNB expects with it.
3. What Dutch banks owe AISPs and PISPs
Article 26k Bpr copies the bank’s duties from PSD2 Articles 66 and 67. The bank communicates securely with both providers and treats their requests like the customer’s own, on timing, priority and charges, unless it has an objective reason. It gives the PISP all initiation and execution information it holds as soon as the order arrives. It may not require a contract and may not put up obstacles. Article 26h(6) Bpr adds that the bank must let both providers rely on the authentication procedures it gives its customers.
The technical detail comes from Commission Delegated Regulation (EU) 2018/389, the RTS on SCA and common and secure communication. In the Dutch market every significant bank chose a dedicated API under Article 31 RTS. Under Article 32(4) RTS each bank publishes quarterly statistics on the availability and performance of that interface and of its customer channel on its own website. DNB does not publish a league table of its own, so a TPP comparing banks reads the banks’ disclosures.
A bank with a dedicated interface must also keep a fallback (Article 33(4) RTS) unless DNB exempts it under Article 33(6). DNB applies the EBA Guidelines on that exemption (EBA/GL/2018/07). In 2019, sixteen banks asked DNB for one, so a TPP cannot assume a fallback exists at a given bank.
4. DNB’s redirection Q&A: the Dutch journey standard
Here the Netherlands differs. Where Article 32(3) RTS speaks abstractly of “obstacles”, DNB consulted on concrete criteria in 2019 and on 1 July 2020 published a Q&A on an obstacle-free, redirection-based journey through the dedicated interface. The Dutch text is binding and the English version is a courtesy translation. DNB treats the following, among others, as potential obstacles in the bank’s part of the flow:
- making the user log in or complete SCA twice or more;
- letting the bank set the scope or duration of the user’s consent;
- several confirmation screens, each needing a user action;
- asking the user to pick an account the TPP has already specified, or not telling the TPP which account the user picked;
- ending the redirect with a screen that needs an extra click;
- forcing a slower authentication method when the bank’s app is available on the device;
- showing anything unrelated to authentication, or discouraging wording and design.
DNB also describes the target journeys. For payment initiation, one SCA in the bank’s domain that also binds the amount and the payee, with an optional confirmation screen but no second SCA. For account information, one SCA followed by confirmation of the request and, if needed, account selection. A second SCA in a PIS flow is acceptable only for security or fraud reasons, such as high-value or multi-signatory payments, and only if the bank asks for the same thing in its own channels.
The SCA cadence for AIS changed after the Q&A. Delegated Regulation (EU) 2022/2360, applicable since 25 July 2023, added Article 10a to the RTS. When an AISP accesses balances or the last 90 days of transactions through the dedicated interface, the bank may not apply SCA except at first access and again once more than 180 days have passed since the last SCA. The bank can still apply SCA where it has documented grounds tied to unauthorised or fraudulent access. Older material describing a “90-day re-authentication” is out of date.
5. When access fails: the Dutch escalation path
DNB’s February 2022 page on reporting interface problems sets a clear order. First, the TPP uses the bank’s own complaints procedure and completes it. If no compliant solution follows, the TPP reports to DNB, by email or through its account supervisor, using DNB’s complaint form (tabs A.1 and A.2). DNB acts only on banks it supervises; interpretation questions belong in the EBA Q&A tool.
The traffic also runs the other way. Under Article 7:523(5) BW a bank may deny an AISP or PISP access for objective, evidenced reasons linked to unauthorised or fraudulent access, including fraudulent initiation of a payment. It must tell the payer, before the denial where possible and otherwise straight after, and restore access once the reasons have gone. It must also report the incident to DNB immediately with the relevant facts and reasons (Art. 7:523(8) BW). DNB assesses the case and can act against either side.
6. Liability, data and the AFM, DNB and AP split
When a PIS-initiated payment turns out to be unauthorised, the bank refunds the payer by the end of the next business day (Art. 7:528(4) BW). If the PISP is responsible, it reimburses the bank on request and carries the burden of proving that, within its sphere, the payment was authenticated, correctly recorded and not affected by a technical failure (Art. 7:528(5) BW). Article 7:545a BW applies the same structure to non-executed or defective transactions.
Three supervisors touch this area, and the split is less obvious than “DNB prudential, AFM conduct”:
- DNB licenses AISPs and PISPs, supervises the Bpr duties, receives the bank’s access-denial reports and handles TPP complaints about interfaces.
- AFM appears at one specific point. A payer’s PSP that suspects fraud may delay the next-day refund only if it reports its grounds in writing to the AFM (Art. 7:528(3) BW).
- Autoriteit Persoonsgegevens (AP) supervises the explicit-consent rule for access to personal data. Article 1:24(5) Wft takes compliance with rules made under Article 3:17(7) Wft out of DNB’s remit in favour of the AP’s competence under the GDPR implementing act. Those rules include the Article 26e Bpr consent requirement.
On the provider side, Articles 26i and 26j Bpr bar a PISP from storing sensitive payment data or changing the amount or payee, and limit an AISP to designated accounts and to the service the user asked for. A PISP must also give the payer its contact details and DNB’s before initiation (Art. 59c(2) BGfo), and a confirmation, reference, amount and charges straight after (Art. 71ba BGfo).
7. Checking who is licensed: the DNB public register
Banks onboarding a new TPP, and merchants choosing a PISP, should check the DNB public register under Article 1:107 Wft. It lists Dutch-licensed providers, exempt providers (expressly marked as not supervised), and providers licensed elsewhere in the EEA that have notified services into the Netherlands. Each entry shows the start date, the authorised services and any restrictions. Agents and passporting routes are covered in PSD2 agents and the register and branch vs freedom of services.
8. Three Dutch scenarios
Facts: An Amsterdam start-up wants to show SMEs a combined view of their bank accounts, with no payments and no client money. It needs a DNB licence under Article 2:3a Wft, scoped to service 8. Safeguarding, minimum own funds and solvency do not apply (Art. 2:3b(5) Wft). It needs indemnity cover under Article 24(3) Bpr and half-yearly statements on it, but since August 2024 no statutory audit. Governance, integrity and ICT still get the full DNB assessment.
Facts: A PISP licensed in another member state starts initiating payments from Dutch accounts for a webshop. It notifies through its home supervisor and appears in the DNB register as a notified provider. If a Dutch bank’s flow forces two SCAs on a standard payment, the PISP first completes the bank’s complaints procedure, then reports to DNB with the complaint form, citing the 2020 redirection Q&A.
Facts: A Dutch bank sees a run of PIS-initiated payments from compromised accounts routed through one provider. It may deny that PISP access under Article 7:523(5) BW. It must inform the affected payers, report the incident to DNB immediately with its reasons, and restore access once the cause is resolved. Refunds for unauthorised payments go out by the next business day, and the bank claims them back from the PISP if the PISP is liable.
9. PSD3 and the PSR: where things stand
The Commission proposed PSD3 and the PSR on 28 June 2023. Parliament and Council reached a provisional agreement on 27 November 2025, and the Council adopted its first-reading positions on both texts on 29 October 2026. As of this review, Parliament’s second-reading approval and publication in the Official Journal are still to come, and application dates will run from entry into force. In general terms the access rules move into a directly applicable regulation with a user permission dashboard at the bank and a list of prohibited obstacles, which will largely replace Article 26k Bpr and the DNB Q&A. Licensing becomes a recast directive with transitional periods. Our PSD3 and PSR tracker follows the file.
One change has already landed. Since 9 October 2025, Verification of Payee under the Instant Payments Regulation applies to euro credit transfers, including those initiated through a PISP, with the check run by the payer’s PSP. See Verification of Payee under the IPR.
10. FAQ
Is AIS in the Netherlands a registration or a licence?
A licence. DNB states that an AISP must hold a licence under Article 2:3a Wft and cannot operate under an exemption. The requirements are lighter: no safeguarding, minimum own funds or solvency, but indemnity cover is required.
Can a Dutch bank charge a PISP or require a contract?
No. Article 26k Bpr bars making access depend on a contract and requires PIS orders to be treated like the customer’s own orders on charges, timing and priority, unless there is an objective reason.
Has PSD3 replaced the Dutch rules yet?
No. The texts still need Parliament’s second-reading approval and publication, so the Wft, Bpr and BW rules apply.
Does the AISP have to make the user repeat SCA every 90 days?
No. Since 25 July 2023, Article 10a RTS requires SCA at first access and again only after more than 180 days, for balance and 90-day transaction data through the dedicated interface.
11. What to do, today
- If you are a TPP, map your obligations across all four instruments, Wft, Bpr, BW and BGfo, not just the Wft.
- Scope the DNB licence application to services 7 or 8 and build the Article 24 Bpr indemnity cover around your actual liability exposure.
- If you are a bank, test your redirection flow screen by screen against DNB’s 2020 Q&A, and keep the quarterly Article 32(4) RTS statistics current.
- Write a denial-of-access procedure that covers the payer notice, the immediate DNB report and restoration (Art. 7:523(5)-(8) BW).
- Route explicit-consent questions to your GDPR team: the AP, not DNB, supervises the Article 26e Bpr consent rule.
12. Sources
The official texts and supervisor pages relied on, checked on 8 November 2026:
- Wet op het financieel toezicht (Arts. 1:1, 1:24, 1:107, 2:3a, 2:3b, 3:17)
- Besluit prudentiële regels Wft (Arts. 24, 26e, 26h-26k)
- Besluit Gedragstoezicht financiële ondernemingen Wft (Arts. 59c, 71ba)
- Burgerlijk Wetboek Boek 7, Title 7B (Arts. 7:522a-c, 7:523, 7:528, 7:545a)
- Staatscourant 2024, 24570: amendment to the Vrijstellingsregeling Wft (Art. 18d)
- DNB, process for an AIS provider to become active
- DNB, exemption from the licence requirement
- DNB, account information services and other business activities
- DNB, obstacle-free redirection-based customer journey (Q&A, 1 July 2020)
- DNB, reporting issues with interfaces for access to payment accounts
- DNB, public register of payment service providers
- Directive (EU) 2015/2366 (PSD2), EUR-Lex
- Delegated Regulation (EU) 2018/389 (RTS on SCA and CSC), EUR-Lex
- Delegated Regulation (EU) 2022/2360 (Article 10a RTS), EUR-Lex
- EBA Guidelines on the exemption from the fallback mechanism (EBA/GL/2018/07)
- Regulation (EU) 2024/886 (Instant Payments Regulation), EUR-Lex
- European Parliament Legislative Train: PSD3 and PSR
- Council of the EU, voting result on the payment services package, 30 October 2026
Related: EMI licence in the Netherlands · DNB public register (Art. 1:107 Wft) · Safeguarding in the Netherlands · The Dutch reporting calendar · SCA exemptions under the PSD2 RTS · PSD3 and the PSR tracker · Verification of Payee · Open banking in France · The Article 32 small payment institution exemption


