CoDi vs DiMo: How QR and Mobile Payments Work in Mexico
By Laís Peixoto
Growth Marketer, Proteside
Published · 7 min read

CoDi and DiMo are different ways to initiate transfers in Mexico, integrated into the SPEI ecosystem. With CoDi (Cobro Digital), the merchant presents a payment request by QR code, NFC or message; with DiMo (Dinero Móvil), the payer uses the mobile number linked to the recipient's account.
CoDi and DiMo are different ways to initiate transfers in Mexico, integrated into the SPEI ecosystem. With CoDi (Cobro Digital), the merchant presents a payment request by QR code, NFC or message; with DiMo (Dinero Móvil), the payer uses the mobile phone number linked to the recipient's account. At checkout, the core risk is the alteration of the identifier displayed before the payment is authorized.
What each one is
SPEI (Sistema de Pagos Electrónicos Interbancarios) is Mexico's interbank transfer system. CoDi and DiMo, both created by the Bank of Mexico (Banxico), are two ways to initiate a transfer on it.
CoDi (Cobro Digital). It went live on September 30, 2019. Banxico describes the platform as available 24 hours a day, without the chargeback logic typical of a card payment, since the buyer authorizes the transfer. This does not eliminate the banking and legal procedures that may apply to errors or fraud. The payment request reaches the customer as a QR code (fixed or generated for each sale), by NFC or as a notification on their phone. In the official guide to remote payments, the customer reviews the payee's name, the amount and the payment description (concepto) in the app before authorizing.
DiMo (Dinero Móvil). It is a scheme developed and operated by Banxico itself and made available to SPEI institutions on February 23, 2023. At the end of November 2024, according to a central bank statement, 21 financial institutions were participating and more than 11 million accounts were linked. The account holder links their mobile number to the account in their bank's app, with consent; each number is tied to a single account, and a new link at another bank replaces the previous one. To send money, the customer enters the recipient's number, the amount and the description, and authorizes with a fingerprint or token.
What changes for the payee
Both end up in the store's account, by different routes:
- Who initiates. With CoDi, the store creates the payment request and the customer only accepts it. With DiMo, the customer builds the transfer from scratch.
- Who sets the amount. A CoDi payment request already carries the amount and description. With DiMo, the customer types the amount, which leaves room for error and makes reconciliation harder.
- What identifies the store. With CoDi, the data travels inside the payment request generated by the store's or the bank's system. With DiMo, the identifier is the mobile number the store publishes.
- What the customer sees before confirming. With CoDi, the payee's name, the amount and the description, according to Banxico. With DiMo, it varies by app: Expansión describes the recipient's name on screen; Nu México reported in 2024 that customers can check the payee's initials; Banamex's step-by-step guide shows the linked number and the destination CLABE.
- How to confirm the credit. With CoDi, both sides receive a notification. With DiMo, the official page advises checking it like any SPEI transfer.
CLABE is the standardized 18-digit number that identifies a bank account in Mexico. It does not go away with DiMo: the mobile number is just another way to reach it.
What takes effect in December 2026
Banxico's Circular 10/2026, published in the Official Gazette (Diario Oficial de la Federación) on June 17, 2026, requires institutions with level 2, 3 or 4 accounts to associate, at the account holder's request, the last ten digits of a mobile number with the account for receiving transfers. It also requires banks to accept transfers that identify the beneficiary's account by CLABE, by the 16 digits of the debit card or by the associated mobile number, and to follow Banxico guides that standardize the experience in their apps. The compliance deadline is December 14, 2026. According to DPL News, the guides organize the flow into four stages: initiation, data entry, consistency and integrity, and notification.
The regulatory update may make it easier to use the mobile number as an identifier; the circular alone does not tell us how much that use will grow among stores. If you offer DiMo at checkout, it is worth reviewing now how you display and confirm that number.
Where the scam gets in
- CoDi QR swapped on the page. Malicious code at checkout replaces the QR with another one, generated for a third party's account, with the same amount. The details are in our guide on CoDi QR payment requests and precautions.
- Swapped phone number. If the page or the confirmation email says "pay by DiMo to this number", changing a few digits is enough. The app may show the recipient's name, initials or other data depending on the institution; the buyer needs to compare the information available with the payee stated by the merchant.
- Fake payment request on the phone. One possible reading: since remote CoDi arrives as a notification, a third party can send the customer a payment request under a name similar to the store's. The logic resembles UPI's collect request, which India has restricted, as we explain in UPI intent, QR and collect.
How to check who will receive the money
- Generate one CoDi payment request per order, with a fixed amount and a description that identifies the purchase.
- Publish the exact name that appears in the apps (the account holder) next to the QR or the number, and ask the customer to compare it before authorizing.
- If you accept DiMo, show the number in one place only and state the amount and the reference the customer should type in the description.
- Say when the store sends payment requests. If you only send a CoDi request after the customer chooses that option, make that clear: any other request is not yours.
- Standardize the identification shown to the buyer. If the company receives payments into different accounts, document the legal names of each payee accepted on CoDi and DiMo. Do not assume both services necessarily use the same account.
- Release the order only once the credit is in your account, and treat "I paid but it didn't arrive" as a sign that something may have been swapped.
These precautions apply both to online stores and to payment providers that generate payment requests for many merchants. What can and cannot be checked on the page is described in CoDi payment protection.
Quick checkout comparison
- How it starts: with CoDi, the payee generates the payment request; with DiMo, the payer initiates the transfer.
- Identifier displayed: with CoDi, the QR, the contactless tap or the payment request message; with DiMo, the linked mobile number.
- On-screen risk: with CoDi, a tampered QR or tampered request data; with DiMo, a destination number altered at checkout or in communications.
- Recommended reconciliation: with CoDi, the request reference and the credit confirmation; with DiMo, the transfer identifier and the bank confirmation.
Frequently asked questions
Does DiMo replace CoDi?
No. They are different Banxico schemes: CoDi is a payment request initiated by the seller; DiMo is a transfer initiated by the payer using the recipient's mobile number.
Does the customer see the payee's name with DiMo?
It depends on the app. Some banks show the name, others the initials, others the linked number and the destination CLABE.
Do I need a CLABE to receive DiMo payments?
Your account still has a CLABE; DiMo just links the mobile number to it. Circular 10/2026 keeps CLABE among the accepted identifiers.
Wrapping up
The same QR payment request design appears in other countries in the region, as we show in our article on the interoperable QR of Transferencias 3.0 in Argentina. Proteside checks, in the payer's browser, whether the CoDi QR displayed at checkout is the one the store generated, blocks the swap before the customer accepts it in the app and records the evidence. Checking the payee in the bank app is still necessary.


