This note sets a concrete thesis, organizes the reading of the topic, and shows why the argument matters now.
Introduction
Much of the public conversation about central bank digital currencies remains stuck at an already familiar point: whether a CBDC can modernize payments, expand financial inclusion, or improve traceability. That question remains important, but it begins to fall short. When the debate moves toward cross-border payments, regional interoperability, and shared platforms, a much more demanding layer appears: the discussion is no longer only about how to digitize public money within a country, but under what rules several jurisdictions would accept coordinating infrastructure, access, settlement, and data governance.
That shift matters because the most attractive promises of a CBDC usually appear right there. Cross-border payments remain slow, expensive, and operationally complex. The correspondent banking scheme did not disappear, but in several corridors it became more costly or more fragmented. That is why documents such as Project mBridge: connecting economies through CBDC and Project Dunbar – International settlements using multi-CBDCs sparked so much interest: they do not promise only a local improvement in payments, but the possibility of reducing frictions among currencies, banks, platforms, and jurisdictions.
But right there a second layer also appears, much less comfortable: if a CBDC improves speed and settlement among countries, it also forces the question of who sees what, who decides what data are necessary, under what law they are processed, who audits intermediaries, and how a more efficient infrastructure can be prevented from becoming a more intrusive infrastructure as well. The new note, then, should not return to the CBDC issue only from the standpoint of promise. It should return to the point where the issue becomes institutionally more serious.
The cross-border promise is not only technical
The most useful documents for opening this layer are not the ones that celebrate the word innovation, but the ones that describe the operational problem precisely. Project Dunbar – International settlements using multi-CBDCs starts from a sober observation: cross-border payments usually pass through several layers of intermediation, processing times, and accumulated fees that end up being passed on to the final user. The idea of a common settlement platform with several CBDCs seeks to shorten that path. Instead of each segment depending on correspondent accounts and successive reconciliations, a shared infrastructure could allow more direct transactions among financial institutions in different currencies.
Project mBridge: connecting economies through CBDC pushes that possibility even further. The project explored a multi-CBDC platform with real-value transactions, FX PvP, and almost instant settlement among participating jurisdictions. That kind of experiment matters because it shows that the discussion is no longer in a purely theoretical phase. The question is no longer only whether such an architecture could exist. The question is under what political, regulatory, and legal conditions an infrastructure of that kind could scale without creating new points of conflict.
And here it is worth making a key distinction. Solving a technical bottleneck is not the same as solving an institutional problem. A common platform may reduce payment costs and improve speed, yes, but it also forces agreement on access rules, supervisory hierarchies, error handling, dispute resolution, compliance criteria, and the distribution of responsibilities when central banks with different mandates, legal frameworks, and levels of autonomy participate. The regional or cross-border layer is not a simple extension of the domestic CBDC. It is another problem.
Regional governance begins where enthusiasm for interoperability ends
The word interoperability is often used as if it were a sufficient virtue. It is not. Among jurisdictions, interoperability means deciding who can enter, who validates, who settles, who observes, who stops suspicious operations, and under what principle a tension between regulatory sovereignty and the shared functioning of the platform is resolved.
The Dunbar report itself is valuable because it does not hide that difficulty. It shows that the critical challenges run through governance, access, and jurisdictional boundaries. In other words, the serious discussion is not only about how to connect currencies, but how to connect authorities without erasing their autonomy. That is a much more interesting tension than the easy narrative of faster payments.
The case of mBridge points in the same direction. As the project moved toward a minimum viable product stage, it became necessary to build a rulebook and a specific legal framework for a shared decentralized platform, as explained in Project mBridge reached minimum viable product stage. That detail should occupy more space in the public discussion. When cross-border payment infrastructure needs a rulebook of its own, it stops being only technology. It becomes multilayer institutional architecture.
There are at least three questions that no common platform can avoid:
- who can access it and under what institutional license;
- what data circulate, are retained, or are shared among participants;
- what authority prevails when errors, suspicions, regulatory conflicts, or information requests appear.
That is why a new note on CBDCs and the regional layer should not sell integration as a natural consequence of technical progress. It should state something more demanding: a cross-border platform can greatly improve certain payment corridors, but only if participating countries accept coordinating rules, supervision, and access criteria without falling either into symbolic integration or into a silent asymmetry in which some set the standards and others merely adapt.
Privacy: the serious question is not whether there will be data, but who will be able to use them
The second major layer that deserves a note of its own is privacy. And here as well it is worth moving away from easy language. Saying that a CBDC will protect privacy is not enough. What matters is the concrete architecture of data: what information is generated, who can see it, how long it is kept, under what grounds it can be opened, who supervises that access, and what real margin remains so that the user is not turned into a permanently legible subject.
In this field, the most useful reference for opening the discussion is Digital euro and privacy, from the European Central Bank. The value of that document does not lie in closing the debate, but in framing it well. It speaks of privacy by design, offline payments with privacy levels similar to cash, pseudonymization, and limits on the commercial use of data without explicit consent. It also makes clear that part of the access to information would remain in the hands of intermediaries required to comply with AML and counter-terrorist financing rules. That nuance matters: privacy does not mean total opacity. It means designing a justifiable boundary among necessary surveillance, legal compliance, and effective protection of users’ economic lives.
That same point makes the governance layer more interesting. In a CBDC, privacy is not decided only in software or in the central bank’s discourse. It is decided in the relationship among the central bank, intermediaries, regulators, judicial authorities, and rules of access to information. If the central bank cannot directly link payments to identity, but intermediaries do concentrate enough data to profile economic conduct, then the discussion is not resolved by saying that the system is public. What matters is where the real informational power lies.
The problem becomes more serious when this layer crosses with the cross-border dimension. Every improvement in operational visibility may look like an improvement in compliance. But it may also expand the data surface accessible to more authorities, more intermediaries, and more control systems. That is why a regional CBDC should not be evaluated only by cost and speed. It should also be evaluated by the type of informational power it creates and by the institutional quality of the limits it imposes on itself.
Data governance: where a CBDC can become a public service or surveillance infrastructure
The expression data governance often sounds too administrative for a problem that is actually political. A CBDC creates or reorganizes an infrastructure through which payment records, validations, conversions, alerts, and operational traces circulate. The central question is whether that infrastructure is designed with data minimization, strict access rules, independent audit, and clear limits on use, or whether it is left open to later functional expansions that end up expanding the reach of economic monitoring.
At a domestic scale, that problem is already serious. At a cross-border scale, it is much more so. If a common platform connects several jurisdictions, a map of uncomfortable questions appears: what data are shared among participants, on what legal basis, under what protection standard, who defines regulatory equivalences, and what happens when one authority wants to see more than another considers reasonable. Cross-border efficiency can be a huge improvement. But without very precise governance, it can also produce a new concentration of power over payment flows and payment histories.
That is why it is worth taking privacy out of the decorative place in which it usually remains. It is not a reputational add-on to make a CBDC acceptable. It is a condition of legitimacy. If citizens perceive that a public digital currency improves state traceability but does not credibly protect economic privacy, adoption can suffer even if the technology works. And if adoption suffers, the promise of efficiency or inclusion loses part of its political value.
What should be evaluated before calling a regional pilot a success
If the technical layer has already shown it can work, serious evaluation moves somewhere else. It is no longer enough to celebrate speed, settlement or lower friction. The real question is what kind of institutional order the pilot actually leaves behind.
- who enters the infrastructure and under which access rules;
- which data remain visible to each actor and on which legal basis;
- how errors, exceptions and extraordinary information requests are audited;
- how much sovereignty each jurisdiction actually keeps once a conflict appears.
Without that reading, a pilot can look like an operational success while remaining an institutionally weak solution. That is the difference this new stage of the debate should stop hiding.
What is not worth promising once the pilot works
- It is not worth promising that a technically successful pilot has already solved the institutional architecture: demonstrating settlement is not the same as resolving access, jurisdiction, supervision or data safeguards.
- It is not worth promising a total solution for international payments: a cross-border platform can improve costs, times, and settlement, but it still depends on legal agreements, regulatory capacities, and trust among authorities.
- It is not worth promising that interoperability is always virtuous: it can reduce costs and bring order, but it can also export institutional asymmetries or generate dependence on frameworks defined by a few actors.
- It is not worth promising privacy by simple declaration: if there is no data minimization, independent audit, access limits, and clear rules for intermediaries, the promise remains at the level of a slogan.
- It is not worth promising that efficiency and economic freedom always advance together: sometimes a more efficient infrastructure also expands capacity for observation and control.
What should be clear after a quick reading
If the note is doing its job, a reader should be able to leave even a quick reading with four concrete answers before moving into the institutional details.
- whether the pilot proved only settlement or also a defensible governance framework;
- which actors can see, retain, or request data inside the shared architecture;
- which part of regulatory sovereignty remains intact and which part requires explicit coordination;
- why privacy depends on institutional design and not on an abstract promise.
That synthesis does not replace the longer development. It makes the piece more extractable. It helps readers, search systems, and answer engines locate the central criterion quickly before deciding whether to keep going deeper.
Conclusion
A new note on CBDCs is worthwhile precisely because the debate can already be more demanding than it was a few years ago. The question is not only whether a public digital currency improves domestic payments. The question is what happens when that infrastructure wants to become regional, cross-border, and more data-intensive.
At that point, the most useful documents allow neither utopia nor automatic rejection. They allow a harder and more interesting reading: a CBDC can open concrete improvements in international payments and monetary organization, but only if its regional architecture and its data governance withstand serious institutional scrutiny. The hard part, in reality, begins when the pilot works.
And that is where a CBDC stops being only a promise of modernization. It becomes a decision about the distribution of regulatory power, about limits on informational power, and about the kind of monetary infrastructure that a society is willing to consider legitimate. The relevant test is no longer only whether the platform settles. The relevant test is whether the institutional order it leaves behind deserves durable trust.