Payment infrastructure for Latin America.
The rails are local. The API isn’t.
We operate the software layer between merchant systems and each country’s local payment networks — authorisation, settlement, FX and reconciliation.
Same page, same webhook — pick a rail:
Monto a pagar
$2,500.00MXN
CLABE para transferir
000 180 •••• •••• 014
Copiar CLABEEn tu app bancaria, el destinatario aparecerá como VPAGO. Es normal.
¿Cómo pagar?
Copia la CLABE con el botón de arriba.
En tu app bancaria, pega la CLABE, ingresa el monto exacto y realiza la transferencia SPEI.
Vuelve aquí — actualizaremos esta página cuando recibamos tu pago.
Monto a pagar
$350.00MXN
Paga en cualquier tienda OXXO
9302 7411 8856 0412
Copiar referencia¿Cómo pagar?
Ve a cualquier tienda OXXO y di que vas a pagar con OXXO Pay.
Di o muestra la referencia (o el código de barras).
Paga $350.00 MXN en efectivo y guarda tu comprobante.
Monto a pagar
$48.500,00ARS
Escaneá el QR con tu app o billetera
El QR no se copia como texto — escaneálo
El QR no lleva el monto: ingresá $48.500,00 en tu app antes de confirmar.
¿Cómo pagar?
Abrí tu app bancaria o billetera y elegí pagar con QR.
Escaneá el código e ingresá el monto exacto.
Volvé acá — actualizaremos esta página cuando recibamos tu pago.
The hosted checkout as it renders today — same page, same webhook; the rail, the wording and the language change by market.
Acceptance
Payment happens where your customer already is.
A payment page we host, carrying the local method for each market. The merchant builds no screen, and the payer never leaves the flow to finish.
The method is chosen locally
Not by a global default — the rail follows the country the payer is in.
Settled off the authorisation
Settlement and reconciliation run off the same record, not a second ledger.
Leaves as a signed webhook
HMAC-SHA256 over the raw body, with a timestamp and constant-time comparison.
Who this is for
Every business takes payment differently.
The rails are the same; what changes is the method mix, the settlement rhythm and what counts as fraud. Find the shape closest to yours.
Money arrives from many people at once.
Each payment gets its own account number, so a transfer lands on the right customer without anyone typing a reference. Short and over payments are states we settle — not errors we reject.
Money outOne payment, several people to pay.
Commissions, splits and co-producers run on their own ledger, with statements per period. A refund reverses the commission it created.
Money acrossCollected here, needed somewhere else.
Settle in the currency you actually need, with the rate locked at authorisation.
Coverage
Where we operate, and with what.
Every market has its own rails. We connect to the methods people actually use in each country — and each line says whether it is running today or being prepared.
| Market | Methods | Currency | Status |
|---|---|---|---|
| Mexico | SPEI · OXXO Pay · Cards | MXN | In operation |
| Brazil | Pix · Boleto · Cards | BRL | In operation |
| Argentina | Transferencias 3.0 (CBU/CVU) · Mercado Pago · Rapipago | ARS | In operation |
| Colombia | PSE · Nequi · Daviplata · Bre-B | COP | In operation |
| Chile | Khipu · Transferencia 24/7 · Webpay | CLP | In operation |
In operation means merchants are transacting on the rail today. In preparation means the connection is built and the market is not open for new volume yet. · All ten markets, methods and settlement currencies →
Capabilities
What the platform does.
Payment software, not financial intermediation. vpago builds and operates the technical layer between merchant systems and the networks.
Take the payment
Initiation and capture by local method, through a hosted checkout or a direct API integration.
Send it back out
Sending to local accounts in each market, with account validation before the order is placed.
Rate locked at authorisation
The rate you are shown is the rate you settle at — not the one on settlement day.
Authorised, settled, credited
Reconciliation between the three, with an auditable trail for every single transaction.
Dashboards that answer
History per transaction and per account, for the operations and support teams.
All of it, once
The same resources, envelopes and webhook signatures in every market on the coverage list.
For developers
One API, every market.
# Create a payment intent curl -X POST https://api.vpago.io/v1/payment_intents \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "amount": 250000, "currency": "mxn", "payment_method": "spei", "metadata": { "order_id": "ORD-4471" } }'
Amounts in the currency’s minor units. Illustrative example — the full reference lives in the documentation.
Security
What we commit to, and where the detail goes.
The commitments below hold today. Formal certifications will be announced when they exist — not before.
What we hold
Who can act
Architecture, controls and evidence go to your security team on request.
Pricing
Quoted case by case.
Charged per transaction, with no monthly fee and no setup cost. The final number depends on volume, the methods used and the profile of the operation — so it comes out of a conversation, not out of a table.
A percentage, or a flat fee
Depending on the local method. Declined attempts are not charged.
A spread over the rate
Locked at authorisation and visible before the payer confirms.
Company
Engineering with mileage.
vpago builds and runs payment infrastructure in Latin America. The platform is in production: transactional systems under load, with settlement, reconciliation and audit running in operation.
The same engine serves other brands of the group in their own markets. What travels between them is the platform; what stays local is the rail.