DNB's payment account carries Dutch settlement risk

Summary

De Nederlandsche Bank N.V. matters to a Dutch bank treasury and payments executive because the paid unit is not a normal supplier account. It is a settlement and continuity position: TARGET-NL access, central-bank money finality, collateral and intraday credit administration, supervisory attention, cyber-resilience discipline and public legitimacy.
The public evidence is unusually direct. DNB says TARGET Services are the technical backbone of European payment and settlement systems, that DNB opens accounts and monitors transactions in the Dutch segment, and that TARGET-NL cash transfers settle irrevocably in central-bank money.
The price of the account is not only the fee schedule. It is the cost of scarce operational staff, legal certainty, liquidity management, collateral readiness, two-data-centre style continuity expectations, incident rehearsal, fraud supervision and dependence on Eurosystem shared platforms, network service providers and European governance.
Substitutes exist, but each is partial. A commercial correspondent-banking workaround, euro-area shared infrastructure, internal liquidity buffers, delayed settlement and manual continuity procedures can reduce exposure to a specific interruption. None gives the same combination of Dutch supervisory authority, central-bank money, settlement finality and public trust.
The judgement would change if private incident data showed weak TARGET-NL help-desk performance, repeated onboarding friction, unsettled payments during stress, poor cyber-test follow-through, slow collateral operations, unresolved fraud-supervision findings, or a credible private route that banks could use without raising liquidity, legal or reputational risk.

The paid unit is settlement trust

The continuity moment is not dramatic at first. It is a Dutch bank treasury desk before a long settlement day, watching liquidity positions, collateral availability, payment queues, securities obligations, fraud alerts and customer-service escalation channels while a payments executive asks a plain question: if one part of the chain fails, what has the bank really bought from the central-bank infrastructure around DNB? The account is not merely a place to hold a reserve balance. It is the right to settle in central-bank money, to connect into TARGET Services through the Dutch central bank, to use central-bank accounts as the final layer beneath commercial-bank promises, and to be inside a supervisory environment that treats payment continuity as a public good.

That is the paid unit. A bank buys the ability to make and receive high-value payments through TARGET-NL, to manage liquidity across the Eurosystem's T2 structure, to use collateral arrangements that support intraday and monetary-policy credit, and to anchor private promises in the balance sheet and authority of the central bank. Around that account sit payment-system oversight, cyber testing, reporting obligations, crisis coordination, fraud monitoring and the reputational benefit of operating inside a rule set that other banks, clearing systems and market infrastructures recognise.

The buyer does have substitutes, and they must be named early because they price the account. A commercial correspondent-banking workaround can route some flows through another bank, but then the buyer accepts commercial credit, cut-off, legal and operational dependencies that central-bank settlement avoids. Euro-area shared infrastructure can spread resilience across the Eurosystem, but it also makes Dutch settlement dependent on common platforms and common change programmes. Internal liquidity buffers can reduce urgency, but idle liquidity has a cost and may not solve legal finality. Delayed settlement can buy time, but it changes customer and market risk. Manual continuity procedures can keep staff oriented during disruption, but they do not recreate a functioning real-time settlement system at scale.

This is why DNB should be read less as a generic public institution and more as a scarce continuity account for the Dutch financial sector. Its public mandate, payment-system role and supervisory powers turn the account into a bundle of services that private banks cannot replicate alone. The bundle is valuable precisely because it is not a profit-maximising product. It is a public-sector platform that private institutions must nevertheless price like a critical vendor.

The channel dependence is also different from an ordinary vendor decision. A bank can change a software supplier, renegotiate a processor contract, add a second cloud region or hire a different consultancy without asking customers to rethink the meaning of a euro payment. It cannot casually replace the account that connects its balance sheet to central-bank money. Even where a bank has multiple commercial channels, the DNB-linked settlement position is the shared reference underneath corporate liquidity, securities settlement, payment-system access and supervisory credibility. That makes the account sticky for reasons that have little to do with customer inertia. It is sticky because the alternative would force the bank to rebuild how counterparties, regulators, treasury staff and auditors understand final payment.

TARGET-NL makes the Dutch account European

DNB's own TARGET Services page is unusually explicit about the mechanism. TARGET Services are described as the technical backbone of European payment and settlement systems. T2 handles interbank euro transactions. T2S settles securities transactions in central-bank money. TIPS enables instant payments within seconds, every day of the year. ECMS manages collateral pledged to national central banks. DNB's role is not decorative. The page says central banks such as DNB support T2 because when commercial banks transfer funds, the transaction goes through the central banks in their home countries. It also says those central banks are involved in opening accounts and monitoring all transactions.

For a Dutch treasury desk, the phrase "home countries" is the hinge. The account with DNB is a national doorway into a euro-area settlement machine. It is Dutch in legal documentation, account maintenance, help-desk contact, collateral processing and supervisory proximity. It is European in technology, governance, settlement architecture and dependency. That double identity is the point. A bank wants the finality and scale of the Eurosystem, but it also needs a national central bank that can open the account, maintain the Dutch segment, interpret local conditions and coordinate with domestic institutions when something goes wrong.

The scale makes substitution hard. ECB facts for T2 describe real-time gross settlement in central-bank money and daily averages of 421,875 payments totalling about EUR 1,811 billion. ECB facts for T2S put securities settlement at roughly 791,416 daily transactions and EUR 972.4 billion in value. DNB's own TARGET page says T2 processes more than a thousand EU financial institutions and that 99.9 percent of transfers are completed in under five minutes. The exact numbers vary by page and reporting year, but the order of magnitude is the economic point: these are not convenience rails. They are balance-sheet arteries.

The account also inherits European project risk. DNB's TARGET consolidation page explains that TARGET2 was replaced by a new real-time gross settlement system and that DNB is the central bank in charge of opening and maintaining accounts in the TARGET-NL segment. It also notes that SWIFT and Sia-Colt were awarded network-service-provider concession contracts after the Eurosystem tender and that participants must select their own network service provider. A bank that treats the DNB account as a standalone Dutch service misses the actual dependency stack. The customer is buying Dutch account governance attached to a common Eurosystem platform, third-party connectivity, ISO 20022 messaging, readiness reporting and migration discipline.

Upstream dependence therefore has to be priced twice. First, the bank must price its direct access choices: network service provider, message connectivity, identity controls, treasury workstation resilience, operational staffing and the internal route from payment instruction to central-bank settlement. Second, it must price common infrastructure choices it cannot fully control: Eurosystem change calendars, shared component releases, cross-border governance decisions, common contingency procedures and the operational readiness of other participants. The DNB account is attractive because it sits inside a disciplined common platform. The same fact means a Dutch participant needs enough internal competence to understand shared-platform change, not just enough compliance capacity to submit forms.

This is not a weakness by itself. Shared infrastructure can be more resilient than a purely national system because costs, expertise, testing and standards are pooled. But shared infrastructure changes the risk. A local bank cannot simply negotiate a bespoke Dutch timetable if a common platform changes. A Dutch central bank cannot single-handedly redesign the European settlement calendar. A Dutch participant's network-service-provider choice can become a practical continuity exposure even when DNB and the Eurosystem perform their own roles well. The account is therefore buying trust inside a federation of dependencies, not trust without dependencies.

The price signal is visible in migration work. ISO 20022 readiness, testing windows, registration forms and migration rehearsals are not ceremonial overhead. They are how a system with thousands of users reduces the chance that one participant's unreadiness creates wider settlement noise. A bank with strong treasury engineering may treat this as normal change management. A weaker participant may experience it as burden. Either way, the account is buying access to a platform where readiness is made public enough, and standardised enough, that counterparties can keep trusting the system during a major technical renewal.

Finality is the legal premium

The legal value of the account is finality. DNB's TARGET legal documentation says TARGET-NL is designated under the Settlement Finality Directive and that cash transfers are settled irrevocably. It lists the accounts TARGET provides for settlement in euro in central-bank money: main cash accounts for central-bank operations, RTGS dedicated cash accounts for large-value payment settlement, T2S dedicated cash accounts for securities settlement, TIPS dedicated cash accounts for instant payments and technical accounts for ancillary system settlement. These account types are dry names, but they are the paid inventory.

A commercial bank can promise a customer that a payment has been made. A correspondent bank can offer access to a network. A clearing system can net obligations and route files. None of those private arrangements has the same legal and monetary meaning as final settlement in central-bank money. That is why the DNB account is not just about operational convenience. It changes the character of the claim. The balance has moved through the layer where central-bank money, national central-bank participation and harmonised legal documentation meet.

This premium matters most during stress. In normal conditions, users experience settlement as an absence of problems. Payments arrive, securities settle, collateral moves and liquidity is available. During stress, the question becomes who bears the risk of delay, reversal, insolvency, failed funding, unavailable collateral or unclear instructions. The settlement-finality framework is designed to stop one participant's problem from becoming a general doubt about whether completed transfers can be unwound. DNB's public documentation shows the Dutch legal segment. The ECB's T2 description shows immediate finality and continuous one-by-one settlement. The combined effect is a public legal product, even though a commercial participant experiences it through operational screens and account terms.

That is also why delayed settlement is a weak substitute. It may be necessary during a specific incident. It can be rational when liquidity is tight, operational confirmation is uncertain or a payments window is disrupted. But delayed settlement changes the position from final to pending. The bank now carries more liquidity risk, market risk, client-service risk and sometimes regulatory risk. A manual procedure can record the intention to pay, and a correspondent can carry some customer obligations, but neither turns a pending obligation into irrevocable central-bank settlement.

The value of DNB's account is therefore partly negative value: the risks the buyer does not have to carry. The bank does not have to price the commercial credit quality of a correspondent for each final euro payment. It does not have to explain to every counterparty why a settled transfer might be uncertain. It does not have to build a private law regime that all counterparties trust equally. It pays to stand inside the central-bank settlement regime, where other institutions already know the rule set.

Collateral and liquidity are operating memory

The DNB account is also a memory system for bank liquidity. DNB's information for counterparties says euro-area credit institutions must hold minimum reserves with the national central bank of their country of establishment, and that institutions independently fulfilling the reserve requirement must have an account with DNB. It says an account in CLM of TARGET must be used for holding. It also links minimum-reserve reporting, standing facilities, monetary-policy participation and the additional terms required for a Dutch counterparty to act as a Eurosystem monetary counterparty.

The practical result is that a bank treasury desk cannot treat payment continuity and monetary-policy access as separate worlds. The same institution that watches customer payment flows also watches reserve fulfilment, intraday liquidity, eligible collateral, credit lines, settlement priorities and standing-facility access. DNB's TARGET Services page connects ECMS to that work. It says ECMS tracks individual collateral and credit positions across national central-bank counterparties, calculates the credit line available to each counterparty and sends this information to the T2 central liquidity management tool. DNB is responsible for transaction processing and corporate actions on behalf of Dutch financial institutions, and credit depends on pledged collateral after risk haircuts.

This is where the account buys repeated operating memory. A participant is not inventing a collateral process on the morning of a crisis. It has eligibility rules, account documentation, pledge arrangements, monitoring routines, national help-desk contacts, reporting obligations and staff habits already in place. A liquidity buffer inside the bank is useful, but the buffer only becomes a system-wide tool when it can move through accounts and collateral channels that the market recognises. A bank can hold more cash, reduce payment outflows, pre-fund certain obligations or plan for daylight liquidity stress. Those are prudent internal substitutes. They do not replace DNB's role as national central-bank account maintainer and collateral processor inside the Eurosystem.

The private facts that would sharpen this judgement are granular. How often do Dutch participants approach intraday credit limits? How quickly are collateral substitutions processed during operational stress? How many payment queues require manual intervention? How often do banks miss internal cut-offs because of account or messaging problems? How quickly does the national service desk resolve participant issues? Public evidence proves the framework and the roles, not the private incident distribution. That distinction matters. The public framework can be strong even if one institution operates poorly inside it, and a bank's internal resilience can be good even if a common platform still creates external dependencies.

The account therefore prices liquidity readiness rather than simple balance storage. Its value rises when market stress makes liquidity timing expensive. It rises when collateral mobilisation is the difference between paying now and paying later. It rises when a bank's corporate clients expect payments to settle without hearing about central-bank operating calendars. It falls only if private alternatives can provide comparable finality, liquidity mobility and market acceptance at lower operational risk, which is a high bar.

Oversight turns public trust into a bank cost

DNB's oversight page makes the supervisory layer visible. It says DNB is responsible for oversight of payment and securities transactions and monitors them to prevent systemic risks and serious disruptions. It names TARGET2NL, Currence iDEAL, Mastercard Europe and equensWorldline as examples in the payments area, and central counterparties and central securities depositories in securities settlement. It also states that institutions must be able to process transactions quickly and continuously, that maintaining two data centres helps continuity, that transactions must be secure and that institutions must anticipate cyberattacks and recover quickly from cyber-related disruptions.

For the bank buyer, oversight is both a cost and a benefit. It is a cost because DNB can require evidence, procedures, controls, board fitness, risk management and remediation. Staff must be hired, systems documented, tests run, suppliers assessed and incidents reported. A payments or treasury executive may experience this as friction. But the same friction is part of what the buyer is buying. A payment account inside an unsupervised ecosystem would be cheaper in the narrow sense and less valuable in the wider sense. The Dutch payments market relies on the belief that critical participants are not merely self-certifying their resilience.

This creates an unusual market structure. DNB is not competing with a commercial processor for account volume. It is setting conditions under which the commercial processors, banks and payment institutions remain trustworthy enough for the public to keep using digital payments. The price is paid through compliance budgets, operational staffing, control functions, technology redundancy, supervisory fees and management attention. The return is lower probability of a payment-chain failure that would otherwise damage every participant, including the well-managed banks.

Supervision also makes competitive pressure more honest. If one provider underinvests in continuity, it can underprice rivals until the weak point appears in an outage. Oversight attempts to make that strategy less available. DNB's page is explicit that payment systems must process quickly and continuously and recover from cyber disruption. A bank buying a DNB-linked settlement account is therefore buying into a market where continuity is supposed to be part of the baseline, not an optional premium.

The risk is that the baseline becomes expensive without being fully visible to end users. Dutch consumers and merchants see card acceptance, mobile payments, iDEAL, instant bank transfers and cash access. They do not usually see data-centre redundancy, fraud-control staffing, incident exercises, TARGET readiness reports or collateral documentation. When resilience spending rises, the political and commercial question is who pays. DNB's Payments Strategy 2026-2028 is candid on this point: it says resilience and autonomy require substantial investments and that society needs support for the right balance between resilience and affordability.

Cyber resilience is part of settlement value

The cyber layer is no longer a separate technology appendix. DNB's TLPT page says the Digital Operational Resilience Act entered into force on 17 January 2025 and authorises DNB to identify financial institutions licensed by, or applying for a licence to, DNB that must conduct threat-led penetration testing when DORA requirements apply. Its TIBER page says DNB developed TIBER-NL in 2016 to simulate cyber attacks in a controlled manner and improve financial institutions' response capabilities. The same page says the Dutch financial sector has been working together for several years to enhance cyber resilience and that TIBER can apply to large banks, payment institutions, pension providers and insurers.

The ECB's cyber-resilience explainer supplies the euro-area reason. Cyberattacks threaten individual institutions, but high financial-sector interconnectedness can turn them into risks to the overall ecosystem. The ECB says financial-market infrastructures, such as payment or settlement systems, need adequate resilience, and that significant institutions must report significant cyber incidents within two hours of classifying them as significant. This is directly relevant to DNB's account value. A settlement account is valuable only if the systems, staff and counterparties around it can keep working through attack, compromise, confusion and recovery.

The cost paragraph belongs here. The expensive input is scarce human and institutional capacity: cyber analysts who understand payment operations, treasury staff who understand liquidity under attack, legal teams who understand finality and incident disclosure, continuity managers who can run exercises without paralysing production, supervisors who can evaluate testing evidence, and engineers who can maintain redundant connectivity, identity controls, logging, patch discipline and recovery playbooks. Hardware and software matter, but they are not the scarce unit. The scarce unit is the cross-functional ability to keep a payment bank alive while evidence is incomplete and time is expensive.

DNB's payments strategy describes why this cost cannot be avoided. It says payment-chain resilience is urgent because of cyber attacks, digital crime, geopolitical tensions and dependence on non-European players. It also says critical links and critical suppliers must be mapped and that Dutch market participants are encouraged to join cyber-resilience programmes such as TIBER and ART testing. In other words, the price of the DNB account includes knowing the chain. A bank cannot simply say its own systems are secure if its processors, card schemes, wallet providers, terminal vendors, cloud dependencies and network connections are weak.

That supplier mapping is where the public-sector account becomes a private labour problem. A bank must know which suppliers touch payment initiation, sanctions screening, fraud scoring, message routing, confirmation, settlement reporting, reconciliation, customer notification and contingency communications. It must know which suppliers can be bypassed, which can only be paused, and which would stop a critical function if they failed. DNB can set expectations and coordinate the sector, but it cannot outsource each bank's institutional memory. The real cost driver is the staff who can translate a supplier failure into a liquidity, customer, legal and supervisory consequence quickly enough to make a decision.

There is also a shift-work problem. A system that supports instant payments, longer settlement windows or more continuous customer expectations requires more than one heroic incident team. It requires documented handovers, decision rights outside office hours, weekend coverage, tested call trees, and executives who understand when a technical incident becomes a market-confidence problem. This is why the account's price keeps moving upward even if per-transaction technology gets cheaper. The marginal message can be cheap while the continuity organisation needed to trust that message becomes expensive.

Cyber resilience also limits the substitute value of manual procedures. Manual continuity procedures are necessary because no system should assume perfect uptime. They can triage payments, communicate with clients, manage liquidity priorities and preserve decision records. But a manual process cannot process the daily value and speed of T2, T2S or TIPS. It cannot make instant payments settle in milliseconds. It cannot restore market confidence if participants believe the system-of-record has been compromised. Manual continuity is a bridge, not a replacement.

Retail payment dependency feeds back into wholesale trust

DNB's article on 2025 point-of-sale payments shows how ordinary payment behaviour feeds into the wholesale question. Dutch consumers made 7.1 billion point-of-sale payments in 2025, with a total value of EUR 185 billion. Cash accounted for 17 percent of payments, card payments rose to 83 percent, and mobile or smartwatch payments rose from 34 percent to 39 percent of point-of-sale payments. This does not prove anything about TARGET-NL availability. It proves that Dutch society has become highly dependent on electronic payment continuity.

The dependence raises the public stakes of a DNB account. Wholesale settlement and retail payment availability are not identical systems, but confidence travels between them. If card payments, instant transfers, bank apps or payment requests fail in a visible way, consumers and merchants do not parse the exact technical layer. They ask whether the banking system works. If a large-value settlement problem delays bank funding or securities settlement, corporate treasurers do not experience it as a technical curiosity. They experience it as trapped liquidity, missed funding windows and client risk. DNB sits across those layers as central bank, overseer, payments authority and statistical publisher.

Fraud data make the same point from another angle. DNB reported that fraudulent transactions involving bank transfers, card payments and cash withdrawals rose 30 percent in 2025 to roughly 658,000, with monetary value up 22 percent to EUR 198 million. It also noted that this was still a small share of total payments, with about 27 million transactions per day and around EUR 13 billion in daily payments in the covered scope. The small-share point matters because payment trust is statistical. A system can be overwhelmingly successful and still politically vulnerable if fraud grows fast enough or concentrates in sensitive channels.

The customer channel is where that statistical trust becomes fragile. A corporate client whose supplier payment is delayed may call the bank's account manager, not DNB. A consumer who sees fraud in an instant transfer may blame the app, the bank, the fraudster and the payment system in one emotional sequence. A merchant whose terminal fails on a busy day may not care whether the weakness came from the acquirer, processor, telecom link, card scheme, bank or settlement layer. DNB's account value sits behind these visible channels, but the public reputation of the account is shaped by the channels above it. That is why DNB's payment strategy treats retail payment resilience and wholesale central-bank innovation as connected concerns rather than unrelated policy files in daily service.

DNB's exploratory fraud-supervision article adds an operating detail: all seven banks, payment institutions and electronic-money institutions examined were taking measures to prevent fraud, but many organised fraud management mainly at an operational level rather than around clear strategic objectives. For a payments executive, that is a warning about where the next cost may sit. It is not enough to process today's suspicious transaction queue. Institutions may need better objectives, better measurement and better strategic governance of fraud controls.

This feeds back into settlement trust because fraud, cyber and payment continuity all compete for the same management bandwidth. A bank that cannot control retail fraud may face more customer reimbursement pressure, more operational alerts, more supervisory attention and more reputational damage. A bank that cannot settle wholesale obligations may create liquidity and market risk. The DNB account does not solve either problem alone. It makes the public authority and the settlement layer part of the same trust architecture.

Data locality is evidence, not sovereignty by itself

The assignment's network-resource lens is useful only if it remains modest. Public DNS and RDAP evidence for dnb.nl shows a DNB registrant name for the domain, active domain status, DNSSEC delegation, Akamai nameservers and short-TTL Akamai web addresses. It also shows DNB-controlled mail hostnames in MX records. That proves a public web and domain-accountability surface. It does not prove where DNB's internal payment systems, TARGET-NL operational data, supervisory data or incident-management platforms are hosted. It should not be inflated into a claim about full data sovereignty.

The distinction matters because payments strategy increasingly uses the language of autonomy, locality and dependence. DNB's Payments Strategy 2026-2028 says Europe has not yet achieved the level of autonomy in payment transactions required to protect public trust, and that over-dependence on non-European players in critical payment-chain roles is undesirable. It points to card schemes, wallets, processors, data storage, token services and other roles in a more complex card-payment circuit. The public DNS evidence for DNB's website shows that even a central bank uses global web-delivery infrastructure for public web presence. That does not weaken DNB's central-bank role. It reminds the reader that autonomy is specific to the function being discussed.

For a bank treasury desk, the relevant data-locality question is therefore functional. Which data and operational processes must remain under Dutch or European jurisdiction? Which can safely use global vendors? Which must be recoverable without a non-European provider? Which require real-time access during a cross-border political or cyber stress? Which can be buffered by caches, offline procedures or alternative channels? DNB's account value rises when it can help the market separate critical settlement, supervision and continuity functions from ordinary web or communications dependencies.

That separation is not easy because modern payments are layered. A payment may start in a mobile app, pass through identity and fraud controls, depend on cloud analytics, touch a sanctions-screening supplier, use a telecommunications provider, enter a bank core system, connect to a processor, settle through a central-bank account and later appear in customer reporting. Some of those layers are local, some European and some global. Some process personal data, some process payment instructions, some only carry messages, and some decide whether a transaction is suspicious. Data sovereignty becomes practical only when the institution can say which layer matters for which kind of continuity failure.

The European Payments Initiative and Wero are part of the same signal. EPI presents Wero as a European account-to-account payment solution and independent alternative, and DNB's strategy says Wero will roll out in the Netherlands in 2026 after EPI acquired iDEAL in 2024. That is not a replacement for DNB's settlement account. It is a retail payment substitute and autonomy project that could change the dependency map above the central-bank layer. If European retail payment instruments become more widely used, some non-European card or wallet dependence may decline. But banks will still need central-bank money, collateral management and settlement finality underneath.

The proof boundary is important. RDAP and DNS evidence proves domain registration, DNSSEC and public delivery dependencies. DNB and ECB documents prove the payment and settlement role. They do not prove internal hosting choices, private vendor contracts, incident performance, or operational data residency for TARGET-NL. The private facts that would change the judgement include DNB's and participants' supplier concentration, recoverability tests, jurisdictional data mapping, resilience of non-European vendors, and whether critical payment operations can continue during a geopolitical or cyber disruption that affects a major shared supplier.

The substitute set changes the risk, not the need

The substitute paragraph should be blunt. A commercial correspondent-banking workaround can be useful for customer payments, foreign flows, contingency routing or temporary access, but it substitutes a commercial bank balance and correspondent rule set for central-bank settlement. It may work for some flows and fail for the exact stress in which finality matters most. Euro-area shared infrastructure is both the main platform and a substitute to national isolation: it pools investment, rules and reach, but it also concentrates dependency in common services. Internal liquidity buffers reduce urgency and payment-queue pressure, but they are expensive and cannot by themselves make a payment final. Delayed settlement protects operational safety at the cost of timeliness. Manual continuity procedures preserve decision control, but they do not recreate the throughput, legal certainty or market confidence of TARGET Services.

Each substitute is therefore a way to buy time, not a way to buy the same trust. This is the central pricing point. If a Dutch bank pays for staff, controls, testing and account participation around DNB, it is not paying because no alternative exists. It is paying because alternatives move risk to places the bank may not want to hold it: correspondent exposure, liquidity cost, client delay, operational manual error, legal uncertainty or dependence on a less visible private supplier.

Competitive pressure enters through budget choices rather than market share. The bank can always decide to spend a little less on testing, train fewer treasury staff, keep thinner liquidity buffers, postpone supplier-exit planning, accept more manual workarounds or rely on group-level expertise outside the Netherlands. Those choices may look efficient until a payment stress reveals which costs were merely deferred. DNB's role is valuable partly because it makes underinvestment harder to hide. Readiness reporting, oversight, cyber testing, fraud statistics and sector exercises convert vague resilience language into work that boards can be asked to fund.

The ECB's T2 operating-hours consultation shows that the substitute question is alive, not theoretical. Stakeholders were asked in 2025 about possible extension of T2 operating hours, and the ECB published a roadmap report in May 2026. The demand behind that consultation is easy to understand. Instant payments run continuously. Securities markets, global liquidity and customer expectations are less patient than old batch windows. A system that closes for weekends or certain holidays can still be robust, but the surrounding market may want more hours, more overlap and less settlement delay. More hours, however, also mean more staffing, monitoring, maintenance complexity and incident exposure.

That trade-off is why manual procedures remain necessary even when they are incomplete. If operating hours expand, the sector may need more continuous staffing. If cyber attacks grow, banks may need more controlled fallback. If retail payments become more instant and mobile, customer expectations for reversal, confirmation and fraud handling become more demanding. If collateral management becomes more harmonised through ECMS, participants may gain efficiency while also depending more on the common system. No substitute removes the governance question. It only moves it.

Competitive pressure is also indirect. DNB is not a commercial competitor, but its account competes against the bank's own willingness to spend. Treasury executives can choose minimal compliance, larger liquidity buffers, more correspondent arrangements, more automation, more internal redundancy or deeper engagement with central-bank processes. The winning mix depends on private incident history, customer base, payment volumes, securities activity, fraud exposure and board risk appetite. DNB's public evidence supports the strong-account thesis, but private bank economics decide how much resilience each participant actually buys around it.

The strongest participants will treat the DNB account as an organising constraint, not a narrow obligation. They will ask whether payment files, collateral calls, securities settlement, fraud controls, treasury dashboards, client communication and executive escalation all still make sense if one shared service is degraded. They will measure time-to-decision, not only time-to-recovery. They will rehearse delayed settlement without normalising it. They will keep correspondent options without confusing them for finality. They will hold liquidity buffers without pretending that idle liquidity is free. That is the practical difference between owning a central-bank account and merely having one.

Public legitimacy is the scarce asset

DNB's mission page says it seeks to safeguard financial stability and contribute to sustainable prosperity in the Netherlands. It lists a smoothly functioning payment system among its tasks, along with stable prices, reliable financial institutions, resolution and advice. That public mandate changes the account's economics. A private vendor can sell uptime. A central bank sells credible continuity because it carries public responsibility when uptime fails. That responsibility is not a marketing feature; it is the source of legitimacy.

Legitimacy affects payment behaviour. Consumers keep using electronic payments because they believe the money will move, fraud will be handled, institutions will be supervised and failures will be temporary. Merchants accept cards and instant payments because they believe payment claims will settle. Banks use central-bank accounts because counterparties believe central-bank money and settlement finality are the ultimate layer under private bank money. If that legitimacy weakens, more private workarounds appear, but they are usually more expensive and less equal.

The Dutch context makes this especially visible because digital payment adoption is high and cash use is lower than it once was. DNB's strategy says cash remains important as public money and as a resilience element, but also notes that cash can no longer act as a full fallback for card payments during some outages. It recommends households keep cash for a 72-hour disruption and discusses deferred card payments and dual-provider strategies. That is not nostalgia for cash. It is an admission that resilience requires diversity. The DNB account sits in that same philosophy: one layer should not pretend to solve every continuity problem, but the central-bank layer must be credible.

Public legitimacy is also why DNB's fraud statistics matter. Publishing fraud data every six months does not make fraud disappear. It makes the problem measurable, comparable and harder to ignore. DNB says the figures are based on reports submitted by payment service providers under European requirements and that they cover about two-thirds of the market, with some methods not yet included. That caveat is valuable. It shows the public authority improving visibility without overstating certainty. For an analyst pricing the account, that is a positive signal: the authority is building public measurement around a trust problem.

The cost is political as well as operational. More resilience can mean higher payment costs, more restrictive onboarding, more expensive supplier controls, more complex fraud screening and more supervisory reporting. The public may want near-free payments and perfect resilience. Banks may want low compliance cost and broad commercial freedom. Merchants may want cheap acceptance and no outage risk. DNB sits between these preferences and has to make the trust price visible enough that the system pays it before a failure forces it.

The proof boundary is private performance

The public evidence proves DNB's mandate, TARGET-NL account role, central-bank settlement framework, oversight expectations, cyber-testing role, payment-fraud measurement, retail payment dependency and public-domain accountability. It also proves euro-area shared infrastructure scale through ECB facts on T2, T2S and TIPS. It implies that a DNB-linked account is a high-value continuity position for Dutch banks because it combines finality, liquidity, collateral, supervision and legitimacy. It does not prove the private quality of every operating process.

That boundary should discipline the valuation. Public pages do not show DNB's incident response times by participant. They do not disclose failed payment queues during stress, national help-desk service levels, participant onboarding defects, private TLPT findings, unresolved remediation plans, collateral exception rates, bank-by-bank liquidity buffers, network-provider outages, or the exact supplier map for critical settlement services. They also do not show whether individual banks treat DNB processes as strategic resilience or as a compliance minimum.

The private facts that would change the judgement are concrete. The thesis strengthens if private data show low incident recurrence, fast help-desk resolution, successful crisis exercises, clean migration rehearsals, strong collateral processing under stress, effective fraud-supervision remediation, credible supplier-exit plans and board-level ownership of payment continuity. The thesis weakens if private data show repeated unresolved incidents, brittle manual procedures, slow collateral substitutions, poor network-provider diversity, superficial cyber testing, or participant behaviour that depends on DNB legitimacy while underinvesting in its own continuity.

There is also a cost-of-capital boundary. DNB as central bank and supervisor is not a listed vendor whose payment-service margins can be modelled like a processor. The economic value sits inside avoided systemic risk, reduced liquidity uncertainty and public confidence. That makes it harder to price but not less real. A bank that avoids a major settlement disruption may not record a visible revenue line. It avoids losses, client compensation, regulatory findings, reputational damage and liquidity stress. The lack of a private margin metric is a feature of public-sector continuity, not evidence that the value is small.

Market commentary should be treated with the same discipline. Public discussion about European payment autonomy, Wero, instant payments, fraud and non-European dependencies is useful as a signal of where investment pressure is moving. It is not proof that any one vendor will fail or that any one retail scheme will win. The best reading is directional: European payment authorities and market participants are trying to reduce avoidable dependency while preserving the scale benefits of shared infrastructure. DNB's account is the Dutch settlement expression of that wider move.

The account buys time when trust is scarce

The final judgement is that DNB's payment account prices Dutch settlement trust because it gives a bank something the substitute set cannot provide in one place. It gives central-bank money, legal finality, Dutch account maintenance, Eurosystem reach, collateral linkage, supervisory attention, cyber-resilience discipline and public legitimacy. The value is highest when continuity is under stress: a cyber incident, a fraud wave, a liquidity squeeze, a migration problem, a supplier outage, an extended-hours policy change or a public-confidence shock.

The account does not remove dependency. It organises dependency. A Dutch participant depends on the Eurosystem, TARGET Services, national account processes, selected network service providers, collateral rules, messaging standards, its own internal systems and the resilience of payment-chain suppliers. That is why the account cannot be priced only as a fee schedule. It must be priced as an operating discipline. The bank pays through staff, liquidity, collateral readiness, controls, testing, supplier governance and management attention. DNB supplies the public settlement layer that makes those private investments coherent.

The substitute judgement should end where it began. A commercial correspondent-banking workaround can move some payments but cannot recreate central-bank finality. Euro-area shared infrastructure provides scale and resilience but is already part of the account's dependency. Internal liquidity buffers reduce pressure but do not settle obligations. Delayed settlement preserves caution but creates risk. Manual continuity procedures are essential but partial. These substitutes are rational only as complements. They are not replacements for the trust bundle around DNB.

For a Dutch bank treasury desk, the account is therefore worth more than the screen it uses and less than the myth of perfect safety. It is a public-sector continuity position with private costs and shared dependencies. The bank is buying the right to keep settlement credible when ordinary confidence becomes scarce. That is why DNB's payment account prices Dutch settlement trust.

Public Evidence Notes

The article relies on public materials that are strong enough to identify the operating unit and its constraints, but not strong enough to prove private unit margin or service quality. The sources below are included so the reader can distinguish official mandate, product, regulatory, technical and substitute evidence from inference. They support the public record; they do not replace private metrics on economics, reliability or retention.

Key public materials used for this judgement include: