Why CoDi Failed and Pix Didn't: Lessons for New Rail Launches

Pix launched in November 2020. By November 2021 — twelve months later — 112 million Brazilians were actively using it. That is 52% of the entire Brazilian population registered on a payment system in one year. By late 2025, Pix approaches 8 billion transactions monthly — more than 3x credit and debit cards combined in Brazil (Banco Central do Brasil, November 2025).

CoDi launched in September 2019, one year before Pix. By 2024 — five years after launch — approximately 4 million Mexicans had registered for it. That is under 3% of Mexico's adult population. Monthly CoDi transaction volumes remain below 0.5% of SPEI volumes.

These two systems are commonly described as comparable: both central-bank-operated, both QR-based, both real-time, both mandated. The outcomes are so different that the comparison forces a question every payment operator and regulator should be asking: what actually determines whether a government-mandated real-time payment rail succeeds or fails?

The Pix Structural Advantages

The performance gap has four root causes, all of which were design decisions, not accidents.

Zero fees for everyone — including merchants. This is the single most important difference. Pix is free for consumers and free for merchants. The Banco Central do Brasil (BCB) mandated zero fees from the beginning and has maintained that mandate. CoDi, by contrast, was structured in a way that allowed banks to charge transaction fees to merchants. Some Mexican banks priced CoDi acceptance at 0.5-1% MDR — not zero, but comparable to debit card rates. That eliminated the killer advantage over cards. A merchant with no cost incentive to prefer CoDi over debit has no reason to prominently offer it, train staff on it, or market it.

The alias system — Chaves Pix. To send a Pix payment, you need the recipient's Pix key: their CPF (tax ID), CNPJ (business tax ID), email address, phone number, or a random alphanumeric key they generate. You don't need a bank name, branch number, or account number. The friction of a bank-to-bank transfer — "what's your ISPB code?" — is eliminated entirely. CoDi requires the recipient to share a QR code for merchant payments or a CLABE (18-digit account number) for P2P transfers. The CLABE requirement for P2P killed casual usage — people don't share 18-digit numbers informally.

BCB's bank enforcement mechanism. BCB mandated participation from every financial institution with 500,000 or more active customers, required compliance by a specific date, and enforced it. More importantly, BCB mandated specific UX standards — the Pix flow within a bank's app had to meet accessibility and usability requirements. If a bank's Pix implementation was slow or cumbersome, BCB intervened. BANXICO's mandate to Mexican banks was weaker: participation was required, but UX quality was not specified. The result was wildly inconsistent CoDi implementations across Mexican banks — some functional, some hidden in menus, some so poorly implemented they were effectively unusable.

P2P first, merchant payments second. BCB deliberately sequenced Pix's rollout: consumer-to-consumer transfers came first, merchant payments came second. This created a network that consumers adopted for personal use before merchants ever needed to integrate it. By the time Pix merchant QR codes appeared, consumers already knew how Pix worked because they'd used it to split bills and send money. CoDi launched with a merchant QR payment focus. The P2P use case — the one that creates organic, social adoption — was secondary. Without the social word-of-mouth of "here's how to send me money," consumer awareness remained low.

What CoDi Got Wrong

The individual failures compound each other, but the fee structure is the origin failure. Every other decision — QR code design, bank UX, consumer awareness campaigns — becomes much less important when the merchant has no economic incentive to accept the payment method.

CoDi also suffered from device compatibility issues that Pix did not. A significant portion of CoDi's early QR code implementations required specific app versions that were incompatible with Android devices running older OS versions — common in Mexico's market where device refresh cycles are longer. Pix was designed for lower-spec devices from the outset, reflecting BCB's awareness of Brazil's device distribution.

The consumer awareness problem was real but downstream of the fee problem. You can run consumer education campaigns, but if merchants don't have terminal QR codes displayed and staff don't know how to accept the payment, consumer awareness doesn't convert to transactions.

The Numbers in Detail

At the three-year mark post-launch:

• Pix (three years, February 2024): 155M registered users, 3.5B+ monthly transactions, average value per transaction approximately BRL 350 (~$70), used for P2P, merchant payments, government disbursements, payroll
• CoDi (three years, September 2022): approximately 3M registered users, transaction volumes not publicly disclosed by BANXICO but estimated by Banco de México research partners at under 10M monthly transactions

At the five-year mark:

• Pix (five years, November 2025): 170M+ registered users, approaching 8 billion monthly transactions, outpacing cards by volume by more than 3x (Banco Central do Brasil/EBANX, November 2025)
• CoDi (five years, September 2024): approximately 21.8 million validated accounts but only 17.8 million cumulative transactions — monthly active usage negligible, effectively replaced as Mexico's priority QR payment initiative by DiMo

DiMo — Dinero Móvil — launched in 2022 as a Pix-inspired alias layer for SPEI, allowing transfers by phone number rather than CLABE. DiMo is growing but has not achieved Pix-scale adoption. The alias problem is being addressed; the fee problem has not been fully resolved.

Lessons for New Rail Launches

The Pix/CoDi delta provides a framework for evaluating any new rail launch. Four questions determine whether a mandated real-time payment system will achieve mass adoption:

1. Are merchant fees zero or near-zero? This is the prerequisite. A new rail competing against cards with comparable MDR has no inherent adoption advantage for merchants. The only reason to actively promote an alternative payment method is if it's cheaper. CoDi had comparable fees to debit; Pix had zero fees. This determined merchant behavior more than any other factor.

2. Is there a human-readable alias system? Bank account numbers are a barrier. A payment system that requires sharing a 15-18 digit number for P2P transfers will not achieve casual social adoption. Pix keys (phone number or email) are shareable in the same contexts as a phone number. The alias system is the UX prerequisite for P2P adoption, which is the adoption vector for merchant payments.

3. What are the bank enforcement mechanisms? Mandating participation is not enough. Banks have structural incentives to under-implement competing payment rails that cannibalize card MDR revenue. The regulator must mandate participation quality, not just participation, and must have the authority and will to enforce it. BCB did this; BANXICO did not.

4. Is P2P the first use case? Consumer-to-consumer transfers create organic adoption through social transmission. Merchant QR codes require merchant integration effort before consumers can use them. The sequencing matters enormously.

Mexico Is Now Running the Third Question as an Experiment

The third question above — does the regulator mandate participation quality, not just participation — stopped being hypothetical in Mexico this year.

On 17 June 2026, Banco de México published two circulars in the Diario Oficial de la Federación, both signed on 8 June. Circular 10/2026 amends Circular 3/2012, which governs the operations of credit institutions, regulated SOFOMes with capital links to banks, and the Financiera Nacional de Desarrollo Agropecuario, Rural, Forestal y Pesquero. Circular 9/2026 makes the parallel amendments to the SPEI Rules in Circular 14/2017, reaching SPEI participants and, through their contracts, the indirect participants they serve. Together they introduce a defined term — the Guías — and bind mobile transfer instructions to it.

The Guías para la homologación de la experiencia de usuario en transferencias electrónicas de fondos a través de dispositivos móviles run to 52 pages and rest on three stated principles: usabilidad, comunicación y estandarización. They set minimum requirements stage by stage through a transfer — the first stage, inicio; the second, ingreso de información; and onward — and they cover four mobile flows explicitly: a transfer using account details, a transfer using only a phone number (Dimo, the spelling the Guías use), a transfer by reading or loading a QR code (CoDi), and a push notification requesting payment (CoDi). They apply where a natural person is offered transfers from a deposit or electronic-money account. Transfers between a customer's own products inside one institution are out of scope.

The compliance date is fixed and close: Circular 10/2026's TRANSITORIO SEGUNDO gives institutions until 14 December 2026 to comply with the Circular and the Guías.

What this is, in the terms this article has been using. It is Banxico mandating participation quality at the layer where CoDi's implementations were weakest — the bank's own app — seven years after CoDi launched and four years after Dimo. That is this article's third question being answered in one market, on rails that already exist, and it is the first opportunity to watch the answer rather than argue it.

What it is not. It is not a change to merchant economics, and on this article's own analysis that is the origin failure rather than a downstream one. Nothing in either circular touches merchant fees, acceptance costs, or the incentive a merchant has to display a QR code. A standardised transfer screen makes the good experience harder for a bank to avoid; it does not make a merchant want to be paid this way. The Guías are aimed at the experience; the fee question is left exactly where it was.

The enforcement hook is worth naming, because it is where this differs from guidance. Circular 9/2026 adds a fifth obligation to Rule 71a of the SPEI Rules — comply with the user-experience specifications in the Guías — so after 14 December this is a condition of providing SPEI transfer services, not a recommendation attached to one. Neither circular creates a new supervisory regime or a stated penalty for the Guías specifically; the duty is placed inside rules that already govern participation. How Banxico applies it in practice is not something either document sets out.

And the specification is a living document: under the amended Rule 7a, Banxico publishes and maintains the Guías on its own website with a version number and an effective date, notifies participants of changes in advance, and keeps superseded versions posted. Anyone building to it should build to a version, not to a memory of one.

Evaluating Current New Rail Launches

UAE — Aani (launched Q4 2023): Early adoption appears CBUAE-mandate-driven, primarily through government and utility payments. The MDR structure for merchant acceptance is still being established — this is the critical variable. If Aani replicates Pix's zero-fee model, it has adoption potential. If MDR is set at debit-card levels, it will develop slowly. Phone number alias is supported. Too early for a verdict.

Europe — Wero (EPI project, launched July 2024 in Germany, France, Belgium): Wero launched with a P2P-first strategy — explicitly the right sequencing. P2P between Wero users is zero-cost. Wero reached 43.5 million users in its first twelve months with over 100 million transactions processed (EPI, July 2025). E-commerce merchant acceptance launched in November 2025. The challenge: Wero is not central-bank-mandated, it's a consortium product. Bank adoption is opt-in, not enforced. But the design principles and early adoption trajectory are meaningfully ahead of CoDi.

India — UPI: Already achieved Pix-scale outcomes and then some — 21.6 billion monthly transactions in December 2025 alone, 400 million+ active users (NPCI, December 2025). Its historical zero-MDR merchant mandate was one part of that growth, but the government has since set a selected P2M fee from 15 October 2026. UPI's alias architecture and distribution also differ from Pix; its growth is not proof that every market needs a permanent zero-merchant-fee rule.

The operator lesson is to test the full product: alias usability, bank participation, merchant economics and the route from P2P to merchant acceptance. No single one of these explains adoption alone, and the merchant fee can change after the rail reaches scale.

Operators monitoring new rail launches should watch for merchant fee announcements as the leading indicator of adoption trajectory, before transaction volumes become available.