Central Banks Are Consolidating Settlement Rails: VASP Infrastructure Is Moving the Opposite Direction
For heads of operations and CTOs at licensed VASPs, the infrastructure question has become unavoidable. Every new product launch means another vendor evaluation. Every scaling milestone reveals another integration bottleneck. The operational stack, liquidity provider, custodian, banking partner, reporting vendor, Travel Rule messaging service, wasn't designed as a system. It accumulated. And now it groans under the weight of its own complexity.
The contrast with what central banks are building could not be starker. The Eurosystem's March 2026 payments strategy outlined an architecture explicitly designed to reduce fragmentation, not accommodate it. Through initiatives like Pontes, the ECB's distributed ledger technology solution launching in Q3 2026, the aim is to deliver a single Eurosystem platform linking market DLT infrastructures with TARGET Services for settlement in central bank money. The operating principle is consolidation: one solution combining three previously explored interoperability approaches, with settlement finality anchored in T2, the Eurosystem's real-time gross settlement system.
This is not a theoretical exercise. The ECB has committed to a dual-track strategy where Pontes provides near-term settlement capability while Appia, the longer-term initiative, shapes a future-ready wholesale ecosystem expected by 2028. The exploratory work preceding this involved 64 participants conducting over 50 trials and experiments. The trajectory is clear: fewer rails, unified standards, common interfaces.
The architectural logic underpinning this consolidation is ISO 20022, the global messaging standard that creates, as the ECB describes it, "a common, data-rich language for financial communications across payments, securities, trade services and foreign exchange." The standard replaces older, fragmented protocols and enables interoperability, automation, and straight-through processing. It reduces manual intervention and improves resilience. Every major payment system in Europe now operates on this foundation.
Now consider the VASP infrastructure stack. Each component, custody, liquidity, banking, compliance reporting, Travel Rule messaging, typically runs on its own API standard, its own authentication protocol, its own error handling logic. The onboarding timeline for a single liquidity provider can stretch to months. Banking partners impose their own due diligence processes. Custodians have distinct key management architectures. None of these components were designed to interoperate natively. Integration is a manual exercise, repeated with each vendor, multiplied across each jurisdiction.
MiCA has not simplified this. The regulation, now fully applicable since December 2024 with transitional periods extending to July 2026, imposes granular requirements on custody, execution, and client asset segregation. CASPs must maintain individual registers of client positions, segregate client crypto-assets on-chain from proprietary holdings, and ensure settlement within 24 hours of execution on-ledger or by end of trading day off-ledger. These are sensible protections. But they also demand operational precision that a fragmented vendor stack makes difficult to guarantee.
The FATF's March 2026 report on offshore VASPs compounds the challenge. Uneven Travel Rule implementation across jurisdictions creates what compliance professionals call the "Sunrise Issue", where one side of a cross-border transfer has live regulatory obligations and the other does not. Attribution is uncertain. Counterparty due diligence is compromised. The compliance burden falls on the originating firm, which must build controls capable of compensating for systemic gaps that no single vendor can resolve.
This fragmentation carries quantifiable costs. Each vendor relationship adds contract negotiation time, ongoing relationship management overhead, and reconciliation complexity. Each integration point is a potential failure mode. When TARGET Instant Payment Settlement processes a transaction, it moves through a single settlement interface based on ISO 20022 standards, with 24/7 availability and no distinction between domestic and cross-border payments. When a VASP processes a trade, it often traverses multiple systems with different uptime guarantees, different message formats, and different escalation procedures.
The operational divergence matters because it affects what a VASP can actually ship. Product velocity depends on infrastructure reliability. Time-to-market for new trading pairs, new jurisdictions, new client segments, all of it bottlenecks at the integration layer. A platform that takes six months to onboard a new banking partner is not competing on equal footing with one that can do it in six weeks.
The central bank approach offers a structural template. The Eurosystem's Pontes solution enables market participants to settle DLT-based transactions with cash tokens on a Eurosystem platform or directly in T2. Delivery versus payment is enabled via the Hash-Link protocol, ensuring synchronised, all-or-none settlement across platforms. The interoperability is designed in, not bolted on.
None of this is directly replicable by a VASP. Central banks operate with different mandates, different balance sheets, different timelines. But the architectural principle, consolidation of settlement rails, standardisation of messaging, reduction of integration points, is not exclusive to sovereign infrastructure. It's a design choice available to any institution willing to prioritise it.
The question for VASP operations leaders is whether their current vendor fragmentation reflects regulatory necessity or historical accident. MiCA does not mandate five separate providers. It mandates specific operational capabilities. How those capabilities are delivered is a strategic decision.
The trajectory of institutional settlement infrastructure is toward consolidation. Central banks are engineering unified systems because fragmentation creates systemic risk, operational inefficiency, and execution uncertainty. The same logic applies to digital asset infrastructure, scaled down but not conceptually different. The VASP that treats vendor consolidation as a competitive priority, not just an operational preference, is positioning itself on the right side of a structural shift already underway in the markets it hopes to serve.
References
[1] ECB, "The Eurosystem's comprehensive payments strategy", March 2026
[2] ECB, "Pontes. Eurosystem DLT solution"
