Stablecoin settlement for the US–Mexico corridor

Replace correspondent banking with one API call.

8os settles cross-border B2B payments on stablecoin rails. USDC in, MXN out — or the other way. Institutional FX, CFDI 4.0 built in, in a single flow. No SWIFT. No two-day wait. No lifting your treasury team off the floor on a Friday afternoon waiting for an MT103 to clear.

See the math on your volume
Settled · 23.4s
FX locked at execution
From · United States
Acme Co.
$50,000.00
USD · ACH
17.046
MXN/USD
To · Mexico
Proveedor SA de CV
$852,300.00
MXN · SPEI
Settled
00:23.4
CFDI 4.0
ABC-2026-X8Z
Webhook
200 OK

Illustrative example of the flow.

Rails

Juniper Research projects Mexico will be the #4 market in the world for B2B stablecoin payments by 2035, at $346 billion in volume — behind only the United States, Brazil, and Japan. The corridor we're building isn't a distant bet. It's where the market is already moving.

Source: Juniper Research, 2026.

The Math

The numbers, without polite rounding.

Moving a payment between the US and Mexico over correspondent banking costs far more than shows up on any invoice. The World Bank estimates cross-border B2B payments take 3 to 5 days and cost an average of 6.3% of the transaction value — across FX markup, correspondent fees, and compliance charges. Traditional bank FX spreads run 2.5% to 5%, and the all-in corridor cost typically lands between 3% and 7%.

Sources: World Bank (2025); US–MX corridor industry benchmarks.

Correspondent banking
On $50,000 USD payment
2.5–5%
  • FX spread (2.5–5%)$1,375
  • Origin wire fee$35
  • Intermediary deductions$22
Total bleed$1,290–$1,575
On 8os
Single synchronous flow
  • FX spreadinstitutional
  • Settlement feebps only
  • Intermediary deductions$0
You keep~$1,290+
On a $50,000 USD payment to a supplier in Mexico, today:
Sources: World Bank (2025); US–MX corridor industry benchmarks.
Correspondent bankingToday
  • FX spread2.5%–5% over interbank
  • Origin wire fee$15–$50
  • Intermediary deductions$15–$30 (surfaced weeks later)
  • Time to settlement3–5 business days
  • CFDI 4.0 emissionNot included
  • TraceabilityManual reconciliation
  • All-in corridor cost3%–7% of transaction value
8os8os
  • FX spreadInstitutional rate, locked at execution
  • Origin wire feeIncluded in per-settlement bps
  • Intermediary deductions$0
  • Time to settlementSingle flow, no T+2
  • CFDI 4.0 emissionAutomatic
  • TraceabilityReal-time webhook + dashboard
  • All-in corridor costPer-settlement bps, locked at execution
What your bank keeps, calibrated honestly:

even at the conservative end of the range, $1M/month in cross-border payments is $120,000 to $360,000 a year your correspondent keeps without it appearing on any invoice.

At $10M/month, that's $1.2M to $3.6M a year. At that range it's no longer operational friction — it's headcount.

Calculator

Run your real volume.

Spread applied
$1M
$100K$50M
What your bank keeps / month
$0
Per year
$0

Estimate based on US–MX correspondent banking spread benchmarks. Calibrate against your real rate by comparing it to the interbank mid-market rate.

01 · The 8os path

The same $50,000 payment, through 8os.

Steps
5
Settlement
Single flow
CFDI
Built in

Five things change: the cost, the latency, the compliance posture, the reconciliation, and the visibility.

Funds received
t = 0s
FX locked
t ≈ 2s
MXN settled
t ≈ 15s
CFDI issued
t ≈ 22s
Webhook fired
t < 30s
  • FX locked at executionCompetitive institutional rate. No hidden spread.
  • Transparent fee structureEvery basis point visible on every settlement.
  • Single synchronous flowSPEI settlement, on-chain provenance, reconciled to the cent.
  • CFDI 4.0 issued automaticallyYour counterparty gets a compliant invoice — no manual step.
  • Real-time dashboard and webhooksEvery payment, every status, queryable on demand.
The flow

The flow, end to end.

Five steps, one synchronous flow. Click any step to inspect what runs underneath.

Step 01 / 05t = 0s

Funds received

Funds arrive at your 8os wallet via ACH, USDC transfer, or virtual CLABE. A webhook fires the moment the deposit confirms — your treasury system knows before the funds settle.

Mercury · ColumnUSDC on EthereumSTP virtual CLABE
Security & architecture

Institutional posture, by design.

Security and regulatory controls matched to the industry we serve — built in, not retrofitted.

L1 · VISIBILITYL2 · EXECUTIONFireblocksBitGoSTPBitsoChainalysisL3 · RAILS & CUSTODYReal-timeintelligenceExecutionlayerRails &custodyARCHITECTURE · 3 LAYERS

Institutional custody

USDC in MPC/HSM-backed custody. Multi-sig for hot operations. No commingled funds.

Real-time screening

Sanctions, AML, and travel-rule compliance on every transaction.

Onboarding

KYB under U.S. BSA and Mexican Ley Fintech standards. PLD/FT program.

Banking

U.S. operating in USD. Mexican concentradora via a SPEI participant.

Certifications targeted for 2026
SOC 2 Type II · ISO 27001
Built for treasury teams

Controls your CFO already wrote down.

Funding, approvals, and integrations that match the governance you already run — without rewriting it.

Illustrative examples.

Funding sources
3 sources
  • Mercury USD operating
    ACH · Wire
    $420,500.00
    USD
  • USDC treasury wallet
    0x71C…f93b
    $1,205,000.00
    USDC
  • MXN concentradora
    CLABE 646 180 …4521
    $8,540,200.00
    MXN

Multiple funding sources

Wire from your U.S. operating account, send USDC from your treasury, or fund in MXN through a virtual CLABE assigned to your organization. We handle the rail abstraction.

Pending approval
Above $100K limit
Payment to
Proveedor SA de CV
$250,000
USD → MXN
Required signers · 2 of 2
MR
Maria Rivera
approved
JC
José Castro
pending
Policy: dual approval over $100K · cryptographically logged

Approvals that match your governance

Per-user spending limits, dual-approval thresholds above set amounts, and counterparty allowlists. Your CFO controls every dollar before it moves.

Integrations
/v1/integrations
SA
SAP
Designed
NS
NetSuite
Designed
QB
QuickBooks
Designed
M
Mercury
Designed
C
Column
Designed
RE
REST API
Designed

Designed to integrate

Self-serve dashboard, CSV bulk for payroll or supplier runs, REST API and webhooks, and ERP connectors (SAP, NetSuite) — designed to integrate with the systems you already run.

What's next

Built for treasury today. Ready for agents tomorrow.

8os was designed API-first from the first commit. The same infrastructure your treasury team uses today to authorize a payment manually can tomorrow orchestrate payments initiated by autonomous systems — with the same limits, the same approval rules, the same audit trails.

We start with treasury; agents are the next floor of the same building.

Identity hierarchy · Policy engine · Per-agent audit trail · Real-time spend controls
The full thesis on the agent economy lives here
L0L1L2ORGOrganizationUSERCFOUSERTreasuryUSEREngineerCollectionsReportsReconcilePayrollSuppliersWebhook
Built for the U.S.–Mexico corridor

Designed for the flow you're already running.

Four buyer profiles, one set of rails. U.S.–Mexico goods trade hit $872.8 billion in 2025; these are the ones who feel the friction of moving it most:

Source: U.S. Census / USTR, 2025. Total goods trade — corridor size, not addressable volume.

US · Origin
Ready
From
Acme Co. Treasury
$50,000.00 USD
Method
ACH wire
Bank
Mercury
↓ USD → MXN↑ MXN → USD
FX locked<30sCFDI 4.0Audit-ready
MX · Destination
Settled
To
Proveedor SA de CV
$852,300.00 MXN
Rail
SPEI · STP
CLABE
…0 4521
Cash flow · USD ↔ MXNUSMXUSD ↓MXN ↑

Software houses

01

Billing U.S. clients in dollars and paying Mexican engineers in pesos — without trapping cash in the float.

USMX
Suppliers paid · per weekmissedavg

Manufacturing & nearshoring

02

Paying suppliers across the corridor with CFDI compliance built in.

USMX
USD income → MXN · monthly→ MXN

Mexican exporters

03

Receiving USD from U.S. customers — settled directly to MXN, or held in USDC for treasury optionality.

USMX
Reserve allocationUSDCtreasury28%→ MXN72% USDCheld

USDC-native treasuries

04

Companies running USDC operations that need a regulated, auditable MXN off-ramp.

USMX
How we work

What working with us looks like.

We're early, and we're working with a small group of design partners — companies already operating in the corridor who want to build this with us from the first real flow.

  1. 01
    Book a call and tell us your cross-border flow.
  2. 02
    We model your current cost on your real volume.
  3. 03
    We design the first flow and the controls your treasury needs, together.
  4. 04
    We run it with you, documented end to end.
Pricing

No setup fees. No monthly minimums.

Volume tier curve
per settlement · compresses with volume
RATEVOLUME →$500K$1M$5M$10M+rate compresses ↘ as volume scales

You pay per settlement, on volume tiers that compress as you scale.

Transparent FX, locked at execution. Every basis point visible on every transaction.

Pricing modeled on your real monthly volume — book a call and we'll send a quote.

Stop overpaying on every cross-border invoice.

Book a 20-minute call. We'll model your current cost against 8os on your real payment volume, walk you through the architecture, and answer every regulatory question your auditor will ask. No commitment.

hi@8osapi.com

Building something that needs to pay across borders, on stablecoins, without humans in the loop? Read the thesis 8osapi.com