Aureo

Pesos and Bitcoin, inside your product.

With the Aureo API, your user pays with Bitcoin over Lightning and the pesos arrive over SPEI at any CLABE in Mexico. We handle compliance, liquidity and SPEI.

  • Private beta
  • REST /v1
  • Sandbox included

Who it is for.

Platforms that already have users holding Bitcoin and need to reach a bank account in Mexico.

  • Wallets and exchanges

    Let your users turn sats into pesos and send them to their own bank, or someone else's, without leaving your app.

  • Payments and remittances

    Collect in Bitcoin over Lightning and settle in pesos over SPEI to whoever needs to get paid in Mexico.

  • Fintechs and companies

    Pay suppliers, contractors or clients in Mexico from your Bitcoin treasury, with proof for every payment.

How a payout works.

Four steps between your user and a bank account in Mexico. Your platform never touches pesos or holds anyone's Bitcoin. The first step is live in the beta; the other three are being built.

  1. Register the recipient

    You send the CLABE and the holder's name. Aureo verifies the account and tells you by webhook when it's approved.

  2. Create the peso order

    You set how many pesos should arrive. The order carries your reference and metadata.

  3. Your user pays over Lightning

    You request a quote and get an invoice with the rate locked for 5 minutes. Your user pays it from any wallet.

  4. Aureo sends the SPEI

    We sell the sats and send the pesos. You get a webhook, and the order shows the tracking key and Banxico's CEP.

What exists today, and what's next.

We're building the API on the same processes that already move pesos and Bitcoin in the Aureo app.

  1. Built, in private beta

    • Live and sandbox API keys, with scopes and instant revocation
    • Indicative BTC→MXN rate for a peso amount
    • Recipients: register a CLABE and Aureo verifies the holder
    • Customers: register the people who pay and Aureo screens them
    • Signed webhooks (HMAC), retried for about 32 hours
    • Dashboard to create keys and register webhooks
    • OpenAPI reference and llms.txt
  2. In progress

    • Peso payout orders to any CLABE
    • Quotes with a Lightning invoice and a rate locked for 5 minutes
    • Every payout's status by webhook; the order includes tracking key and CEP
    • Idempotency-Key on every order, so a retry never pays twice
    • Payment simulator in the sandbox
  3. Later

    • Buy: from pesos over SPEI to Bitcoin
    • On-chain Bitcoin payments, alongside Lightning
    • Activity and reconciliation in the dashboard
    • More partners and open access, with a status page

Built to integrate.

Two members of the Aureo team reviewing the app on a laptop
Versioned REST
Routes under /v1, JSON responses and cursor pagination on every list.
Docs for people and agents
An OpenAPI reference with stable error codes, and an llms.txt your coding assistant can read.
Signed webhooks
Every event is signed with HMAC and retried automatically if your server doesn't answer.
A real sandbox
The same routes and the same webhooks, with outcomes you choose to test every case.
Compliance included
Aureo verifies the receiving accounts and screens the people who pay. Your team never has to decide on identities.

Join the beta, or hear first.

We're adding a few partners to the private beta. Leave your email and what you want to build; we'll write when a spot opens or when we launch.

What are you after?

We only write about the API. You can unsubscribe from any email.

Common questions