​MXNB is a Mexican peso stablecoin issued by Bitso's regulated affiliate, designed to move pesos onchain for B2B payouts, FX, and SPEI settlement. For cross-border operators, MXNB matters because it collapses the USDC-to-MXN leg into a single onchain hop, replacing OTC desks and shaving the FX spread that typically eats 50 to 150 bps on Mexico payouts.
​

MXNB is a peso-denominated stablecoin issued by Juno, Bitso's Mexico-regulated affiliate, with 1:1 backing in MXN held at Mexican financial institutions through Juno's regulated structure; operators should request Juno's current custodian list before treasury commitment. It is CNBV-supervised under the framework Bitso operates inside, and as of June 2026 it is live on Arbitrum, Ethereum, Avalanche, and the XRP Ledger (XRPL added 11 June 2026 via Bitso's expanded Ripple partnership). The asset is meant to be the onchain representation of a peso that can be redeemed back into SPEI rails through Bitso's licensed Mexico entity.
​

For US or EU treasury teams paying contractors, suppliers, or marketplace sellers in Mexico, MXNB is not a speculative position. It is a settlement primitive. You hold it for minutes or hours between receiving USDC and pushing pesos out via SPEI, not as a balance-sheet asset.
​

The traditional path for a US company paying a Mexican vendor is a correspondent-bank USD wire that lands in a Mexican bank, gets converted to MXN at the receiving bank's posted rate, and clears through SPEI. The pain points are well known: two-to-four day settlement, opaque FX markups, wire fees on both ends, and weekend or holiday gaps.
​

The first generation of stablecoin payouts replaced the wire leg with USDC or USDT, then handed the dollar stablecoin to an OTC desk in Mexico for conversion to MXN. That cut the timing problem but kept the FX spread problem: the OTC desk still quotes the rate, and the receiver still depends on a bilateral relationship.
​

MXNB is the second generation. Instead of converting offchain, the conversion happens onchain through Bitso's market-making and treasury infrastructure, and the resulting peso is itself a transferable token. The operator can hold it, route it, or push it into SPEI when the receiver is ready.
​

Picture a US fintech paying 200 Mexican contractors twice a month. The pre-MXNB flow looks like this:

With MXNB inserted, the flow becomes:

The headline change is that step 3 happens onchain against a visible book rather than as a private OTC quote. For a treasurer, that translates into a referenceable execution price and a verifiable settlement trail.
​

The economics depend on three variables: the chain you send USDC on, the spread to MXNB at the time of execution, and the SPEI cutoff window.
​

On chain selection, Base, Solana, and Arbitrum tend to offer the lowest USDC transfer cost. For routing into MXNB specifically, Arbitrum has been the primary MXNB venue since launch and remains a meaningful book; depth across XRPL and Avalanche is building, and operators should confirm the deepest book at the time of execution, so a USDC-on-Base position needs a cross-chain hop. Eco orchestrates that hop using established rails so the operator does not have to hand-roll a bridge or warm a relayer.
​

On the spread, the USDC/MXNB market quote will not be identical to the official MXN/USD reference rate. The spread to the official MXN/USD reference rate is typically in the tens of basis points for institutional-size tickets during liquid hours, widening outside SPEI hours and at larger sizes; quotes should be sized at execution. For tickets in the tens of thousands, the spread is generally tighter than what an OTC desk quotes for the same notional, because the venue is competitive and the operator can split execution.
​

On SPEI, the network operates 24/7 for retail mobile and banking app access per Banxico's published service description; institutional same-day processing windows depend on the participating bank's internal cutoffs rather than the SPEI network itself. The MXNB-to-SPEI hop is fast once submitted, but the overall window for end-to-end same-day settlement is constrained by the participating bank's cutoffs, not by the onchain leg.
​

Compared to USDT-to-MXN via OTC, the MXNB path tends to win on transparency and reconciliation. USDT via OTC can still win on raw cost in specific corridors and sizes, particularly when an operator already has a deep OTC line, but it does not produce an onchain audit trail of the FX execution.
​

MXNB is backed 1:1 by MXN held at Mexican financial institutions through Juno's regulated structure; operators should pull Juno's most recent published reserve attestation directly to confirm the attestor and cadence in force at the time of treasury commitment. The asset's redemption path runs through a CNBV-supervised entity, which is a meaningful difference from offshore-issued dollar stablecoins, because the regulatory venue and the redemption venue are the same.
​

For institutional users, the operative questions are: what is the attestation cadence, who is the auditor, what are the named custodian banks, and what is the documented redemption SLA? These should be verified directly from Bitso or Juno disclosures at the time of integration rather than taken from a general explainer.
​

We do not render a safety verdict on third-party assets. The factual mechanics: peso-collateralized, regulated issuer, multi-chain availability, integrated with the issuer's licensed off-ramp.
​

MXNB is not useful when the receiver wants USD. If a Mexican supplier invoices in USD and prefers to hold USD, routing through a peso stablecoin only introduces an extra hop. The USDC-direct path or a USD account at a Mexican bank is cleaner.
​

It is also not useful for tax or regulatory arbitrage. The Mexican peso received via MXNB is treated as a peso for SAT purposes; the onchain step does not change the obligation. See the companion article on Mexico's 2026 stablecoin remittance withholding for the B2B implications.
​

Finally, MXNB book depth is concentrated at Bitso. For seven-figure tickets the operator should pre-negotiate execution with Bitso rather than assume the public book can absorb the size without slippage.
​

Mexico is one of the two highest-volume B2B stablecoin corridors in LATAM, alongside Brazil. The corridor has matured faster than most because SPEI is fast and Bitso is licensed, which means the offchain rails are not the bottleneck. The bottleneck has been the FX leg, and MXNB is the most direct attempt to put that leg onchain at institutional scale.
​

For a treasurer designing a 2026 LATAM payout stack, the practical question is not whether MXNB belongs in the architecture. It is which chain to route on, what spread to accept, and how to wire the reconciliation. Those are integration questions, not strategy questions.
​

For a fuller view of the Mexico path including the 2026 withholding proposal and the SPEI provider matrix, see support/en/articles/15575503. For the broader LATAM corridor benchmark, see support/en/articles/15575499. For the underlying USDC vs USDT decision that sits above the peso layer, see support/en/articles/15575500.
​