Payments and fintech: decisions taken at group level
A decision taken by a foreign parent about its Dutch payment or e-money subsidiary can trigger notification or approval duties that do not exist for an ordinary trading company. The trigger is the licence, not the transaction. This applies to any group with a Dutch entity holding a payment institution, e-money institution or account information licence, and it is worth checking before the parent's resolution is implemented rather than after.
Why this arises here
Payment institutions and e-money institutions established in the Netherlands hold a licence granted by De Nederlandsche Bank (DNB), with the Authority for the Financial Markets (AFM) supervising conduct towards customers. The licence is granted to the Dutch entity on the basis of who controls it and who determines its policy day to day. A group-level decision, made by a parent board that has never dealt with a Dutch authority, can change one of those facts without the parent realising that a Dutch regulatory file has just been reopened. This is a corporate governance practice question the moment the decision reaches the Dutch board for implementation, because it is the Dutch board that carries the notification duty, not the parent.
That link between a group resolution and a licence condition does not exist for a company outside the regulated payments sector, where a parent-level board resolution stays inside the group and rarely reaches a public authority. Payments and fintech is the sector where the internal governance record and the regulatory file are, in substance, the same paper trail.
The mechanics in short
A Dutch payment or e-money institution operates under a licence issued under the applicable Dutch rules transposing the EU payment services and e-money frameworks. Two features of that licence matter for a group decision:
- Control. A change in who holds a qualifying stake in the licensed entity, directly or through the group's holding chain, falls to be assessed by DNB before or shortly after the change takes effect, depending on how the change is structured.
- Policy makers. The persons who determine the entity's day-to-day policy, the dagelijks beleidsbepalers (day-to-day policy makers), are individually tested for suitability and reliability. Replacing one of them at group level, for example by rotating a regional director into the Dutch board seat, restarts that test for the new appointee.
A group decision that changes either of these two features, even where the decision itself is taken entirely outside the Netherlands, has a Dutch regulatory consequence that a similar decision at an ordinary operating subsidiary would not have.
The pattern specific to payments and fintech
Three features are typical of this sector and rarely appear elsewhere in a group's Dutch corporate structure. First, the contract pattern: agency and distribution agreements under which local agents provide the payment service on the licence holder's behalf, and safeguarding arrangements that keep client funds in an account segregated from the group's own working capital. A group treasury decision to pool cash across entities has to be checked against that segregation before it is implemented.
Second, the register that touches it: DNB maintains the register of licensed payment and e-money institutions, and AFM maintains the register of financial service providers under its conduct mandate. Both registers are public and both are updated when the underlying facts change, which means a group decision that is not notified can leave the public register out of step with reality.
Third, the situation that only arises here: a group restructuring resolution, such as merging the Dutch licence holder into another group entity or transferring its business to an affiliate, can require prior notification to or approval from DNB before it takes effect for the licensed entity. In an unregulated Dutch subsidiary the identical resolution is purely an internal governance matter with no external gatekeeper. In a licensed payment or e-money institution, the gatekeeper sits between the resolution and its implementation.
What to check
Before a group-level decision affecting a Dutch payment or fintech subsidiary is implemented, confirm:
- Whether the Dutch entity holds a licence, or operates under a registered exemption, and what that licence or exemption actually covers.
- Whether the decision changes control, a day-to-day policy maker, or the entity's programme of operations as filed with the regulator.
- Whether prior notification to, or approval from, DNB or AFM is required, and what period runs from the point of notification before implementation is permitted.
- Whether the entity's cross-border passporting notifications to other EU member state regulators need to be updated as a result of the same decision.
Decision type and its Dutch regulatory trigger
| Decision taken at group level | Where it originates | What it can trigger at the Dutch entity |
|---|---|---|
| Appointment or removal of a director | Group board or group HR | Suitability and reliability test of the new day-to-day policy maker |
| Change of ultimate parent or controlling shareholder | Group M&A | Assessment of the qualifying holding in the licensed entity |
| Intra-group loan restructuring or cash pooling | Group treasury | Review against the safeguarding arrangement for client funds |
| Merger or transfer of the licensed entity's business | Group restructuring | Prior notification to, or approval from, DNB before implementation |
A dispute about a DNB decision following one of these steps runs through administrative objection and appeal, not the ordinary Dutch court that hears company law and commercial disputes, which is itself a distinction worth knowing before a group assumes the two routes are the same.
What this does not cover
- This page does not cover the licensing procedure itself: it addresses the interaction between an existing licence and a decision taken above the licensed entity.
- It does not cover payment services regulation outside the Netherlands, or Wft licence categories other than the payment and e-money institution licences described above.
- It does not state specific thresholds, fees or notification periods. These depend on the entity's exact licence and on current regulatory practice: check the current position before relying on any particular figure.
- It does not cover individual customer complaints or payment disputes, which sit with the entity's conduct obligations rather than with group governance.
Questions
Does a decision taken by the foreign parent board bind the Dutch licensed subsidiary directly?
No. A parent-level resolution has to be implemented by the Dutch entity's own board, and where it changes control, a policy maker or the licensed activity, that implementation step is where the Dutch notification duty arises, not the parent's resolution itself.
Which Dutch authority is notified when a group changes who controls the payment institution?
De Nederlandsche Bank supervises the qualifying holding and the suitability of day-to-day policy makers of Dutch payment and e-money institutions. The Authority for the Financial Markets supervises the entity's conduct towards its customers, and the two mandates can both be engaged by the same group decision.
Does this apply if the Dutch entity only holds an exemption rather than a full licence?
An exemption depends on the conditions under which it was granted. A group-level change, such as a shift in control or in the scope of activity, can put the entity outside those conditions, so the same check applies before the decision is implemented, not after.
Author
Hugo Steenbergen, corporate law and governance. Eva works on board decisions, group governance disputes and the procedures before the Enterprise Chamber that follow when a group decision is contested internally.
Where this sits and what to read next
This note sits inside the corporate law and governance overview, alongside the equivalent question for group decisions in professional services, which follows a different pattern because there is no licence in the chain. Where the same group decision has downstream consequences after a deal has closed, see post-closing steps in energy and renewables deals. Where the Dutch entity sits under a Spanish holding layer, see how a group map handles the Spanish layer. Where a group decision has already caused a loss and the question is recovery rather than prevention, see enforcing a trustee's liability claim for the mechanics of that route.
A structure report sets out who controls a Dutch entity, whether it holds a licence, and how a proposed group decision sits against that picture, before the decision is implemented rather than after.
Last legal review: 2026-09-29