Payouts
Get money to the people and businesses you need to pay.
Pay suppliers, sellers, contractors and customers through local bank and wallet rails, and track every payout from request to completion.
- Pix, SPEI, COELSA, TEF
- Real-time, 24/7
- One API
Delivering results for global businesses
- 24/7
- Real-time payout API, every day of the year
- Pix · SPEI
- Instant rails, confirmed in seconds
- Webhook
- Every status, signed, as it happens
- API
- One call per payout, with no manual approval
Why Localpayment
Fewer providers, faster payouts, cleaner books
One partner for local payouts across the region: one balance, one integration and the same statuses in every country.
One integration, local markets
Pay over local rails, in local currency, from one balance. New countries are a configuration, not a reintegration.
One integration, local markets —Bank accounts and wallets
Pay people where they get paid: to their bank account, or to their mobile wallet where they are offered.
Real-time, 24/7
Pix, SPEI, COELSA, TEF, CCE, Bre-B and SINPE Móvil confirm in seconds, 24/7, including weekends.
Less reconciliation
Every status reaches your systems by signed webhook and every completed payout has a proof of payment, so each payout matches your ledger.
Less reconciliation —
Talk to our sales team
Tell us your markets and volumes, and we’ll design the integration with you.
Payout methods
Bank accounts, wallets and billing references
Choose how each beneficiary gets paid. Every method runs on the same API, statuses and webhooks.
Bank transfer
- ar
- bo
- br
- cl
- co
- cr
- do
- sv
- gt
- hn
- mx
- pa
- py
- pe
Pay bank accounts over each country’s clearing systems and instant-payment networks, such as Pix, SPEI, COELSA, TEF, CCE, Bre-B and SINPE, in local currency.
Bank transfer —Wallets
- ar
- bo
- br
- cl
- co
- cr
- sv
- mx
- pe
Direct to wallet with Yape in Bolivia, SINPE Móvil in Costa Rica and CCE wallets in Peru, or by bank transfer to the account behind the wallet in Argentina (CVU), Bolivia (Tigo Money), Brazil, Chile, Colombia, El Salvador and Mexico.
Wallets —Tax, Bill and Service Payments
- mx
Pay a government or service billing reference, such as a SAT payment reference, instead of a bank account, in MXN. Every payment status is notified by webhook.
Tax, Bill and Service Payments —
Use cases
Built for platforms that pay many people
Marketplace seller payouts
Settle seller earnings in local currency, on the schedule you choose.
Marketplace seller payouts —Driver & courier earnings
Pay drivers and couriers daily or instantly on real-time rails.
Driver & courier earnings —Payroll & contractors
Pay employees and freelancers across the region from one balance.
Payroll & contractors —Remittances
Deliver cross-border transfers to bank accounts and wallets.
Remittances —Publishers & affiliates
Pay creators, publishers and affiliates in their own currency.
Publishers & affiliates —Wallet withdrawals
Let users cash out their balance to any local bank account.
Wallet withdrawals —
Coverage
Local payout rails on local rails
Payouts travel over each country’s own clearing systems and instant-payment networks, in local currency.
Argentina
- Currency
- ARS
- Rails
- COELSA
- Speed
- Real-time 24/7
Brazil
- Currency
- BRL
- Rails
- Pix
- Speed
- Real-time 24/7
Chile
- Currency
- CLP
- Rails
- TEF
- Speed
- Real-time 24/7
Colombia
- Currency
- COP
- Rails
- Bre-B · TransfiYa
- Speed
- Real-time 24/7
Costa Rica
- Currency
- CRC
- Rails
- SINPE Móvil
- Speed
- Real-time 24/7
Mexico
- Currency
- MXN
- Rails
- SPEI
- Speed
- Real-time 24/7
Paraguay
- Currency
- PYG
- Rails
- SIPAP
- Speed
- Real-time 24/7
Peru
- Currency
- PEN
- Rails
- CCE
- Speed
- Real-time 24/7
United States
- Currency
- USD
- Rails
- ACH and wire
- Speed
- Offered
Euro area
- Currency
- EUR
- Rails
- SEPA
- Speed
- Offered
China
- Currency
- CNY
- Rails
- CNY
- Speed
- Offered
Hong Kong
- Currency
- HKD
- Rails
- HKD
- Speed
- Offered
Singapore
- Currency
- SGD
- Rails
- SGD
- Speed
- Offered
Instant rails documented on docs.localpayment.com/docs/global-coverage. Each country page lists every rail. USD (ACH and wire), EUR (SEPA), CNY, HKD and SGD are offered
Payouts
Also offered
USD (ACH and wire), EUR (SEPA), CNY, HKD and SGD payouts are offered.
- USD · ACH and wire
- EUR · SEPA
- CNY
- HKD
- SGD
Money flow
From your balance to the beneficiary
Create the payout, approve it, and follow every status until the credit is complete.
- 1
Your platformLocalpayment:
POST /api/payout/
Beneficiary, amount and country, one by one or in batches.
- 2
LocalpaymentYour platform:
Validation and approval
Data checks and, where configured, double-signature approval.
- 3
LocalpaymentLocal rail / bank:
Sent over the local rail
Bank transfer, Pix, SPEI, wallet or the rail of the country.
- 4
Local rail / bankBeneficiary:
Credit to the account
The beneficiary sees the funds in their account or wallet.
- 5
LocalpaymentYour platform:
Status webhook
Completed, rejected or returned: your system reconciles automatically.
Illustrative flow. Rails, cut-offs and limits vary by country; see the country pages.
Controls
Controls your finance team will trust
Every payout runs through the same checks: the destination is valid, and your balance can cover it. It goes out in real time, 24/7.
Real-time API
Each payout is one API call, 24/7, on rails such as Pix and SPEI. Funds move without a manual approval step.
Low balance alerts
Set a threshold per account and get notified before your balance runs short for upcoming payouts.
Proof of payment download
Download a proof of payment for each completed payout — from the portal or the API — and share it with the beneficiary.
API playground
Payouts, one call at a time
POST /api/payout/ is a real-time API, 24/7. Enter plays simulated responses from the public docs. A marketplace split is several payout calls.
The 80/20 bar is an illustrative storyboard allocation.
Each beneficiary is its own POST /api/payout/.
Illustrative balances
- USD25,000.00
- ARS250,000.00
- BRL184,200.00
- MXN310,500.00
Balances move only inside this demo, by the sample amounts.
USD in this demo: United States, Panama, Peru and El Salvador.
POST /api/payout/ · 1/2
Authorization: Bearer <DEMO_TOKEN>
DEMO · Nothing is sent. This demo never calls Stage or Production.
POST /api/payout/ · 1/2
The simulated response appears here
For developers
One endpoint, country-specific beneficiary fields
Create a payout with POST /api/payout/ — one request for every market, with beneficiary fields that depend on the country and the local rail chosen by payment method code. Authenticate with a Bearer token and follow each payout by signed webhook.
- Your own externalId on every payout; duplicates return HTTP 409
- A signed webhook for every status, 24/7
- Cancel with PATCH /api/payout/cancel; proof of payment via API
# Illustrative request — see docs.localpayment.com for the exact contract curl -X POST https://api.v3.localpayment.com/api/payout/ \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "externalId": "3f9c1b2e-0000-4000-8000-000000000042", "paymentMethod": { "type": "BankTransfer", "code": "0130", "flow": "DIRECT" }, "country": "MEX", "currency": "MXN", "amount": 18400.00, "accountNumber": "<your-account-number>", "conceptCode": "0001", "beneficiary": { "type": "INDIVIDUAL", "name": "Lucía", "lastname": "Méndez", "document": { "type": "RFC", "id": "MEML900101XXX" }, "bank": { "account": { "type": "C", "number": "012180000000000000" } } } }'
// Illustrative. Credentials are injected from your secrets manager, never hard-coded. const auth = await fetch('https://api.v3.localpayment.com/api/token/', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ username: process.env.LP_API_USER, password: process.env.LP_API_PASSWORD, }), }); const { access } = await auth.json(); // Send a Pix payout (fields simplified) const res = await fetch('https://api.v3.localpayment.com/api/payout/', { method: 'POST', headers: { Authorization: `Bearer ${access}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ externalId: crypto.randomUUID(), paymentMethod: { type: 'BankTransfer', code: '0031', flow: 'DIRECT' }, // Pix country: 'BRA', currency: 'BRL', amount: 1250.0, accountNumber: process.env.LP_ACCOUNT_NUMBER, conceptCode: '0001', beneficiary: { type: 'INDIVIDUAL', name: 'Marina', lastname: 'Costa', document: { type: 'CPF', id: '000.000.000-00' }, bank: { account: { alias: 'marina.costa@example.com' } }, // Pix key: send alias, omit account type and number }, }), }); const payout = await res.json(); // status.description: INPROGRESS — the final status arrives by signed webhook await savePayout(payout.externalId, payout.internalId);
Frequently asked questions
In which countries can I send payouts?
Localpayment offers local payout rails on local rails: Argentina, Bolivia, Brazil, Chile, Colombia, Costa Rica, the Dominican Republic, El Salvador, Guatemala, Honduras, Mexico, Panama, Paraguay and Peru.
How fast does a payout arrive?
On Pix, SPEI, COELSA, TEF, CCE, Bre-B and SINPE Móvil, payouts confirm in seconds, 24/7, through the same API.
Do payouts wait for a manual approval?
No. A payout is a real-time API call, 24/7. POST /api/payout/ sends it onto the rail, and each status arrives by signed webhook.
What statuses does a payout go through?
Received (validated and accepted with your externalId), Locked (the amount is reserved from your balance, so it can’t be spent twice), In progress (on the local rail; it can no longer be canceled) and Completed (funds reached the beneficiary). Each change is notified by signed webhook.
Can I cancel a payout?
Yes, until it reaches In progress. Once the transfer is on the local rail, returns and recalls follow the rules of that rail.
How do I fund my payouts?
Payouts are debited from your Localpayment balance, which you can fund with your local collections or with a Wire In in fiat or stablecoins. Low-balance alerts warn you before it runs short.
Can I pay many beneficiaries?
Yes. Send one API call per payout, each with its own externalId, and follow every status by signed webhook.
What does a beneficiary need to provide?
It depends on the rail: a bank account or key (CBU/CVU, Pix key, CLABE, CCI…), the account holder’s name and tax ID. The country guides in the docs list the exact fields per rail.
Do I get proof of payment?
Yes. Completed payouts carry a proof of payment that you can download from the Business Portal or share with the beneficiary.
How do Tax, Bill and Service Payments work in Mexico?
You send a payout to a billing reference instead of a bank account, in MXN, through the same Payout API: paymentMethod.type BillPay, code 0119. Federal taxes (billType 0098) are paid with the corresponding payment reference, and every status is notified by webhook.
Also on the same API
Reporting & reconciliation
Match every payout to your ledger with reports and webhooks.
Reporting & reconciliation —FX & treasury
Quote and lock rates before you convert.
FX & treasury —Tax, Bill and Service Payments
Pay federal taxes in Mexico with the payment reference, through the same API.
Tax, Bill and Service Payments —Coverage
Licensed, registered or supervised presence in local currencies and local rails, country by country.
Coverage —Payment methods directory
Every documented method, with codes, limits and speed by country.
Payment methods directory —Developer quickstart
Get a token, send your first request and receive a webhook on Stage.
Developer quickstart —
Pay out locally, at scale
Get Stage credentials when the partnership starts and go live in weeks. New countries are a configuration, not a reintegration.

Pix, SPEI, COELSA, TEF
























