Netherlands · Regional page
Open banking Netherlands: one platform for Dutch bank payments
The Dutch market does not need to be convinced that paying from a bank account works. Consumers here select their bank at checkout without thinking about it. The useful question is how a company serves that habit in the Netherlands and in every other market it sells into, from one platform. Licensed providers deliver the regulated payment services on this route, and viaBanking confirms in read-only mode that the amount was credited to your own C2B account.
- OnePlatform contract covering the Netherlands and the wider market
- Read-onlyConfirmation of the credit on your own C2B account
- LicensedPartner providers deliver the regulated payment services
- Nothing heldviaBanking never holds or moves your funds
The Dutch starting point
A settled habit that does not travel
The Netherlands is a market where open banking style payments already won. The problem a Dutch company brings us is almost never the local one: it is what happens to those payment services the moment the business sells outside the Netherlands.
- 01
The Dutch market solved this a long time ago
Paying a merchant straight from a bank account is not a new idea in the Netherlands. Consumers here have been selecting their own bank at checkout for years, and the behaviour is so settled that a business adding a payment method is competing with a habit rather than with an absence.
- 02
The domestic route stops at the border
A payment service tuned for one market serves that market and nothing beyond it. A Dutch company selling into Germany, Belgium or Spain discovers that the arrangement covering the Netherlands does not travel, and a second integration project begins.
- 03
Every market means another contract
Each new payment service brings its own agreement, its own reporting format and its own support channel. A finance team ends up reconciling three or four separate services that all describe the same thing differently.
- 04
Arrival is still assumed rather than checked
Whichever service carries the payment, most integrations act on an acknowledgement from the provider. Whether the money reached the account the business actually reconciles against is left to a person opening a banking screen at the end of the day.
Definition
What sits behind a Dutch bank payment
The rules are described on the PSD2 open banking page. Here is the short version for this market.
The bank operates the interface
Banks in the Netherlands run a regulated access interface that a licensed institution may use on a customer's instruction. It carries a payment request and returns payment status. The interface exists because European rules oblige the bank to provide it, and it is what every open banking service in this market builds on.
The customer selects and approves
A Dutch payer selects their bank, lands inside that bank's own environment and approves the amount and the beneficiary. Strong customer authentication takes place there. The user's payment consent is given to the bank, and no banking credential reaches the merchant or viaBanking.
Regulated services stay with the licensed institutions
Payment initiation is a regulated service performed by a licensed PIS provider. Account information is a regulated service performed by a licensed AIS provider. viaBanking supplies the platform, the routing and the payment data model around those services, and holds neither permission.
By segment
Six Dutch segments and what each one gets
The Netherlands is one market with several very different buyers inside it. What a marketplace wants from open banking services has almost nothing in common with what a subscription platform wants, so this section splits the market by segment rather than offering one summary for all of them. Read the segment closest to your own and ignore the rest, because the differences between these segments are larger than the similarities.
- Ecommerce
Checkout conversion in a bank first market
Dutch shoppers expect to select their bank and approve in an app they open every day. What an ecommerce business needs from open banking services in this segment is not persuasion, it is a bank selection list that is complete, a status feed that resolves quickly and a confirmed account credit that tells the warehouse when to pack. The market rewards services that behave consistently at three in the morning as well as at noon.
- Marketplaces
One payment shape across many sellers
A marketplace collects from buyers on many banks and owes money onward to many sellers. The valuable property of this segment is that every incoming transfer arrives in one payment model with the reference intact, so the seller ledger updates from a credited amount rather than from an acknowledgement. Cross border marketplaces get the same behaviour from the same services in every market they select, which is rarely true of domestic services bought market by market.
- Fintech and financial services
Funding accounts without carrying the risk
Brokerages, savings services and payment businesses fund customer balances from the customer's own bank. This segment is the strictest user of the confirmation signal, because releasing a balance on a provider acknowledgement means carrying the difference on the company's own book. Firms selling regulated services of their own are also the quickest to ask which party in this chain holds which permission, and the capability table below answers that segment by segment.
- Subscriptions and platforms
Annual plans and large upgrades
Recurring monthly charges are well served by existing card services. This segment uses open banking services for the amounts that sit awkwardly on a card: annual plans, seat expansions, arrears and enterprise renewals. Both sets of services report into the same payment model, so nobody has to run a second reconciliation service alongside the first.
- B2B and wholesale
Invoices that must reconcile themselves
Dutch businesses settle invoices by transfer as a matter of course. Sending a payment link instead of an IBAN means the reference survives the journey, and the accounts receivable service matches the account credit without a person reading a bank statement. This segment usually sees the fastest payback on the integration, especially where professional services firms invoice monthly.
- Travel and ticketing
Group bookings above card limits
A multi passenger booking regularly exceeds what an issuer allows in a single transaction. In this segment open banking services remove the limit conversation and give the operator a confirmed account credit before a seat is held, which matters when inventory is perishable. Travel services also benefit from the reference travelling with the payment, because a booking code is worth more than a payment identifier.
- 6Business segments served from one platform contract
- 1Payment model, whichever segment and whichever market
- 2Signals per payment: provider status and confirmed credit
The platform
What the platform layer is actually for
One platform for the Netherlands and everything after it
Your systems integrate once. The Dutch market is one configuration on that platform, and the next market you select is another, with the same payment model and the same payment services behind it.
Provider selection stays ours
viaBanking selects which licensed provider carries each payment, based on the bank the customer selected and how that route is behaving. Nothing about that selection reaches your codebase.
One payment model across every market
A payment approved in a Dutch bank comes back in the same shape as one approved anywhere else, so your reconciliation service is written once and never learns a market specific format.
Confirmed credit on your own account
A licensed AIS provider reads your C2B account in read-only mode and we raise one event when the expected amount is credited. Your order logic depends on that event instead of on a service acknowledgement.
The full platform surface is described on the open banking platform page, and the licensing split on the PIS provider page.
Capabilities
Every service in the flow, and who delivers it
| Capability | What it is | Delivered by |
|---|---|---|
| Bank selection list | Dutch institutions reachable on the routed provider, presented to the payer | viaBanking presents, the payer selects |
| Payment initiation | A regulated service, performed on the user's payment consent | Licensed PIS provider |
| Authentication | Strong customer authentication inside the selected bank | The payer's bank |
| Funds movement | Between the payer's bank and your C2B account, on bank rails | Banks and EMIs |
| Status normalisation | One vocabulary for every provider and every market | viaBanking |
| Account credit confirmation | Read-only account information service on your own account | Licensed AIS provider, surfaced by viaBanking |
| Payer account data | Balances, statements and transaction history are out of scope | Not offered on this platform |
Integration
One integration, five stages per payment
- 1
Integrate once
One set of credentials, one payment endpoint. The Netherlands is a configuration value rather than a code path.
- 2
Create the payment
Amount, currency, reference and the destination C2B account. No market specific fields.
- 3
The payer selects a bank
From the Dutch institutions the routed licensed provider reaches.
- 4
Consent and authentication
Given inside the selected bank, where the payer already has a relationship.
- 5
Status and confirmation
The provider status arrives normalised, then the credit event lands when the money does.
Payload detail is on the open banking for developers page.
Security and consent
What the payer gives, and to whom
The bank keeps the credentials
Authentication happens inside the bank the payer selected. No password, code or device confirmation reaches viaBanking, and none is stored by the merchant either.
One consent, one payment
The user's payment consent covers a single amount to a single beneficiary account with a single reference. It ends when the payment resolves and grants no continuing access.
Read-only account information, on your account
The account information service runs against the C2B account your company holds, in read-only mode, through a licensed provider. It recognises an expected account credit. It cannot manage the account and cannot send money from it.
FAQ
Six questions from Dutch teams
-
How does open banking work in the Netherlands in practice?
Your platform creates one payment, the payer selects their Dutch bank and approves inside it, a licensed provider performs the initiation as a regulated service, and viaBanking confirms in read-only mode that the amount reached your own C2B account. The market is already used to this shape, so the payer needs no explanation.
-
How is this different from the domestic service we already use?
Mechanically it is close, and commercially it is not. A domestic payment service covers one market. This platform covers the Netherlands and every other market you select, on one contract and one payment model, and it adds a confirmed credit on your own account, which most services leave to the merchant to work out.
-
Which business segments does it suit best?
Marketplaces, fintech and financial services, B2B invoicing and travel see the clearest benefit, because the amounts are large and the reference matters. High frequency low value ecommerce is usually well served by the payment services already in place, and open banking services add less there. The segment breakdown above sets out what each segment gets, and we are happy to say when a segment gains nothing.
-
Who performs the regulated steps on this route?
Licensed institutions. Payment initiation is performed by a licensed PIS provider, the account information service behind the account credit confirmation by a licensed AIS provider, and the funds move between banks and EMIs. viaBanking is a software company and holds neither permission.
-
What actually confirms that money arrived?
A read-only account information service checking your own C2B account and raising an event when the expected amount is credited. It is a check on your business account only. It does not read the payer's account, their balances or their transaction history, and no account ownership check is performed or sold.
-
How long does integration take?
Sandbox on the first day, then usually one to three weeks of engineering, most of it spent on payment statuses rather than on the happy path. Opening the C2B account with the receiving bank or EMI happens directly between your company and that institution. The wider regional picture is on the Europe page, and the German market on the Germany page.
Serve the Dutch market and the next one from the same platform
Tell us your segment, the Dutch banks your customers select most often and the markets you expect to open next. We come back with live coverage from the licensed providers behind our routes and with what the C2B account arrangement would be for your company.
viaBanking is a software and technology provider. Regulated payment initiation and account information services are delivered by licensed partner institutions. viaBanking does not hold an AIS or PIS licence, does not execute bank payments and does not move funds.