Frequently Asked Questions

A tokenized deposit is a digital token issued by a regulated commercial bank representing a claim on fiat reserves held at that bank. It remains a bank liability, is subject to deposit insurance frameworks and prudential supervision, and can only be issued by a licensed institution. JPMorgan's JPMD (formerly JPM Coin) is the most prominent live example.

A stablecoin is a digital token whose value is pegged to a reference asset — typically the US dollar — issued by a non-bank or specialized payment institution, backed by reserves held outside the traditional banking system. The key distinction is who bears the liability and who supervises it. Tokenized deposits sit inside the existing bank regulatory perimeter; stablecoins create an adjacent category that regulators are still calibrating under frameworks like the GENIUS Act (US) and MiCA (EU).

A wholesale CBDC is a central bank digital currency restricted to regulated financial institutions — banks, payment service providers, and financial market infrastructures — for use in interbank settlement, securities settlement, and cross-border payment operations. It is the digital equivalent of reserves held at the central bank and is the CBDC design most relevant to institutional payment infrastructure.

A retail CBDC is made available directly to the general public as a digital form of cash, carrying the same sovereign guarantee as banknotes. Retail CBDCs raise complex design questions around financial privacy, bank disintermediation, and the future of physical cash — questions that wholesale CBDCs largely avoid. Post Oak Labs' advisory work focuses on wholesale CBDC architecture and its integration with tokenized A2A rails; see our A2A Payments page for deployment context.

A well-designed tokenized A2A rail is asset-agnostic at the protocol level: the settlement logic, atomic swap mechanism, and compliance layer operate independently of which monetary instrument is being transferred. In practice, institutional A2A rails are most commonly built around tokenized commercial bank deposits, which fit naturally inside the existing bank regulatory perimeter.

They can also carry wholesale CBDC where a central bank has issued one and integrated with the network, and stablecoins where they are issued by licensed entities under applicable regulatory frameworks. The practical constraint is not technical but legal and governance: each instrument type requires specific reserve verification, regulatory treatment, and participation agreements. Multi-asset rails are feasible but require careful upfront governance design.

Project mBridge was a multi-central-bank wholesale CBDC initiative originally developed in collaboration with the BIS Innovation Hub, the Hong Kong Monetary Authority, the Bank of Thailand, the Digital Currency Institute of the People's Bank of China, the Central Bank of the UAE, and later the Saudi Central Bank. It demonstrated cross-border settlement using wholesale CBDCs with sub-10-second finality under proof-of-concept conditions — one of the most cited benchmarks for tokenized settlement speed.

The BIS Innovation Hub stepped back from the project in October 2024, describing this as the project reaching operational maturity and transitioning governance to the participant central banks. The remaining participant central banks continue development under their own governance, but mBridge's current status, production roadmap, and institutional backing should be verified directly with those institutions before being cited as an active BIS-endorsed initiative. It is currently best described as an ongoing multi-central-bank pilot under a governance structure that is still evolving. See footnote 9 of the Comparison page for the full sourcing note.

Reserve verification sits on a spectrum from weakest to strongest: (1) Self-attestation — the issuer publishes reserve composition unilaterally with no independent verification. This is the weakest form and has historically been associated with reserve quality concerns in some stablecoin issuers. (2) Third-party attestation — an accounting firm reviews reserves at a point in time and publishes a letter confirming what the issuer reported. This is not a full audit: auditors confirm what they were shown, not that the reserve actually exists and is unencumbered. Circle (USDC) publishes monthly attestations of this type. (3) Full audit — auditors independently verify reserve existence, composition, and legal ownership. Rare in the stablecoin industry. (4) Cryptographic proof of reserves — a Merkle tree-based approach allowing on-chain verification that a claimed reserve balance is backed, without revealing individual account details. More common in crypto exchanges than stablecoin issuers.

Tether (USDT) has historically provided attestations rather than full audits, which remains a subject of regulatory concern. The GENIUS Act (US) and MiCA (EU) both require licensed issuers to maintain high-quality liquid reserves and undergo third-party audits, raising the floor for regulated issuers. Tokenized deposits are different: they are bank liabilities, not stablecoin claims. They do not require proof-of-reserves mechanisms — the bank's entire balance sheet is subject to standard prudential banking supervision, deposit insurance frameworks, and regulatory capital requirements. This is one reason why tokenized deposits are considered lower risk than most stablecoin instruments for institutional settlement purposes.

Tokenized A2A works alongside SWIFT — it does not replace it. SWIFT is a messaging network; it carries payment instructions but does not itself move money. Tokenized A2A is a settlement layer: it handles the actual transfer of value between participating institutions on a shared permissioned ledger. RTGS systems (operated by central banks) remain the final settlement backbone; A2A abstracts over them and uses them more efficiently via end-of-cycle net settlement.

SWIFT's 11,000-plus member network also represents global reach that tokenized A2A networks are still building toward. For corridors not yet served by A2A participants, SWIFT and correspondent banking remain the only viable option. The practical near-term vision is hybrid: A2A for corridors where network participants exist, correspondent banking for the rest.

Nostro and vostro accounts are foreign-currency accounts that correspondent banks must pre-fund — park capital in advance — so they can settle cross-border payment instructions without delay. A nostro account is held at a foreign bank (from the Latin "ours"); a vostro account is the same relationship seen from the foreign bank's perspective ("yours").

The problem for treasury teams is that this pre-funded capital sits idle between uses, earning little or nothing, while simultaneously consuming regulatory liquidity buffers under Basel III's LCR and NSFR. Industry estimates place total trapped capital globally at approximately $27 trillion (McKinsey, 2016 estimate; no industry-wide restatement has since been published, though some 2025 sources cite figures closer to $28 trillion). Tokenized A2A infrastructure replaces pre-funding with just-in-time settlement via netting cycles, freeing that capital for productive use. See the Comparison page footnote 2 for full source notes on the $27T estimate.

The four-corner model describes the minimal architecture for an interbank payment: the payer, the payer's bank, the payee's bank, and the payee. Tokenized A2A infrastructure operates at this level — the two commercial banks settle directly on a shared ledger with no intermediaries between them.

Traditional correspondent banking expands this to six, eight, or more participants by inserting correspondent banks between the originating and receiving institutions. Each added correspondent adds cost (wire fees, FX spread), processing time (batch windows, cut-off times), opacity (the payer cannot track funds in transit), and counterparty risk. The compression back to a true four-corner model is the central structural advantage of tokenized A2A rails — but it requires both institutions to be participants on the same network, which is why network reach remains A2A's primary current limitation.

ISO 20022 is the global standard for financial messaging, replacing the older SWIFT MT format with richly structured XML or JSON messages. Unlike legacy MT messages — which truncate beneficiary names, addresses, and purpose codes — ISO 20022 MX messages carry complete structured data, enabling automated sanctions screening, straight-through processing, and richer AML analytics. SWIFT completed mandatory migration to ISO 20022 for cross-border payments in stages through 2025. The US Federal Reserve also migrated Fedwire Funds Service — the largest RTGS system in the world by transaction value — to ISO 20022 on July 14, 2025.

The connection to tokenized A2A is direct: ISO 20022-formatted data travels inside the payment token on the ledger, so every transaction carries complete structured information at the point of settlement — not just a routing instruction degraded through multiple correspondent hops. This eliminates the data loss that occurs across the correspondent chain and gives every participating institution simultaneous access to the same compliance-relevant data. See the ISO 20022 page for a full technical treatment.

All three are permissioned distributed ledger platforms used in institutional finance, but they differ in architecture and privacy model.

Hyperledger Fabric uses a channel-based privacy model: transactions are only shared with nodes in a specific channel, making it well-suited for multi-party supply chain and trade finance applications requiring bilateral confidentiality between specific subsets of participants. Hyperledger Besu is an Ethereum-compatible permissioned chain using EVM smart contracts — ideal when Ethereum ecosystem tooling and future public-chain interoperability are priorities. R3 Corda is specifically designed for financial bilateral contracts: transactions are shared only on a strict need-to-know basis, with only the parties directly involved seeing the details.

For a candid, practitioner-authored comparison of these platforms — including deployment data, market sizing, and due diligence guidance — see the Post Oak Labs Enterprise Blockchain Market Briefing. Post Oak Labs does not endorse any specific blockchain or distributed ledger technology. Platform selection is a governance, regulatory, and ecosystem question as much as a technical one; the right answer depends on your institution's specific architecture, jurisdiction, and strategic objectives.

In the tokenized A2A mint-transfer-redeem cycle, FX conversion happens at the point of redemption by the receiving bank — not at each intermediary hop as in correspondent banking. The originating bank mints a token representing a claim in the sending currency; the token transfers across the ledger; the receiving bank redeems it and credits the recipient's account in local currency, applying the FX rate at that moment.

This means the originating bank or its designated FX provider captures the conversion spread — rather than losing it to correspondent intermediaries who take a cut at each hop. This is a commercial redistribution of FX revenue, not an elimination of FX costs. It typically results in more transparent, tighter spreads for the end client, and moves the FX economics from the correspondent chain back to the institutions that have the direct customer relationship.

See the A2A Tokenization Explained page for a full technical walkthrough of the transaction lifecycle. For the underlying infrastructure vocabulary, see the Glossary entry on the Mint-Transfer-Redeem Cycle.

Settlement finality is the point at which a payment becomes legally irrevocable and unconditional — when the transfer of funds is complete and cannot be unwound, reversed, or reclaimed by any party. In practice it matters because until finality is achieved, both counterparties carry principal risk: if the paying institution fails after initiating a transfer but before finality, the receiving institution may be unable to recover the funds.

In traditional correspondent banking, final settlement may take one to three business days, meaning open exposure persists for the duration. On tokenized A2A rails using atomic settlement, both legs of a transaction settle simultaneously and instantly — either both complete or neither does — eliminating the principal risk window. Note that legal finality must accompany technical finality: the contractual and regulatory framework backing irrevocability is as important as the technical mechanism. Both must be present for the risk reduction to be real.

Three different production architectures, each with different target use cases and governance models.

JPMorgan Kinexys: single-bank-issued deposit token (JPMD) on a JPMorgan-operated permissioned ledger; clients are JPMorgan's institutional counterparties; expanding to Canton Network and Base (public L2) as of January 2026. Strengths: deepest production maturity, largest daily volume, JPMorgan credit backing. Limitation: single-bank issuer model; counterparties must be JPMorgan clients or network participants.

Partior: multi-bank consortium ledger (JPMorgan, DBS, Temasek, Standard Chartered, Deutsche Bank); multi-currency settlement (USD, SGD, EUR); Asia corridor focus; open to non-bank PSPs (Nium joined 2025). Strengths: genuine multi-institution ownership; no single-bank dependency; active production flows.

Fnality: bank-funded consortium; member banks hold accounts directly at relevant central banks; tokenized representations settle against actual central bank money (£FnPS has Bank of England Settlement Finality Designation; $FnPS in development). Strengths: strongest legal finality protections; direct central bank money backing. Status: £FnPS live; $FnPS pending Federal Reserve approval.

For most Global South institutional deployments, Post Oak Labs architects for a multi-institution consortium model similar to Partior's architecture — not dependent on a single bank's infrastructure.

Central bank settlement accounts are the ultimate liquidity backstop for tokenized A2A networks. In a DLT-based net settlement model, banks settle token-layer obligations in central bank money at periodic intervals — the RTGS is not eliminated, it is made more efficient. In Fnality's model, member banks hold segregated accounts at the Bank of England (for £FnPS) or the Federal Reserve (for $FnPS once approved), with token balances representing claims on those accounts. In consortium models using commercial bank deposit tokens, central bank settlement accounts fund net positions at end-of-cycle.

The implication: A2A networks reduce the frequency and size of central bank settlement flows (through netting), but they do not remove them. Central bank approval to participate in a qualifying payment system is often a prerequisite for institutional A2A deployment in regulated jurisdictions.

SWIFT is actively pursuing an interoperability layer role. Its partnership with Chainlink CCIP provides a mechanism for SWIFT payment instructions to trigger cross-chain token movements. DLT network connections are in development. SWIFT's 11,000+ member institution reach is a significant asset that tokenized A2A networks are still building toward.

The likely near-term architecture: SWIFT messaging initiates payment instructions for corridors where A2A participants exist; the A2A network handles settlement; SWIFT's data standards (ISO 20022) travel inside the token. This is a compatibility-layer improvement, not SWIFT replacement. Post Oak Labs frames this as a structural settlement upgrade that integrates with SWIFT messaging, not a competing network.

The G20 Cross-Border Payments Roadmap, managed by the BIS Committee on Payments and Market Infrastructures (CPMI), is the multilateral policy framework driving global improvement in cross-border payment speed, cost, transparency, and access. Its targets: reduce average retail remittance cost below 3%; make cross-border payments available 24/7; eliminate payment opacity.

Tokenized A2A institutional rails are one of the primary technical pathways endorsed by the Roadmap — particularly for eliminating correspondent intermediaries (cost), enabling continuous settlement (speed), and carrying ISO 20022-structured data through the entire payment chain (transparency). Institutions evaluating tokenized A2A infrastructure can reference the CPMI Roadmap when engaging central banks and regulators — it reframes the conversation from 'novel technology experiment' to 'implementation of multilateral policy commitment.'

Four reasons: (1) Privacy. Public chains expose transaction data to all participants and observers; permissioned ledgers restrict data visibility to the parties directly involved in a transaction. An interbank payment should not be readable by every other participant on the network. (2) Finality. Public proof-of-work and proof-of-stake chains have probabilistic finality — a transaction can technically be reversed while the chain reorganises. Permissioned ledgers (Corda, Hyperledger Fabric, Canton) offer deterministic finality: once committed, a transaction cannot be reversed. Settlement risk requires deterministic finality. (3) Regulatory accountability. Permissioned networks require KYC and legal entity verification for node participation; public chains do not. Institutional payment infrastructure must know who its counterparties are. (4) Performance and cost predictability. Permissioned ledgers can handle institutional throughput without mempool congestion, gas fee volatility, or block time uncertainty.

This does not mean public chains have no institutional role. Tokenized MMF products like BlackRock BUIDL and Franklin Templeton BENJI use public chain infrastructure for token issuance and secondary transfer. But the settlement layer for institutional A2A cross-border payments uses permissioned infrastructure for the reasons above.

Programmable money is a digital monetary asset whose transfer can be governed by embedded logic — conditions that must be satisfied before the payment executes or releases. In practice this means payment instructions can carry rules that execute automatically on the ledger, without manual intervention or reliance on a third-party escrow agent.

Concrete institutional examples: (1) Conditional cross-border payment that auto-executes on delivery confirmation, enabling delivery-versus-payment for trade finance without a letter of credit intermediary. (2) Tokenized MMF redemption automatically triggered when a corporate treasury balance falls below a defined threshold, keeping the treasurer fully invested up to the moment liquidity is needed. (3) Supplier payment released upon receipt of a third-party quality attestation from a certified inspection body — contractual certainty without manual approval queues. (4) Scheduled FX hedging executed atomically at a pre-agreed rate on a specific date, eliminating settlement risk on the FX leg.

Importantly, institutional programmable money use cases are typically simple, auditable conditionals — not the complex protocol logic seen in DeFi. Simpler logic means smaller attack surface, easier audit, and more predictable regulatory treatment.

The GENIUS Act (Guiding and Establishing National Innovation for US Stablecoins Act), enacted in 2025, is the first dedicated federal framework for payment stablecoins in the United States. It requires US-regulated stablecoin issuers to maintain 1:1 reserve backing in US dollars or short-term Treasuries, prohibits algorithmic stablecoins, and subjects issuers to Bank Secrecy Act and AML obligations. Banks with federal charters can issue payment stablecoins under OCC oversight; non-bank issuers above $10 billion in outstanding stablecoins fall under federal supervision, while smaller issuers may operate under state charters.

The Act broadly aligns US stablecoin regulation with the EU's MiCA framework for e-money tokens and brings significant legal clarity for banks evaluating stablecoin programs. The GENIUS Act was signed into law on July 18, 2025; its requirements entered into force on August 4, 2025.

Requirements vary by jurisdiction but typically include:

(1) Primary regulator approval to operate distributed ledger infrastructure and issue or hold digital payment tokens — this may require a DLT sandbox approval, no-action letter, or amendment to the bank's operating license. (2) AML/BSA compliance framework extensions covering on-chain transaction monitoring and the shared identity attestation architecture. (3) Data protection compliance (GDPR in Europe, equivalent frameworks elsewhere) for cross-border sharing of KYC attestations. (4) Central bank approval in some jurisdictions to participate in any payment system that touches central bank settlement accounts.

The technology readiness and regulatory readiness must advance in parallel. Post Oak Labs advises on regulatory sequencing as a core part of our engagement framework — mapping the approval path before infrastructure build work begins is a material time and cost saver.

Open banking regulation — PSD2 in the EU, equivalent frameworks in the UK, Australia, and parts of Asia — creates API access obligations for retail banking data and payment initiation at the consumer account level. Tokenized A2A operates at a different layer: institutional interbank settlement, not retail account access. The two frameworks are complementary, not the same thing.

In Post Oak Labs' primary target markets — Latin America, Africa, the Caribbean, South Asia — PSD2-style mandatory open banking frameworks do not uniformly apply; open banking is at varying stages of development across these regions. Where open banking APIs do exist, they can serve as a distribution channel for institutional A2A products (for example, a corporate treasurer accessing real-time A2A settlement status via their bank's API), but the underlying settlement infrastructure is architecturally distinct from the open banking framework itself. Banks evaluating A2A should not conflate the two in their regulatory analysis.

Post Oak Labs focuses on the Global South — primarily Latin America, the Caribbean, Africa, and South Asia — where correspondent banking de-risking has been most acute, remittance costs highest, and the structural demand for alternative institutional settlement infrastructure most evident.

Within those regions, the firm has active production deployments in the Caribbean, where three jurisdictions have launched live retail CBDCs and the Eastern Caribbean Currency Union represents a unique multi-jurisdictional opportunity: a single currency, eleven countries, a live CBDC infrastructure, and no unified commercial bank tokenized A2A layer on top of it yet. South Asia is a second active focus given the scale of inbound remittance flows. Advisory work also covers trade-corridor engagements in Africa and Latin America. See the A2A Payments page for regional detail.

De-dollarization — the trend of reducing dependence on the US dollar in trade settlement and reserves — is a structural driver of demand for local-currency payment infrastructure in Post Oak Labs' target markets. Several governments and central banks in Latin America, Africa, and South Asia are actively seeking to reduce dollar dependency, and tokenized local-currency infrastructure is one of the tools available to them.

The local-currency tokenized MMF product is directly relevant here: it allows banks to offer corporate clients yield-bearing settlement assets denominated in local currency, reducing the need to hold dollar-denominated instruments for settlement purposes. Post Oak Labs takes no political position on de-dollarization as a policy goal. The practical observation is that institutional demand for local-currency alternatives to USD-denominated settlement instruments is real and growing, and tokenized infrastructure is better positioned to serve that demand than traditional correspondent channels — which are themselves predominantly dollar-denominated.

The crossover point depends on the specific corridor, the bank's existing correspondent banking costs, and the fixed costs of joining or building the A2A network. As a directional benchmark: Post Oak Labs' production deployments demonstrate 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) via tokenized A2A, against a 2.5–5%+ total cost in comparable correspondent banking corridors (inclusive of wire fees, FX spread, and nostro maintenance). At that differential, the per-transaction economics favor A2A from relatively modest volumes.

The more important threshold is network investment recovery: deploying integration infrastructure, compliance frameworks, and regulatory approvals for A2A participation requires upfront investment that typically needs $50–200M+ in annual corridor volume to recover within a reasonable timeframe, depending on implementation complexity. For institutions already operating high-volume B2B corridors, the case is strong. For low-volume corridors, a shared-network model with other corridor participants typically improves the economics materially. Contact us for a corridor-specific analysis.

Correspondent banking requires institutions to maintain pre-funded nostro balances in every active corridor — capital that sits idle between uses, earning below-market returns and consuming Basel III liquidity buffers. Industry estimates put total globally trapped nostro/vostro capital at approximately $27 trillion (McKinsey, 2016 estimate; no industry-wide restatement has since been published).

Tokenized A2A infrastructure enables just-in-time settlement via intraday netting cycles: participating institutions submit payment obligations to the shared ledger throughout the day, and net positions settle against central bank reserves at end-of-cycle via RTGS. This significantly reduces the need for pre-funded corridor balances (residual liquidity requirements remain for intraday buffers and central bank settlement account balances), freeing that capital for productive use while maintaining the central bank settlement backbone. The shift from pre-funding to JIT settlement is one of the primary capital efficiency arguments for institutional tokenized payment rails.

No core banking replacement is required. The integration architecture has four components: (1) API gateway — translates your core's internal data model into ISO 20022-structured messages compatible with the A2A rail; typically built on your existing API management infrastructure. (2) Tokenization module — mints settlement tokens against core balances at the point of outgoing payment; redeems tokens and credits core on receipt; can be a bank-built module or a vendor-supplied SDK depending on platform. (3) Token custody interface — manages private key infrastructure for signing on-chain transactions; requires HSM (hardware security module, FIPS 140-2 Level 3 or equivalent) for production deployment. (4) Reconciliation and reporting — ensures DLT state and core ledger state remain synchronized; feeds into existing regulatory reporting. Integration timeline in Post Oak Labs' production deployments has ranged from 4–9 months depending on core banking platform and regulatory sequencing. No existing infrastructure is decommissioned.

No. Tokenized A2A sits above the core banking system as a settlement and messaging layer. It integrates via APIs and does not require core replacement. Banks connect their existing core — Temenos, Finastra, Oracle FSS, Mambu, or any other — to the A2A network through an integration layer. The core continues to hold the books of record and manage customer accounts; the A2A network handles interbank settlement messaging and token lifecycle.

The practical integration work involves building or procuring an API gateway that translates between the core's internal data model and the ISO 20022-structured messages that travel on the A2A rail, and implementing a token custody or tokenization module that mints and redeems settlement tokens against core balances. This is non-trivial engineering but is well within the scope of a standard systems integration project. It does not require decommissioning any existing infrastructure.

Project Agorá is a BIS Innovation Hub research initiative involving seven major central banks — the Federal Reserve Bank of New York, Bank of England, Bank of Japan, Bank of Korea, Banque de France, Monetary Authority of Singapore, and Swiss National Bank — together with a private sector cohort of commercial banks. It explores whether tokenized commercial bank deposits and wholesale central bank reserves can be integrated on a unified programmable platform to make cross-border payments faster and cheaper. Agorá is a proof-of-concept program, not a live production system, and its multi-central-bank backing makes it one of the most significant institutional signals that deposit-token-based A2A settlement is on the long-term horizon. See: BIS Project Agorá overview.^[fn1]

Project mBridge was a multi-CBDC cross-border settlement pilot originally co-developed with the BIS Innovation Hub and four central banks. The BIS Innovation Hub stepped back in October 2024, describing this as the project reaching operational maturity; the remaining central banks continue development independently. Unlike Agorá (which uses tokenized commercial bank deposits alongside central bank reserves), mBridge was built around wholesale CBDC as the primary settlement instrument. The two projects represent different architectural philosophies for the same end goal. See the Glossary entries for Project Agorá and Project mBridge for more detail.

Atomic settlement means that two legs of a transaction — the transfer of value and the transfer of the corresponding asset or payment — happen simultaneously and indivisibly on the ledger. Either both succeed or neither does. There is no window between delivery and payment during which one party holds the asset and the other has not yet received funds.

In payment contexts, the relevant form is Payment versus Payment (PvP): both currency legs of an FX transaction settle atomically. In securities contexts, it is Delivery versus Payment (DvP). The institutional significance is the elimination of principal risk — the risk that a counterparty fails after delivering its leg but before receiving the other. This risk window is material in traditional correspondent banking, where a payment may take 1–3 days to achieve finality. See BIS CPMI guidance on PvP:^[fn2] Strategies for achieving a safer, faster, and cheaper cross-border payments. See also the Glossary entry on Atomic Settlement.

No — privacy architecture is one of the defining design decisions in permissioned institutional ledgers, and different platforms take different approaches.

R3 Corda is the most restrictive: transactions are shared only with the parties directly involved (on a need-to-know basis). A bank on the same Corda network cannot see the transactions of two other banks unless it is a party to them. Hyperledger Fabric uses channels: a subset of participants can share a private ledger within a broader network. Hyperledger Besu supports private transactions via the Tessera privacy manager, but its EVM base means more visibility by default unless explicitly restricted. In all cases, a notary or ordering service may see transaction metadata (if not the full content) to prevent double-spend — a privacy boundary that requires careful governance design.^[fn3] See the Enterprise Blockchain Market Briefing for a platform-by-platform privacy comparison.

A tokenized money market fund (tMMF) is a traditional money market fund whose units are represented as digital tokens on a distributed ledger, enabling near-instant subscription and redemption, 24/7 transferability, and use as on-chain collateral. USD-denominated tMMFs already have substantial institutional traction — BlackRock's BUIDL fund surpassed $1 billion AUM in 2024, and Franklin Templeton's BENJI fund has operated on public blockchain infrastructure since 2021.^[fn4]

On A2A rails, a local-currency tMMF can serve as a yield-bearing settlement asset: corporate treasurers park surplus liquidity in a tMMF at end of day and redeem it intraday for settlement — eliminating the opportunity cost of holding non-earning settlement balances. The effect is strongest in emerging markets where local-currency instruments with same-day liquidity are scarce. See Tokenized Money Market Funds on A2A Rails for Post Oak Labs' full architecture treatment.

Each participating institution remains independently responsible for its own AML obligations under the law of its jurisdiction. A shared ledger does not transfer regulatory liability — it provides richer data to discharge it. The compliance architecture in a well-designed tokenized A2A network typically has three layers:

(1) On-boarding / identity layer: KYC and beneficial ownership verification is performed by each bank for its own customers; the attestation is cryptographically signed and travels with the payment token, reducing re-verification burden at each hop. (2) Transaction monitoring: each institution runs its own transaction monitoring software against the on-ledger data it can see; the richer ISO 20022 structured data substantially reduces false positives compared to legacy MT message screening.^[fn5] (3) Network-level governance: the consortium governance agreement typically requires all participants to maintain FATF-compliant AML programs and grants the network operator authority to suspend participants that lose regulatory standing. See A2A Tokenization Explained for the compliance layer architecture.

Atomic settlement eliminates the most dangerous failure scenario in traditional correspondent banking — the situation where one bank delivers its leg of a transaction and then fails before the other bank delivers its leg. On a tokenized A2A network using atomic settlement, there is no exposed window: the transaction either completes entirely or is rolled back entirely by the ledger's consensus mechanism. The receiving bank never holds an asset for which it has not yet been paid, and vice versa.

The residual failure risks on a tokenized network are different in nature: pre-minting exposure (a bank mints tokens against fiat reserves that are subsequently frozen by a regulator) and network access failure (a bank's validator node going offline). These are addressed through consortium governance provisions — including participant collateral requirements, network failover design, and orderly exit procedures — rather than through the atomic settlement mechanism itself. Operational resilience requirements for participating institutions are typically specified in the network participation agreement.^[fn6]

Correspondent banking de-risking — the withdrawal of global correspondent banks from serving smaller or higher-risk jurisdictions — is one of the primary drivers of demand for tokenized A2A infrastructure. The World Bank, BIS, and FSB have all documented the decline in active correspondent banking relationships since 2011, with the sharpest concentration in the Caribbean, Pacific Islands, and parts of Africa.^[fn7]

Tokenized A2A networks are not immune to the same dynamic, but the structure is different. Rather than a large correspondent bank making a binary decision to exit all respondent banks in a jurisdiction, an A2A consortium governance framework can set risk-tiered participation criteria and require participating banks to maintain FATF-compliant programs — without one participant's risk assessment determining another's access. The governance design of an A2A consortium is therefore directly relevant to whether smaller or frontier-market institutions can access the network. This is a design choice, not an inherent property of the technology.