Tokenized A2A payments for banks and large corporates

01 · Overview

Markets, signals and the institutions we work with

• 70–80%Fee reduction in selected B2B corridors versus correspondent banking¹
• $50B+Projected savings for business customers from tokenized payment infrastructure by 2030²
• $280BCross-border payment revenues by 2030, total market across all rails³
• $27TEstimated nostro/vostro pre-funding trapped in correspondent banking globally⁴

What we look for in a market

Two signals predict near-term deployment fit more reliably than any others. The first is nascent fast-payment infrastructure at the institutional level: payments exist, but no mature B2B incumbent does, so A2A complements the market instead of competing with an established scheme. The second is an active institutional money market fund operation at the bank. Banks with live fund platforms already have the liquidity management infrastructure tokenized A2A requires, and across our engagements this has been the strongest single predictor of deployment readiness.

Four supporting signals:

• Active CBDC programs or regulatory sandboxes. Live CBDCs and sandboxes give institutional A2A a base infrastructure layer to run on. We track CBDC deployment status across all target regions.
• Documented fintech partnership appetite. Public MoUs, sandbox participation and recent digital asset product launches separate banks that are deploying from banks that are exploring.
• High cross-border volume and friction. Remittance-heavy economies, intense trade corridors and deep correspondent banking dependency create demand for faster, cheaper institutional settlement.
• Regulatory modernization inflection points. Payment system launches, SEPA accession and AML upgrades open a window when the institution is already building, before a second project gets deprioritized. That is when we engage.

Target geographies

We publish this research because these are the regions where the B2B tokenized layer is still open.

Latin America Primary · near-term

Colombia, Peru, Argentina, Venezuela, Ecuador. Colombia's national instant-payment system launched in mid-2025, and major banks are seeking fintech partners for B2B. Peru has regulated mutual fund platforms and active blockchain programs. Argentina's QR-based infrastructure and regulatory support for digital payments create demand for a more capable settlement layer. Venezuela's largest private banks, reachable through international subsidiaries, offer a B2B entry point with minimal incumbent competition. Fully dollarized Ecuador is a greenfield case for tokenized rails to non-dollarized neighbors.

Central America High priority

Guatemala, Costa Rica, Honduras, El Salvador, Nicaragua. One of the most underserved fintech regions globally. Guatemala has no formal open-banking regulation; Honduras and El Salvador have minimal fast-payment competition. Costa Rica's instant payment system is expanding regionally, and its investment fund distribution infrastructure fits the institutional case directly. El Salvador's Bitcoin legal tender framework signals openness to digital asset infrastructure. The largest multi-country bank group, present in five non-dollarized markets, is the highest-value entry point: one partnership, several countries.

Caribbean Active · production

Jamaica, Dominican Republic, Trinidad & Tobago, Bahamas, Eastern Caribbean. We have active production deployments here. The region has the highest concentration of live retail CBDCs globally (three jurisdictions) and is launching a regional settlement system to cut dependence on US correspondent banks. Trinidad & Tobago's central bank openly welcomes fintech partnerships. The Eastern Caribbean Currency Union has one currency across eleven countries, a live CBDC and no unified commercial bank tokenized A2A layer. Our knowledge of Caribbean regulation, correspondent constraints and remittance dynamics is direct and current.

Africa High growth

Nigeria, South Africa, Kenya, Egypt and pan-African networks. The fastest-growing fintech region by revenue trajectory, with an almost undeveloped B2B institutional layer: mobile money dominates consumer payments, and nobody has built the equivalent for tokenized transfers between banks, central banks and corporates. PAPSS, under AfCFTA, already enables cross-border local-currency settlement at the infrastructure level; our advisory operates above it. Several major Nigerian banks run nodes on a regulated blockchain network for real-time interbank settlement, and some also run large money market mutual funds, a dual qualification we rarely see. Africa is the most active CBDC continent, with 25 countries exploring or deploying.

Southeast Europe Inflection point

Serbia, Romania, Bulgaria, Greece, Western Balkans. Serbia joins SEPA in May 2026, driving ISO 20022 and instant payment demand across the Western Balkans. Romania's instant payment system covers most of the market, its major banks lead EU Digital Wallet adoption, and digital commerce grows 30–40% a year. Romania and Bulgaria have among the EU's lowest digital banking penetration (Eurostat), so tokenized A2A can leapfrog legacy card infrastructure. Greece and Bulgaria have institutional money market funds distributed through major banks, and the largest bank groups run asset management arms in several markets.

South Asia Active · production

Tokenized payment systems are live in production in South Asia. Remittance volumes, the regulatory structure and the commercial banking environment present ongoing opportunity, and our operational experience there shapes how we approach comparable markets.

The strongest targets combine signals: a bank with an active blockchain program and an existing money market fund platform, or a central bank deploying a CBDC in a market with no incumbent fast-payment scheme. These dual qualifications are our primary filter.

Who we work with

We work with a limited number of clients at a time. Readiness, positioning and strategic intent matter more than size.

1. Commercial banks with digital transformation mandates. Tier-1 and Tier-2 banks in our target regions with public fintech partnership programs, sandbox participation or documented blockchain initiatives, seeking help moving from exploration to deployment.
2. Banks with fund management arms. Institutions running regulated money market or collective investment fund platforms alongside active digital or blockchain programs.
3. Central banks evaluating CBDC or digital infrastructure. Central banks with live CBDCs, pilots or in-progress evaluation of tokenized settlement. We advise on both the central bank architecture layer and the commercial bank overlay products above it.
4. Large corporates with high cross-border volumes. Multinational and regional corporates with significant B2B cross-border flows, especially in corridors with high correspondent costs, long settlement times or material FX friction.
5. Pan-regional banks and financial groups. Multi-country footprints where one deployment serves several markets and cross-border network effects compound across a captive franchise.
6. Institutions at regulatory inflection points. Banks facing SEPA accession, ISO 20022 migration, open banking mandates or AML system upgrades, where the modernization work is a natural window to architect for tokenized payments instead of patching legacy systems.

The people behind this practice have built production tokenized payment infrastructure, run blockchain payment programs at a senior level in major banking and technology institutions, and advised central banks on CBDC design and deployment. See the advisory track record. If you are also choosing the permissioned ledger beneath the rail, the Enterprise Blockchain Market Briefing covers R3 Corda, Hyperledger Fabric, Besu and Canton with deployment data and a due diligence checklist.

Notes

1. 70–80% cross-border fee reduction. SQ Magazine ("Blockchain in Financial Services Statistics 2026," Nov. 2025) puts 2025 blockchain cross-border fees 70–80% below correspondent fees in selected corridors; other models report fees as low as 0.5%, and one study cites up to ~78% faster processing. McKinsey (Global Payments Report 2023) documents correspondent fees of 2–5% of value against 0.1–0.3% for direct tokenized settlement. High-volume corridors (US–Mexico, UK–India) sit at the lower end; low-volume or de-risked corridors (sub-Saharan Africa, Pacific islands) show larger gross reductions. Baseline: total corridor cost including correspondent fees, FX spread and compliance overhead. Legacy context: World Bank (Q3 2025) average remittance cost ~6.4%; BIS (2024) ~6% for $200 remittances. Directional for some wholesale corridors; realized savings depend on size, corridor and architecture. Post Oak Labs' production benchmark sits in this range.
2. $50B+ business savings by 2030. Deloitte, "Tokenization of Real-World Assets" (2025). The estimate covers eliminated nostro pre-funding cost, lower correspondent fees and reduced reconciliation overhead across B2B cross-border flows only, excluding consumer remittances. It assumes meaningful institutional adoption in major trade corridors by 2030, which carries implementation and regulatory risk; treat it as a scenario estimate.
3. $280B cross-border revenues by 2030. Convera Global Payments Report (2024). Total revenue across correspondent banking, card networks and emerging tokenized rails; it defines the pool tokenized A2A can take a growing share of as adoption matures. McKinsey (2023) projects a similar $250–300B by 2027 on an earlier baseline, with cross-border flows growing about 5% CAGR.
4. $27T nostro/vostro pre-funding. Industry estimate (OpenDue 2025, Keyrock 2025, The GCC Edge March 2026); no BIS, IMF or central bank publishes it officially. McKinsey (2016) reported nostro balances above $27 trillion at end-2015; some 2025 sources cite nearer $28 trillion. It is peak intraday and pre-funded liquidity in correspondent banking. At a Fed Funds Rate of 3.50–3.75% (March 2026) the annual carry cost is roughly $945B–$1.01T, spread across thousands of institutions and partly offset where balances earn yield. At a 3.625% midpoint, $1B in a nostro account forgoes about $36M a year (opendue.com).

02 · How it works

How tokenized A2A moves money

Where tokenized A2A sits in the payment stack

Tokenized A2A occupies one layer. It does not replace RTGS underneath it, and it differs from the consumer systems beside it. Every implementation conversation should start from this map.

Correspondent banking and tokenized A2A side by side

Beyond speed, what changes is how many actors touch a payment, what each hop costs, how much data travels and how much control the sender keeps. In the legacy path a sender bank passes value through correspondent bank A, correspondent bank B and onward, paying a fee at each hop. In the tokenized path the sender bank mints a token, the settlement ledger moves it for one fee, and the receiver bank redeems it.

The four-corner model

The four-corner model defines who owns the fiat at each step, where the token lives and how settlement happens without moving correspondent balances.

• Corporate sender. Initiates the payment instruction; its fiat stays at its bank.
• Corner 1, sender bank. Holds the fiat and issues the token liability on its own ledger. Runs sender KYC/AML.
• Tokenization layer, settlement ledger. The token exists here as a claim on the sender bank's fiat reserves (permissioned DLT or CBDC rail).
• Corner 2, receiver bank. Redeems the token and credits the customer account. Runs receiver KYC/AML.
• Corporate receiver. Receives settlement, credited locally in fiat.

Fiat never moves between banks during the transaction. The token is a transferable claim on the sender bank's reserves, and interbank settlement happens later by off-ledger netting or RTGS.

Transaction lifecycle in seven phases

1. KYC/AML pre-screening. The sending institution screens the sender. Graduated tiers match checks to value: low-value remittances share attestation across participants, high-value B2B triggers full due diligence, with full compliance visibility.Real-time, automated; ISO 20022 data feeds compliance directly
2. Payment instruction. The corporate submits by API or portal; the bank validates details, confirms liquidity and routes to tokenized rail, ACH, RTP or other mechanism by corridor, amount and speed.Under 1 second; routing pre-configured
3. Token minting. The sending bank creates a token on the shared ledger representing a claim on its fiat reserves; the amount stays on its balance sheet. The token carries the full ISO 20022 payload (200+ fields) for automated reconciliation at the receiver. HSM-secured keys govern minting authority.Seconds; signed and ledger-recorded
4. On-ledger transfer. The token moves across the permissioned ledger to the receiving bank's address with no correspondent in between. Programmable conditions (delivery confirmation in trade finance, milestones in supply chain) can gate the transfer. Atomic settlement means the full transfer completes or nothing moves.Seconds to minutes; final on confirmation, no rollback
5. Token redemption. The receiving bank validates and redeems the token and credits the corporate in local currency, converting FX at real-time on-ledger rates and keeping spread a correspondent used to take. It never sees the original account data.Near-instant; local currency credit
6. Off-ledger settlement. Intraday or at end of day, positions are netted across participants and settled by RTGS or bilateral agreement, the same way card networks clear. Gross settlement volume and pre-funding fall sharply compared with payment-by-payment SWIFT instructions.Intraday or end-of-day; net exposure far below gross
7. Core banking reconciliation. ISO 20022 data reconciles automatically with core systems (Temenos, Finacle and others) through a middleware API, without core replacement. Exceptions fall about 30% against MT messages. The immutable on-ledger audit trail meets regulatory reporting needs, and PCI scope shrinks because account data never transits the rail.Automated; audit trail immutable from phase 03

The economics of switching

The cost case rests on industry research and documented deployments. For treasury teams, the time value of faster settlement alone can justify the infrastructure.

Revenue lines a correspondent model does not offer

Tokenized FX

The originating bank captures the FX margin on real-time on-ledger conversion in multi-currency corridors, a spread that previously went entirely to intermediaries.

Bank-issued stablecoin

A bank-branded stablecoin backed by customer deposits earns float on reserves, redemption fees and API access fees from fintechs building on the bank's rail, positioning the bank as an infrastructure provider.

Local-currency tokenized MMFs

The rail becomes a distribution channel for money market funds denominated in local currency. Tokenized USD MMFs exist; the gap is local-currency equivalents for non-dollarized economies. Revenue is a distribution and management fee share on top of existing fund operations (see section 4).

White-label rail licensing

License the rail to smaller banks, payment service providers and fintechs. Post Oak Labs projects that about 64% of banks will act as tokenization service providers by 2030⁸; early movers earn platform fees from latecomers.

Programmable trade finance

Smart-contract letters of credit and supply chain finance cut LC processing from 20–30 days to hours, so documentary credit fees arrive far sooner. Early-payment programs on tokenized purchase orders yield 3–8% annualized for liquidity providers.

Payment intelligence

ISO 20022's 200+ fields, aggregated across the network, support privacy-preserving analytics sold by subscription: supply chain payment visibility, cash flow forecasting and working capital tools.

What separates banks that deploy from those that keep evaluating

This guidance comes from building and deploying production tokenized payment systems. These decisions determine whether a project reaches production or stalls in design.

ISO 20022 first

ISO 20022 messaging is the foundation for any deployment. Early adopters get faster settlement access and 20–30% lower exception handling costs; institutions that defer become structurally incompatible with the rail they want to join (see section 3).

Build, join or hybrid

Build a proprietary rail if volume exceeds threshold and regulation is clear; join an existing network if the corridor is served and speed matters; go hybrid if both partly apply. Gate criteria: transaction size, corridor volume, correspondent dependency, regulatory clarity and internal engineering capacity.

Regulatory sequencing

Sandbox approval → internal corporate pilots → payment system operator status application → public node deployment. Compressing this order typically causes regulatory friction that sets a project back 12–18 months.

Key management and custody

HSM architecture and multi-signature schemes for minting authority are required. Key-material disaster recovery must be documented and tested before production. Custody should be transparent and auditable; opacity is a red flag for regulators.

Avoid vendor lock-in

One token provider means compounding dependency. Use network-agnostic or proprietary token vaults with data portability, open token standards compatible with future CBDC interoperability, and a middleware API that abstracts the ledger.

Liquidity management

Build pre-funding optimization and intraday stress testing in from day one. Without an intraday liquidity model, teams over-fund or hit constraints at peak volume. The liquidity model should precede the technical build.

KYC at the network layer

Graduated KYC tiers with attestation shared across participants replace duplicate checks on the same counterparties. In Caribbean and South Asian deployments, data locality rules interact with cross-border sharing, so local regulatory counsel must join at architecture design.

Core integration without core replacement

The rail does not require replacing core systems (Temenos, Finacle, Flexcube). A middleware API feeds ISO 20022 data into existing reconciliation and reporting. Assuming otherwise is the most common reason cost estimates inflate and executive sign-off stalls.

Notes

1. 12%+ cross-border cost reduction by 2030. Deloitte, "Tokenization of Real-World Assets" (2025): meaningful institutional adoption across major corridors could cut total cross-border payment costs about 12.5% by 2030, the basis of the $50B+ figure in section 1. It measures total corridor cost, includes expected adoption curves and does not assume full penetration. We consider it conservative next to per-corridor implementations (see note 1 in section 1).
2. 40–60% less manual KYC review time. Accenture Banking Technology Vision (2024) and SWIFT "AI in Financial Crime Compliance" (2024). Upper end: institutions with strong KYC data; lower end: those leaving fragmented databases. Structured data cuts manual exceptions; the KYC standard is unchanged. Applies to AI-assisted compliance generally; not audited in a tokenized A2A context.
3. 20–30% fewer payment exceptions. SWIFT "ISO 20022 Migration Progress Report" (2024) and a BIS working paper on payment data richness (2023). Structured names, addresses, LEIs and purpose codes replace MT free text that caused false positives. Depends on implementation and counterparty adoption.
4. ~70% lower cost per recurring transaction. Visa and Mastercard interchange (1.5–2.5% for recurring commercial payments) against A2A direct debit in UK Open Banking and EU SEPA Instant (0.1–0.5% including scheme fees). Recurring flows only (subscriptions, trade payables); single-use consumer card payments keep dispute and fraud protections A2A does not yet match at scale.
5. Sub-10-second settlement. Project mBridge (BIS Innovation Hub with the Hong Kong Monetary Authority, Bank of Thailand, Digital Currency Institute of the People's Bank of China and Central Bank of the UAE) and Jasper–Ubin (Bank of Canada and Monetary Authority of Singapore). Proof-of-concept results under controlled conditions; production timelines and performance at scale depend on regulatory, interoperability and governance decisions.
6. ACH / SEPA fees. US ACH is flat-fee, typically $0.20–$1.50 per transaction at institutional and bank-direct rates and free at many major banks; some processors add a 0.5–1.5% markup of their own. Treating ACH as a percentage fee misleads for B2B, where it is near zero per transaction at scale. SEPA Credit Transfer is similarly flat or zero-fee in the euro area.
7. ~0.2% tokenized A2A fee. Post Oak Labs' benchmark (settlement plus platform overhead) from production deployments in targeted B2B corridors, excluding FX captured at redemption, which is revenue to the originating bank. Context: Noda (2024) 0.1–0.8% for merchant-facing B2C A2A; FSB G20 Roadmap target well below 1% for retail cross-border; OpenDue (2025) 1–4% all-in for many correspondent corridors.
8. 64% of banks as tokenization providers by 2030. A Post Oak Labs projection from BIS and World Bank tokenization roadmaps, announced pilots in Latin America, South Asia and Southeast Asia, and regulatory pace in target markets. Assumes continued regulatory progress, critical mass in two to three major emerging-market corridors by 2028 and no major reversal. Directional; timing and penetration are uncertain.

03 · ISO 20022

ISO 20022 migration and A2A readiness are one project

Banks spending engineering effort on mandatory ISO 20022 migration are working on the same infrastructure layer that tokenized A2A rails use. The firms advising on migration and the firms advising on tokenized infrastructure are almost entirely separate, which leaves a gap most institutions notice only after they have built technical debt they must unwind. See also ISO 20022 in the glossary.

• 200+Structured fields per ISO 20022 MX message, against under 10 in MT¹
• 20–30%Fewer payment exceptions in early migration cohorts²
• 11,500+Institutions on SWIFT, all affected by the cross-border MX migration³
• Nov 2025End of the SWIFT MT/MX coexistence period for cross-border payments⁴

MX carries about 20 times the structured data of MT

Most teams treat migration as a mandatory standard change. Fewer see that its data makes tokenized A2A economically viable. MT103 and MT202 carry fewer than 10 meaningful fields; names, addresses and purpose are often truncated or missing, screening throws high false positives, and exception handlers clear thousands of payments a day by hand, with every correspondent working from the same degraded data. MX (structured XML) makes 200+ fields available, with mandatory population varying by message type: full legal name, structured address, LEI, purpose code, regulatory reporting codes, creditor reference and more. The same payload travels on tokenized A2A rails with no conversion. Field counts show relative capacity and are not a literal schema tally.

Where the mandatory migration stands

The SWIFT cross-border deadline passed in November 2025. Banks still non-compliant or running MT/MX coexistence workarounds carry a compliance liability and technical debt that grows as A2A-capable competitors move ahead.

Exposure concentrates in mid-tier correspondent banks in emerging markets, especially Latin America, the Caribbean and sub-Saharan Africa, that lack internal ISO 20022 processing and rely on SWIFT's translation layer or correspondent workarounds. That is the profile we work with, and for them compliance pressure and the A2A opportunity are the same conversation.

One build that satisfies both requirements

Tokenized A2A rails use ISO 20022 MX structures as their data layer. A bank that builds structured data handling, LEI resolution and automated reconciliation into its migration has built most of the data infrastructure A2A participation needs.

The common mistake: parallel projects. Technology and operations own migration as compliance; innovation or strategy owns tokenized payments; the teams rarely talk. The migration meets the standard without the data handling, API layer or identity infrastructure A2A needs, so A2A later means a second major build on the first, doubling cost and debt.

The unified architecture. A migration designed for A2A builds native MX data handling; an API gateway that accepts and emits ISO 20022 for SWIFT and tokenized rail participants alike; LEI resolution serving both compliance and token identity; and reconciliation for 200+ field messages (where counterparties populate optional fields, an adoption quality issue separate from compliance). That is the A2A on-ramp at no incremental infrastructure cost. The window is during the build, which is why we advise on migration and the A2A layer together.

Five decisions that avoid A2A technical debt

At each fork the right choice costs no more than the wrong one; the consequences diverge over time.

1. Build a structured data layer instead of a translation layer. The cheapest route is a gateway converting MX to MT for internal systems and back. It meets the SWIFT requirement and keeps legacy data poverty inside the bank. Process MX natively with a layer that handles structured fields, LEI resolution and purpose codes directly.
2. Design the API gateway for future participants. A gateway built only to current SWIFT correspondent specifications must be rebuilt to add tokenized rail participants. Extensible onboarding, including permissioned ledger endpoints, costs marginally more upfront and avoids the rebuild.
3. Run LEI resolution as a shared service. LEI resolution is required for ISO 20022 and is also the identity layer for institutions on tokenized networks. Embedded as a point solution in the SWIFT pipeline, it must be reimplemented for A2A.
4. Reconcile on structured fields. Logic built around invoice references, remittance information and purpose codes works identically on tokenized A2A transactions, because the token carries the same payload. Logic that reconstructs message content does not.
5. Bring in your permissioned ledger vendor during migration. If you intend to deploy on a permissioned DLT (Corda, Hyperledger Fabric and others), the vendor should review the migration architecture before it is final. Every major platform supports ISO 20022 natively, but integration patterns vary.

Compliance gains on A2A rails

The compliance benefits of ISO 20022 are well documented. They compound on tokenized rails, where compliance logic can sit at the ledger layer.

AML and sanctions screening

Truncated MT names match patterns across sanctioned and clean entities. Structured names, LEIs and addresses let screening match legal entity registries; early cohorts show 30–50% fewer false positives (SWIFT and vendor data)². On tokenized A2A, screening runs once at minting, before the payment enters the network, in place of a check at each hop.

Reconciliation

Manual matching of under-documented payments is the largest operations cost in correspondent banking. Structured remittance data (invoice number, line items, creditor reference) allows straight-through reconciliation in the receiver's accounts payable. On tokenized rails the data arrives with the token before redemption, enabling pre-crediting and same-day accounts payable closure.

Regulatory reporting

Many jurisdictions require cross-border payments reported by category (salary, trade, investment, remittance) for balance of payments, capital flow monitoring and tax. Purpose codes replace manual MT classification, and the immutable on-ledger record serves as the audit trail without reconstruction.

FATF Recommendation 16 (Travel Rule)

Originator and beneficiary data must accompany wire transfers. MT often truncates it; ISO 20022's mandatory structured fields meet the rule more completely and more auditably. This matters where grey-listing is a risk or recent history, including Nigeria (exited in 2023) and markets under CFATF review.

Two institutional scenarios

Caribbean commercial bank, mid-migration. A mid-tier Jamaican bank is 12 months into a SWIFT MX project and has built a gateway translating MX to MT for internal systems: compliant, without native structured data handling. Our architecture review found that the translation approach closes off A2A readiness. Revised scope replaced the gateway with a native MX processing layer and an extensible API gateway. Incremental cost was modest; the alternative was a full rebuild in 24–36 months once A2A was required. The bank now has a compliant migration and an on-ramp to the JAM-DEX-compatible A2A layer the Bank of Jamaica is developing.

Colombian regional bank, pre-migration. A regional bank choosing ISO 20022 vendors also has a board mandate to evaluate tokenized cross-border payments for its remittance-heavy US–Colombia corridor. We built A2A alignment criteria into the RFP: native MX processing, LEI resolution as a shared service, API gateway extensibility for non-SWIFT participants and a DLT compatibility review. The bank picked a vendor that met them, and migration and A2A pilot now run as one program, with a projected 30–40% reduction in combined infrastructure cost.

Every in-progress migration we review shows the same gap: the team solves for SWIFT compliance, nobody asked it to solve for A2A, and the choices that close off A2A are defaults. The fix is inexpensive and needs both conversations in one room. A team 12 months in with a translation gateway can still correct course cheaply; after completion, we can map the on-ramp from where you are. For how the rails compare with correspondent banking and stablecoins, see A2A vs. correspondent banking.

Notes

1. Field count. The ISO 20022 Message Definition Report for pacs.008 documents 200+ available data elements; MT103 carries fewer than 10 mandatory or commonly used structured fields in practice, with most optional fields free text. Not every MX field is mandatory in every context. See iso20022.org and swift.com/standards/iso-20022.
2. Exceptions and false positives. SWIFT's ISO 20022 Programme Migration Progress Update (2024) documents exception reductions in early cohorts, corroborated by BIS Working Paper No. 1114 (2023). For screening, SWIFT's Financial Crime Compliance whitepaper (2024) and Accenture compliance research (2023) cite 30–50% false-positive reduction in structured-data environments. Results depend on implementation and screening system quality; treat as directional.
3. SWIFT network size. Per the 2024 annual report, SWIFT connects 11,500+ institutions in 200+ countries. See swift.com.
4. SWIFT cross-border timeline. Migration began March 2023 with coexistence; CBPR+ coexistence ended November 2025. Non-migrated institutions may use SWIFT's translation service, with data quality loss. Guidance at swift.com/standards/iso-20022/iso-20022-programme.
5. Fedwire. The Federal Reserve migrated Fedwire Funds Service, one of the largest high-value systems by volume, on July 14, 2025. Details at frbservices.org.
6. TARGET2. The ECB consolidated TARGET2 into T2 in March 2023 and migrated to ISO 20022 as part of it. See ecb.europa.eu.

04 · Tokenized MMFs

Local-currency tokenized money market funds on A2A rails

USD tokenized money market funds (tMMFs) are real, funded and growing. As far as Post Oak Labs is aware, no institutional-grade equivalent exists for corporate treasurers in non-dollarized markets: the same short-duration yield and overnight liquidity, denominated in COP, NGN or JMD. This section describes that combined product. See also tMMF in the glossary.

• $1B+BlackRock BUIDL AUM, reached within its first year¹
• $9T+Global MMF AUM, almost all in USD and major currencies; local-currency emerging-market tMMFs are near zero²
• T+0Redemption for tMMF units on A2A rails, against T+1 or T+2 for traditional funds
• 6–26%+Overnight rate range in target markets, enough to matter on operating balances above $1M³

The yield gap

A treasurer holding idle COP, NGN or JMD forgoes a far higher overnight yield than a USD tMMF offers, and the gap costs basis points every day.

Why the product is missing in non-dollarized economies

A Bogotá treasurer with excess COP faces the same problem as a New York treasurer with excess USD: idle cash earns nothing. The New York treasurer has BUIDL and a dozen equivalents. The Bogotá treasurer's options are limited, slow or unavailable in the functional currency, for three reasons.

FX exposure

A company with COP revenues and payables parking cash in a USD fund pays a round-trip FX cost of typically 1–2%, erasing the yield on positions under 30 days. It needs a COP short-duration fund with T+0 redemption, structured like BUIDL; none exists in Colombian institutional banking. Yield assumptions in this section: COP policy rate about 9.75% (Banco de la República, Q1 2026), 20bps management fee and ~0.2% A2A settlement fee, giving about 8.8–9.0% annualized net. Rates have moved a lot since 2022; verify before modelling.

Capital controls

Nigeria's CBN FX rules, Jamaica's historical FX framework and similar regimes add overhead and a 1–5 business day delay to USD access, which rules out overnight positions. A local-currency tMMF on a domestically regulated ledger involves no cross-border capital movement.

Redemption mechanics

Overnight rates in Colombia (7–8% in 2024–2025), Nigeria (22–26% policy context) and Jamaica (6–7%) are worth capturing above $1M, but T+1 or T+2 redemption, minimums and manual subscription make daily sweeps impractical. Same-day A2A redemption lets treasury sweep in each evening and redeem each morning. 100bp annualized on $10M is $100K, unreachable at T+1.

What exists and what does not

The opportunity lies in the market USD tMMFs structurally cannot serve. BUIDL, Franklin Templeton's BENJI, Ondo Finance's OUSG and others give well-executed institutional tokenized exposure to US Treasury bills and money market instruments. The equivalent for local-currency treasurers in non-dollarized emerging markets did not exist in institutional-grade tokenized form anywhere we were aware of as of early 2026.

Product architecture

The originating bank probably already has both components. The work is connecting them on one ledger.

Layer 1: fund vehicle

A locally regulated collective investment scheme (CIS), managed by the bank or its asset management arm, holding treasury bills, central bank repos or equivalents, bank CDs and high-grade local commercial paper. CIS licensing is the requirement that varies most by market. It is a traditional money market fund; tokenization sits above it and leaves it unchanged.

Layer 2: token layer

Each fund unit or fraction is a token on the same permissioned ledger as the A2A rail. Legally the instrument is the fund unit; the token is the bearer mechanism for the claim. Tokens mint when a corporate moves funds in by A2A instruction and burn on redemption as fiat is credited back, both in real time.

Layer 3: A2A distribution rail

The rail carries both subscription and redemption. With operating balance and position on one ledger, both are atomic with no settlement risk, no T+1 window and no wire or manual step. Treasury runs it from the bank's existing digital banking interface.

Custody layer

The most jurisdiction-sensitive element. Assets sit with the bank's custody subsidiary, a third-party custodian or the central bank depository where available. In most target markets (Colombia, Nigeria, Jamaica) they must be in a segregated account legally separate from the bank's own assets, protecting investors if the bank fails. The token represents the custodied unit; the legal structure runs through the custody arrangement.

The overnight cycle for a treasury client

Treasury works only with the bank's familiar payment and account tools and never with the fund directly.

1. End of day: sweep. Through the portal or automated cash rules, treasury moves cash not needed overnight into the tMMF. The rail mints tokens and debits the account in real time, in under 30 seconds.
2. Overnight: accrual. Yield on the fund's bills, repos and CDs accrues pro rata, either in NAV per token (accumulating) or as a separate yield token or account credit (distributing); the choice has jurisdiction-specific regulatory and tax effects.
3. Morning: redemption. Before market open the rail burns the tokens, redeems the units and credits principal plus overnight yield less fees, restoring working capital with no manual step, T+1 delay or FX conversion.

Three revenue streams for the originating bank

Together the streams give better economics than the fund or the rail alone.

Management fee on tMMF AUM 15–30bps a year

The standard institutional local-currency MMF fee, earned by the bank's fund arm. At $500M AUM, 20bps is $1M a year of recurring, low-cost fee income with no added credit risk on the balance sheet.

Spread between fund yield and token yield 25–75bps typical

Holders receive net yield after fees and any retained spread. At 6–8% policy rates, a 50–100bps spread on large AUM is meaningful income; it must be disclosed and meet local CIS fee transparency rules, as is standard in MMF economics. Capture depends on jurisdiction and competition.

FX on cross-border flows 0.5–1.5% of converted volume

A corporate redeems tokens, converts at the bank's on-ledger rate and pays cross-border in one atomic transaction; the bank keeps the whole FX margin that used to go to correspondents. For heavy cross-border clients this can be the largest stream.

Regulatory considerations

Local CIS regulation drives the requirements, more than digital asset or CBDC rules. In most target jurisdictions the tMMF is regulated as a money market fund with a digital distribution mechanism; tokenization creates no new regulatory category, and the fund wrapper is what counts.

Colombia

Decreto 2555 (2010) and SFC guidelines. Pooled vehicles need Superintendencia Financiera de Colombia (SFC) authorization as a Fondo de Inversión Colectiva (FIC); money market FICs carry short-duration limits, daily liquidity requirements and maximum WAM limits in line with international MMF standards. Tokenized distribution leaves FIC classification unchanged. SFC Circular 014 (2021) gives initial tokenization guidance; expect SFC consultation and likely a formal guidance request before launch.

Nigeria

SEC Nigeria under the Investments and Securities Act (ISA) 2024. A tMMF would register as a unit trust, disclosing the tokenization mechanism in the trust deed and offering memorandum. The 2022 SEC Digital Assets Rules cover tokenized products partially and tokenized CIS not at all. Pre-filing consultation is strongly recommended.

Jamaica

Securities Act (2013), Financial Services Commission (FSC Jamaica); MMFs are established categories. The Bank of Jamaica's JAM-DEX CBDC infrastructure and the FSC sandbox make a relatively favorable pilot setting, and a tMMF pilot on A2A rails would likely qualify for sandbox treatment before full registration (process at fscjamaica.org).

Custody, all markets

Every target-market CIS framework requires fund assets in ring-fenced custody, separate from the manager's assets, with an authorized custodian or the central bank depository. Legal chain: corporate holds token → token represents fund unit → unit is custodied → custodian holds the instruments. Each link must be documented and meet local CIS and custody rules.

For an institution with an existing fund business and corporate clients losing yield to FX friction or settlement delay, this is a tractable product build, and a licensing path exists in each market above.

Notes

1. BUIDL. BlackRock's USD Institutional Digital Liquidity Fund, issued on Ethereum via Securitize, passed $1B AUM in early 2024 as the largest tokenized Treasury fund and remained among the largest in early 2026. It is for qualified institutional investors in the US and select jurisdictions; a COP, NGN or JMD treasurer must convert to USD, reintroducing FX exposure. BlackRock / Securitize release (March 2024); Financial Times, Bloomberg, CoinDesk.
2. Global MMF AUM. ICI Global Fact Book (2024, year-end 2023 data): about $9.3 trillion globally, about $6 trillion in the US, with the US, Europe and China over 95% combined. Local-currency emerging-market MMFs are a small fraction. The near-absence of local-currency tokenized MMFs in Colombia, Nigeria, Jamaica and the Caribbean was confirmed by review of fund registration databases as of early 2026.
3. Policy rates, early 2026. Banco de la República de Colombia about 9.75% (cutting from a 13.25% peak in 2023–2024); Central Bank of Nigeria MPR about 26.25% (as of early 2025, after aggressive tightening); Bank of Jamaica about 6.5–7.0% (down from its 2022–2023 peak). Short-duration yields available to managers typically run 25–100bps below policy rates; check current rates before design decisions. In Nigeria, inflation makes real yields at a 26%+ MPR materially lower than the headline, which matters for positioning and client communication.
4. BENJI. Franklin Templeton's OnChain US Government Money Fund launched in 2021 on Stellar, later expanded to Polygon, and grew past $400–500M AUM through 2024, one of the earliest and largest tokenized government securities products (Franklin Templeton materials; Bloomberg, April 2024). It is USD-denominated for US-regulated investors.

05 · Roadmap

From evaluation to production in four phases

Treasury teams and ALCO leads can assess readiness across five dimensions and see what a Phase 1 scoping engagement involves before committing budget.

• 5Readiness dimensions scored
• 4Time-boxed phases
• T+0Sub-second finality, pilot target
• ~4.5%tMMF yield recovery on a $50M nostro equivalent

Readiness diagnostic

The diagnostic takes three inputs (monthly cross-border volume, primary corridors and ISO 20022 migration status) and estimates annual nostro float drag as monthly volume × 12 × 4.5%. It scores five dimensions:

ISO 20022 alignment

Migration status is the main driver of Phase 1 timeline; institutions already in progress can shorten Phase 1 by 2–3 weeks. The diagnostic scores not started at 15%, in assessment 35%, in progress 65% and completed 90%.

Liquidity model fit

Corridor volume sets potential tMMF yield recovery; higher monthly volume strengthens the case for redesigning the liquidity model.

Regulatory posture

Tokenized deposits operate within your existing banking license. Phase 1 mapping surfaces jurisdiction-specific issues before architecture starts.

Technical capacity

Core integration paths vary by vendor; the architecture phase identifies options that need no core changes where available.

Corridor economics

Corridor FX spread, settlement lag and correspondent dependency set the net benefit of an A2A deployment.

A time-boxed, reversible path

Each phase ends with a Go/No-Go gate, keeps budget approvals within ALCO norms and delivers standalone value. Nothing requires a multi-year commitment upfront.

Phase 1 is the only required commitment, and most ALCO committees can authorize it without board sign-off. Each later phase is approved independently.

Tokenized deposits and third-party stablecoins

For compliance teams and board risk committees: the liability structure, capital treatment and regulatory perimeter of tokenized deposits differ fundamentally from third-party stablecoins. See the regulatory FAQ for more.

Tokenized deposits stay inside the regulatory perimeter your board already understands and the deposit franchise you already run; the tokenization layer sits within existing infrastructure.

What happens when you reach out

There is no RFP process and no six-week discovery phase. Phase 1 starts with a 30-minute treasury review confirming corridor fit, jurisdiction coverage and ISO readiness; the memo and risk register follow within 4–6 weeks, and starting Phase 1 needs no budget commitment. Before Phase 2 you can compare DLT platforms, corridor economics and settlement topology in the architecture matrix, which covers Corda, DAML, Hyperledger Fabric and hybrid approaches across jurisdiction classes. Platforms we work across: R3 Corda, Digital Asset DAML and Hyperledger Fabric.

We take on a limited number of institutions at a time. For a live corridor problem, a direct conversation is fastest.