Solutions · Payment platforms & PSPs
Add Latin America to your platform without building it
PSPs, orchestrators, banks and wallets plug into Localpayment’s local rails for pay-ins, virtual accounts, payouts and FX through one API, and offer them to their own customers.
- Local rails in 14 countries
- Virtual accounts per sub-merchant
- Funding by wire, USDC or USDT
Local rails in 14 countries- Payout countries
- 14
- Pay-in countries
- 9
- Virtual Account markets
- 7
- API for every market
- 1
Who we work with
Built for the platforms behind the payments
PSPs & gateways
Offer local methods such as Pix, SPEI, PSE and Bre-B to your merchants without opening an entity in each market.
Orchestrators
Add Localpayment as a connection for Latin American rails and route to it alongside your other providers.
Banks & neobanks
Extend collections and payouts to your corporate clients’ counterparties across Latin America.
Digital wallets
Fund user wallets with local transfers and pay out to bank accounts across the region.
Cross-border B2B platforms
Collect from buyers and pay suppliers locally, with FX into hard currency.
Money-transfer operators
Deliver funds into bank accounts and wallets over local rails in the destination country.
Integration options
Connect the way your platform already works
Most partners integrate once with our REST API and reuse that integration in every market. Orchestrators add us as a connection next to their other providers. If your platform runs its own provider specification, our partnerships team assesses case by case whether the integration can be adapted to it.
- Direct REST API: one integration for pay-ins, virtual accounts, payouts and FX
- Inside your orchestration layer, as your connection for Latin American rails
- Your own provider specification: assessed case by case
- Stage testing first, then go live market by market
What you can offer
Everything your customers need from Latin America
Pay-ins
Cards in Argentina, Colombia, Mexico and Peru; Pix, SPEI, PSE, Bre-B, QR and more through one Create Payin endpoint.
Pay-ins —Virtual accounts at scale
Accounts per customer, per transaction, per sub-merchant or omnibus, created one by one or in batches.
Virtual accounts at scale —Payouts
Bank transfers in 14 countries and wallet payouts in 9, with approvals, alias verification and proof of payment.
Payouts —FX & treasury
Convert local currency into USD, EUR, GBP, CAD, AUD, NZD, CHF, USDC or USDT, with a locked rate.
FX & treasury —Stablecoin rails
Fund your account with USDC or USDT on Ethereum or Tron and withdraw to allow-listed wallets.
Stablecoin rails —Reporting & reconciliation
Balance, activity and reconciliation APIs per account, plus reports in the Business Portal.
Reporting & reconciliation —
Onboarding
From first call to live markets
- 01
Onboarding
A commercial agreement and a due-diligence review sized to your business model.
- 02
Stage credentials
Receive Stage credentials at the start of the partnership.
- 03
Test
Test every flow in Stage with no real money. Production access follows a security review and business verification.
- 04
Go live
Launch your first market in weeks and add new ones by configuration, without reintegrating.
For engineers
Signed webhooks for every event.
Every event reaches your endpoint as a webhook signed with HMAC-SHA256. Verify the signature over the raw request body before you trust it.
- Server-side calls from allow-listed IPs
- Separate Stage and Production credentials
- MCP server and llms.txt for AI-assisted integration
// Verify a Localpayment webhook signature (Node.js). Example.
import crypto from 'node:crypto';
// x-signature header: "HMAC-SHA256 <hex>", computed over the raw request body
export function isValidSignature(rawBody, signatureHeader, secret) {
const received = String(signatureHeader ?? '').replace(/^HMAC-SHA256\s+/i, '');
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const a = Buffer.from(received, 'hex');
const b = Buffer.from(expected, 'hex');
return a.length === b.length && crypto.timingSafeEqual(a, b);
}
// Reply 200 fast, process asynchronously and deduplicate on externalId / internalId.The challenge in Latin America
What slows a platform down in Latin America, and how we remove it
What gets in the way
- A license per countryCollecting and paying out locally needs a licensed, registered or supervised entity in each market, plus its reporting and AML obligations. Building that footprint takes years.
- Fourteen rail integrationsPix, SPEI, PSE, Bre-B, COELSA, TEF, CCE: each rail has its own messages, identifiers, limits and cut-off times. Fourteen countries means fourteen integrations to build and keep current.
- Sub-merchant funds flowsA platform needs to know which merchant each deposit belongs to, hold funds separately and pay out the right amount, in a model its regulator and ours accept.
- Operations at volumeThousands of status changes an hour, payouts that must be approved and reconciled, and merchants asking where their money is.
How Localpayment addresses it
- Our footprint, your productLocalpayment has a licensed, registered or supervised presence in 18 countries. You contract one partner and offer the markets you need.
- One API for every railPOST /api/payin/ and POST /api/payout/ cover local rails in 14 countries. New markets are enabled by configuration, with no reintegration.
- Virtual accounts per sub-merchantAssign virtual accounts per sub-merchant, per customer, per transaction or as omnibus accounts, created one by one or in batch, subject to our compliance review of your model.
- Signed webhooks and reconciliation by APIEvery status change arrives as an HMAC-SHA256-signed webhook carrying your external ID. Payouts run in batches with double signature; balances and activity are available by API and in the Business Portal.
Recommended method mix
What to offer your merchants, country by country
Instant transfers and virtual accounts everywhere; cards where we acquire them; real-time rails for sub-merchant payouts.
Brazil
- Pay-in methods
- Pix (QR and Copia e Cola) · Pix-key virtual account per sub-merchant
- Payout rails
- Pix 24/7 · TED
Mexico
- Pay-in methods
- CLABE virtual account (SPEI) · Cards with 3D Secure, installments and subscriptions · SPID USD account
- Payout rails
- SPEI 24/7 · Bill payments
Colombia
- Pay-in methods
- PSE · Bre-B · Bre-B-key virtual account · Cards with installments and subscriptions
- Payout rails
- Bre-B key 24/7 · TransfiYa · ACH
Argentina
- Pay-in methods
- CVU virtual account · Debin · QR · Cards (Visa, Mastercard, Amex, Naranja, Cabal)
- Payout rails
- COELSA transfers 24/7 · Bank transfers above the COELSA limit
Chile
- Pay-in methods
- TEF virtual account · ETPAY
- Payout rails
- TEF 24/7 up to CLP 7,000,000 · same-day above
Peru
- Pay-in methods
- CCI virtual account (PEN and USD) · QR · Cards with 3D Secure, installments and subscriptions
- Payout rails
- CCE real-time up to PEN 30,000 · LBTR above · Wallets
Only methods documented in our API are listed. Limits, speeds and cut-off times per method are on each country page.
Money flow
From a merchant’s customer to the merchant’s bank account
How a PSP or platform collects, attributes, converts and pays out through Localpayment, with your own identifiers end to end.
- 1
Your platformLocalpayment:
Create the charge or account
POST /api/payin/ with your external ID, or a virtual account per sub-merchant (single or batch) so transfers are attributed automatically.
- 2
PayerLocalpayment:
Pays locally
Pix, SPEI, PSE, Bre-B, a transfer to the virtual account, or a local card where we acquire. Real-time rails confirm in seconds, 24/7.
- 3
LocalpaymentYour platform:
Signed webhook
Each status change is signed with HMAC-SHA256 and carries your external ID. Reply 200, process asynchronously, deduplicate.
- 4
LocalpaymentLocalpayment:
Balance per sub-merchant
Funds sit in the account structure agreed for your model: per sub-merchant, per customer or omnibus, visible by API.
- 5
LocalpaymentLocalpayment:
FX when needed
Convert within local market hours; lock the rate with a quote token. Hard currencies include USD, EUR, USDC and USDT.
- 6
Your platformLocalpayment:
Order the payout
POST /api/payout/ per merchant or in batches. Double signature protects every approval.
- 7
LocalpaymentYour merchant:
Merchant is paid
By local rail in local currency: Pix, SPEI, Bre-B, COELSA, TEF or CCE. You receive the final status by webhook.
The account structure for sub-merchants is defined during the compliance review of your model. Conversion happens within local market hours; the rate is locked with a quote token.
Market figures
The volume your merchants expect you to handle
Public figures from official and industry sources. Each one links to its source.
78.4 bn
payment operations in Brazil in the second half of 2025, across all instruments
73.5M
people in Mexico made at least one SPEI transfer in a quarter
Source: Banco de México, Informe anual sobre las infraestructuras de los mercados financieros 2024
6.2 bn
operations by credit institutions and SEDPE in Colombia in one quarter
Source: Superintendencia Financiera de Colombia, Informe de operaciones, Q4 2025
Industry FAQ
Do we have to build to your API?
Most partners integrate once with our REST API and reuse it across markets. If your platform already runs its own provider specification, tell our partnerships team: whether the integration can be adapted to it is assessed case by case.
Can Localpayment sit behind our orchestrator?
Yes. You can connect Localpayment as the provider for Latin American rails inside your existing routing, or work with us directly.
Can we offer virtual accounts to our own merchants?
Yes. Virtual accounts can be assigned per sub-merchant, per customer, per transaction or as omnibus accounts, subject to our compliance review of your model.
Which countries can we offer?
Localpayment has licensed, registered or supervised presence in 18 countries, with local rails in 14. The coverage page lists the methods country by country.
How do we pay out to our merchants?
With POST /api/payout/, one by one or in batches, on real-time rails such as Pix, SPEI, Bre-B, COELSA, TEF and CCE. Double signature is required to approve payouts, and the final status arrives as a signed webhook.
How does FX work for our balances?
You hold local-currency balances and convert within local market hours into USD, EUR, GBP, CAD, AUD, NZD, CHF, USDC or USDT. A quote token locks the rate for the amount you are converting.
How do we fund payouts and withdraw funds?
Fund your account by wire or with USDC or USDT on Ethereum or Tron. Withdrawals go only to your own bank accounts or to allow-listed wallets.
What does onboarding involve?
A commercial agreement and a compliance review sized to your model, Stage testing, then a security review and business verification before production access. New markets are then enabled by configuration.
Keep exploring
Partners
How we work with platforms, resellers and technology partners.
Partners —Virtual accounts
Accounts per sub-merchant, customer or transaction, created singly or in batch.
Virtual accounts —Developers
Quickstart, sandbox, webhooks and AI tools for your integration.
Developers —Coverage
18 countries with a licensed, registered or supervised presence.
Coverage —Payment methods by country
Every documented method with limits and speeds.
Payment methods by country —Checkout experiences
What the payer sees, method by method, country by country.
Checkout experiences —
Add Latin America to your network
Tell us about your platform, your merchants and the markets you want to open. We will show you how our rails fit.