Post Oak Labs · Infrastructure Comparison Framework
Tokenized A2A, stablecoin infrastructure, and correspondent banking occupy distinct layers of the institutional payment stack. This framework is a fully consolidated reference for banks and corporates evaluating where tokenization fits in their architecture and revenue model.
Project mBridge / Jasper-Ubin — see fn. 9
The Institutional Payment Stack
The most common mistake banks make is treating these three as substitutes. They are not. Stablecoin/CBDC infrastructure is the monetary primitive: what digital money is. Tokenized A2A is the institutional rail: how banks move it at scale. RTGS is the final settlement backbone beneath everything. The confusion costs institutions time, money, and the wrong vendor relationships.
3–5 intermediary hops per payment · 2–5 day settlement on non-gpi routes (SWIFT gpi: ~60% within 30 min on connected corridors) · high pre-funding requirements · limited data fields per transaction
Account-to-account tokenized settlement, near-instant finality, ISO 20022 data richness. B2B cross-border, corporate treasury, interbank settlement, tokenized MMF distribution.
Central bank digital currency, private stablecoin rails, reserve management, programmable money. The enabling base layer on which A2A can optionally operate.
Pix, FedNow, UPI, SPEI, FPS — the retail consumer layer. Not the institutional A2A layer.
Permissioned DLT, public L1 blockchains, central bank RTGS[12]
The monetary primitive: a tokenized representation of fiat value. What the settlement asset is: bearer instrument, programmable on-chain value, CBDC unit, or tokenized deposit. Does not, by itself, solve how regulated banks move it at scale.
The institutional payment rail: orchestration, routing, and settlement workflow above the asset layer. How regulated banks, central banks, and large corporates transfer value efficiently across borders. Can carry stablecoins, CBDCs, or tokenized deposits as the underlying asset.
The settlement backbone: central bank money on central bank books. Not replaced by A2A; abstracted and used more efficiently. A2A nets positions across participants intraday and end-of-day, reducing gross RTGS settlement volumes while preserving finality in central bank money.
Comparison 01
A2A is a payment rail: the mechanism by which value moves between bank accounts. Stablecoin is a monetary instrument: what moves on the rail. A bank that conflates the two will architect for the wrong problem. Where the two models differ on a structural dimension, a contextual note explains whether the difference is a design trade-off or a fit-for-purpose distinction. Neither model has a universal advantage over the other; each is optimized for a specific position in the stack.[1]
| Dimension | Tokenized A2A | Stablecoin Infrastructure |
|---|---|---|
| Role in Stack | Orchestration, routing, and settlement workflow layer (application/network layer) | Base asset and settlement primitive layer (asset/ledger layer) |
| Position in Stack | Operates above stablecoin/CBDC as institutional B2B settlement rail | Enabling/base layer; programmable money that A2A rails can optionally carry |
| Nature of Instrument | Tokenized deposit: programmable claim on the sender bank's fiat reserves; fiat never leaves the bank balance sheet during the transaction | Privately issued digital bearer instrument representing fiat value; backed by reserves and operates entirely on-chain |
| Core Function | Moves funds between bank accounts (B2B, interbank, treasury) via tokenized claims | Represents tokenized fiat value as an on-chain liability; enables direct P2P transfer |
| Balance-Sheet Treatment | Stays on issuing bank's balance sheet; funds remain inside the banking system and support traditional lending | Off-balance-sheet for banks; reserves held with the stablecoin issuer, removing deposits from the banking system Trade-off[2] |
| Settlement Mechanism | Tokenized claim transfer, then net settlement via RTGS at end-of-cycle; fiat never moves between banks during the transaction itself | Direct on-chain transfer of tokenized value via blockchain consensus; settlement is the transfer itself |
| Issuer Identity | Regulated commercial bank or central bank (known, licensed entity) | Nonbanks (Circle, Paxos), bank subsidiaries, or regulated banks (JPMorgan, BNY Mellon) |
| Reserve Backing | 1:1 fiat reserves held at the originating bank; transparent custody under banking supervision | Varies by issuer: cash, Treasuries, crypto, or algorithmic. Reserve quality and transparency differ significantly by issuer. Context[3] |
| Redemption Rights | Redeemable at par with the originating bank; clear legal claim under banking law | May trade at discount or premium in secondary markets. Redemption terms vary by issuer. Regulated issuers are moving toward standardized at-par redemption obligations. Context[3] |
| Network Type | Closed, permissioned ledgers among known, KYC'd institutional participants | Public or open blockchains, or private/permissioned ledgers, depending on the issuer and deployment |
| Access Model | Restricted to regulated participants: banks, corporate treasury, central banks Context[4] | Open wallet-based access: any party with a compatible wallet can hold and transfer, enabling consumer remittances and DeFi applications Context[4] |
| Regulatory Oversight | Full banking supervision; settlement is a bank liability | Evolving. The GENIUS Act (US, signed July 18, 2025; in force August 4, 2025), MiCA (EU) establishing stablecoin-specific frameworks; not equivalent to banking supervision yet |
| Programmability | Smart contracts for conditional payments, trade finance, escrow, and compliance automation within the permissioned network | Fully programmable on public EVM chains; broad DeFi composability; conditional payment logic via smart contracts |
| FX Revenue | FX conversion captured at point of redemption by the originating bank, not lost to intermediaries Trade-off[4] | FX conversion typically handled by the user or issuer at on-chain or off-ramp point; varies by deployment |
| Data Standard | ISO 20022: rich structured data per transaction; automated reconciliation; ~30% fewer exceptions vs. legacy MT[5] | On-chain data only; off-chain compliance data managed separately; ISO 20022 integration not standard |
| Primary Use Cases | Institutional B2B, interbank settlement, corporate treasury, trade finance, tokenized MMF distribution | Consumer remittances, DeFi liquidity, merchant settlement, crypto-native commerce, cross-border B2C |
Comparison 02
Tokenized A2A and correspondent banking both address the same problem: moving money between banks across borders. They differ fundamentally in how they achieve it. This table reflects the structural differences relevant to institutional architecture decisions. Where a difference is a design trade-off rather than a binary win, a contextual note explains why.
| Dimension | Tokenized A2A Rails | Correspondent Banking / RTGS |
|---|---|---|
| Topology | Direct "four-corner" model: sender bank, settlement ledger, receiver bank; no intermediary banks on the token transfer path itself | Fragmented multi-hop network; payment passes through 3–5 or more correspondent banks, each adding fees and processing time[7] |
| Intermediaries and Fees | 0–1 logical intermediaries; approximately 0.2% in direct settlement fees in selected B2B corridors where Post Oak Labs has deployed production infrastructure (excludes FX conversion fees, which are captured as originating bank revenue)[8] | 3–5 intermediary hops per payment; layered fees at each (SWIFT + correspondent + FX spread + nostro maintenance); total 2.5–5% plus FX spread[7] |
| Settlement Speed | Seconds to minutes; under 10 seconds demonstrated in multi-CBDC corridors (Project mBridge, PoC conditions)[9] | 2–5 business days for final settlement on legacy non-gpi routing; SWIFT gpi: ~60% of payments credited to end beneficiaries within 30 minutes, and nearly all within 24 hours on connected routes [9]. Delays beyond 24 hours occur primarily in corridors with capital controls, legacy back-office systems, or time-zone mismatches. These are not typical of standard gpi routing[9] |
| Liquidity Pre-funding | Near-zero for participants; just-in-time settlement via netting cycles; frees capital currently held in correspondent pre-funding[2] | Heavy reliance on pre-funded nostro/vostro accounts across all active corridors; industry estimates put total trapped globally at approximately $27 trillion (McKinsey, 2016 estimate; some 2025 sources cite ~$28 trillion)[2] |
| Capital Efficiency | High; reduced trapped liquidity; capital freed for productive lending and investment | Low; significant capital lock-up in correspondent balances earning below-market returns while idle. At 5% rates, $1B in a non-interest-bearing nostro costs roughly $50M/year in lost yield (actual opportunity cost varies by treasury management practice; some balances earn partial overnight returns, but typically well below market) Context[2] |
| Operating Hours | Typically 24/7 on DLT/permissioned ledger, subject to network risk policy and bilateral agreements | RTGS: limited to operating hours and maintenance windows; correspondent layers add timezone, cut-off, and batch processing effects |
| FX Handling | On-ledger real-time FX at point of redemption; originating bank captures the spread rather than losing it to correspondents | Opaque spread markups at each correspondent hop; spread captured by intermediaries rather than the originating bank Trade-off[4] |
| Data per Transaction | ISO 20022: substantially richer structured data than legacy MT; automated reconciliation; approximately 30% fewer exceptions vs. MT-based workflows[5] | Legacy MT messages carry far fewer data fields than ISO 20022; manual reconciliation required; high exception rates; zero real-time payment status visibility[5] |
| Reconciliation | Automated, ledger-native via ISO 20022 rich data; immutable audit trail from token minting | Manual, exception-heavy; post-hoc audit trail reconstruction from multiple systems at multiple institutions |
| Programmability | Full conditional logic: escrow, milestone payments, trade finance automation, atomic settlement | Static instructions only; no conditional logic or programmable execution in legacy MT messaging |
| KYC/AML Overhead | Shared attestation across network participants; graduated KYC tiers; compliance data travels with the payment | Repeated independently at each correspondent hop; each bank runs its own checks on the same counterparties Trade-off[10] |
| Audit Trail | Immutable from token minting; regulatory reporting embedded at the ledger layer from inception | Fragmented; reconstructed from multiple systems at multiple institutions after the fact |
| PCI Scope | Reduced; actual account data never transits the tokenized rail | Full account data transits through all intermediaries in the correspondent chain |
| Settlement Mechanism | Token transfer on-ledger; net settlement via RTGS or bilateral netting at end-of-cycle; RTGS is retained as the final settlement backbone | Payment-by-payment SWIFT instructions; gross RTGS settlement on central bank books for each individual transaction |
| Network Reach | Limited to participating institutions currently; A2A network effects are still building Trade-off[11] | SWIFT connects over 11,000 financial institutions across 200-plus countries; established global reach with deep liquidity pools. That is a genuine structural strength of the correspondent model[11] |
| Governance and Risk | Closed multilateral platform with shared rules; consistency enforced by protocol; participants are known and permissioned | Bilateral correspondent relationships and SLAs; credit and FX risk held in intermediaries; RTGS operates with a central bank/sovereign backstop |
For operational risk questions see the FAQ, particularly What happens when a participant fails and Is tokenized A2A the same as Pix or FedNow.
A2A is not an RTGS replacement. It is an enhancement. RTGS remains the final settlement layer (central bank money); A2A is the transaction layer that uses RTGS for net settlement at end-of-cycle. RTGS is not eliminated. It is abstracted and used far more efficiently. That shift drives fewer intermediaries, less capital lock-up, faster perceived settlement, and richer compliance data. The primary near-term limitation of A2A is network reach: SWIFT's 11,000-plus member institution footprint represents a global coverage that tokenized A2A networks are still building toward, and correspondent banking remains the only viable option for corridors not yet served by A2A participants.[11]
Quick Reference
The correct infrastructure choice depends on the scenario, counterparty type, market maturity, and regulatory environment. No single infrastructure is universally superior. Each is fit for specific use cases, and the most capable bank architectures combine all three in the correct dependency order. Correspondent banking retains a role wherever A2A network reach has not yet extended.
Stablecoin/CBDC = enabling layer (what is the digital money?). A2A = institutional payment rail (how do banks move it at scale?). RTGS = settlement backbone (how do positions net finally?). The most compelling institutional deployments combine all three in the correct order of dependency, not as competing bids for budget but as complementary layers of a single coherent architecture. Correspondent banking retains a genuine and important role for global reach in corridors where A2A network participants have not yet been established.
Post Oak Labs works with commercial banks, central banks, and large corporates that are ready to design and deploy tokenized A2A infrastructure. We have built production systems in the Caribbean and South Asia. We know what works.