Frequently asked questions

Localpayment is payment infrastructure for Latin America. Through one API and the Business Portal, businesses collect local payments (pay-ins), send payouts, issue virtual accounts and convert currency across the region.

Localpayment is part of Aleph Group, which pairs payments with digital media for platforms and brands entering emerging markets. Figures such as 26,000+ advertisers, 55+ platforms and 130+ markets describe Aleph Group as a whole, not Localpayment on its own.

Both. We orchestrate payments through one API, and we do it on top of a licensed, registered or supervised presence in 18 countries and local rails in 14, instead of only routing to other providers.

Businesses that collect from or pay people across Latin America: ecommerce and marketplaces, digital goods and gaming, fintechs and wallets, remittance companies, SaaS, travel, mobility, payroll and advertising platforms. The solutions pages show typical flows for each.

Pay-ins with local payment methods and cards, virtual accounts, recurring payments, hosted checkout, payouts, bill pay, FX and treasury, a global treasury account, stablecoin rails, smart routing, and reporting and reconciliation — all through one API and the Business Portal.

No. Localpayment is a payments provider. In each country we hold the license, registration or supervision that local regulation requires for payments — a payment institution in Brazil, a money transmitter in Mexico and so on — and the licenses page lists the exact status for all 18 countries.

The enterprise platform is quoted business by business, so volume is one input among several. Small and mid-size businesses can also request early access to Localpayment for SMBs, a self-serve business account. Tell us about your flows and we will point you to the right option.

We have a licensed, registered or supervised presence in 18 countries, with local payment rails in 14. Payment methods, currencies and license details vary by country; the coverage and licenses pages list them one by one.

It depends on the country: bank payments such as Pix in Brazil, SPEI in Mexico, Bre-B and PSE in Colombia and Debin in Argentina; QR payments in Argentina, Bolivia, Guatemala and Peru; virtual accounts in seven countries; and cards in Argentina, Colombia, Mexico and Peru. The payment methods directory lists every method by country.

No. In Brazil, customers pay with Pix — by QR code or Copia e Cola — or by transfer to a virtual account identified by a Pix key. Cards are available in Argentina, Colombia, Mexico and Peru.

Visa and Mastercard in Argentina, Colombia, Mexico and Peru, plus American Express, Diners Club, Naranja and Cabal in Argentina and American Express and Diners Club in Colombia. 3D Secure, installments and subscriptions are available in Colombia, Mexico and Peru.

No. You integrate once and add markets by configuration, with no reintegration. A new country or payment method may require an additional compliance review.

The coverage pages list every country with its license status, currencies and rails, and the payment methods directory lists every method by country. Live availability of each country’s rails is published at status.localpayment.com.

Our catalog centers on bank payments, QR, virtual accounts and cards — the methods most people in the region use online today. If your use case needs a cash option in a specific country, talk to sales.

For collections, we offer QR and transfer methods rather than wallets: interoperable QR and CVU transfers in Argentina, Pix in Brazil, QR in Bolivia and Peru, and QR Fri and Wallet Fri in Guatemala. For payouts, wallets are reachable in 9 countries (Argentina, Bolivia, Brazil, Chile, Colombia, Costa Rica, El Salvador, Mexico and Peru): with direct wallet integration in Bolivia, Costa Rica and Peru, and through bank rails in the rest.

Yes. Pix in Brazil, SPEI in Mexico, Bre-B in Colombia, COELSA transfers in Argentina, TEF in Chile, CCE in Peru and SINPE Móvil in Costa Rica confirm in seconds, 24/7, within each rail’s limits.

Coverage grows continuously, but we only publish what is live today. If you need a market or method that is not listed, tell sales: it helps us prioritize and we can share what we are able to support for your case.

Bank-transfer payouts run over local rails in 14 countries: Argentina, Bolivia, Brazil, Chile, Colombia, Costa Rica, the Dominican Republic, El Salvador, Guatemala, Honduras, Mexico, Panama, Paraguay and Peru.

On real-time rails such as Pix, SPEI, COELSA, TEF, CCE, Bre-B and SINPE Móvil, payouts confirm in seconds, 24/7, within each rail’s limits. Batch rails such as ACH or TED credit the same day or the next business day, depending on cut-off times.

Yes. Wallet payouts reach 9 countries. Direct wallet integration is available in Bolivia, Costa Rica (SINPE Móvil) and Peru, and bank-transfer payouts can reach wallets in Argentina, Bolivia, Brazil, Chile, Colombia, El Salvador and Mexico.

Yes. With double signature, one user creates a payout and a different user authorizes it — using requireAuth in the API or the approval queue in the Business Portal.

Proof of payment is available for each payout through the API and the Business Portal, and every status change — from Pending Authorization to Completed — arrives by signed webhook.

Through the API, one request per payout from your own systems, or by uploading a batch file in the Business Portal. Both routes support double-signature approval and report each payout’s status by webhook.

The beneficiary’s name, tax ID (CPF or CNPJ, CUIT, RFC, NIT and so on) and bank account identifier — CBU or CVU, CLABE, Pix key, CCI, IBAN or the local equivalent — plus the fields local regulation requires in that country. The API validates formats before the payout is sent.

If validation or the bank rejects it before it is sent, you receive a Rejected status with the reason. On batch rails a beneficiary bank can return a payment days later; the funds are then credited back to your balance and you are notified by webhook.

Payouts on real-time rails are final once completed. For other rails a recall is a manual, best-effort process handled with support, and it depends on the receiving bank. Validating beneficiary data and using double signature are the best protection.

Yes. Payouts are debited from your Localpayment balance, which you fund with a Wire In in hard currency or stablecoins or with the proceeds of your pay-ins, depending on your agreement.

Individuals and companies: suppliers, sellers, creators, drivers and couriers, gig workers, remittance beneficiaries and wallet users withdrawing their balance. Payouts are always in local currency over local rails.

Local currencies convert into hard currencies: USD, EUR, GBP, CAD, AUD, NZD and CHF, plus the stablecoins USDC and USDT. Conversions run from local to hard currency.

Within each local market’s hours, which vary by country — for example, 10:00–12:30 in Brazil and 08:00–15:30 in Mexico, local time. Conversion is not available around the clock; the docs list the hours for each country.

Yes. Request a quote and you receive a quote token (exchangeRateToken) with an expiration date. Operations submitted with that token before it expires use the locked rate.

With a Wire In: a bank transfer that you notify through the API or the Business Portal, or USDC or USDT on Ethereum or Tron, which are detected and credited automatically, usually 2–10 minutes after on-chain confirmation.

With a Wire Out to your own external bank account or to an allow-listed USDC or USDT wallet. Wire Outs never go to third parties; payments to third parties use payouts.

No. Stablecoins are a treasury tool: USDC and USDT fund your business account and can be withdrawn to allow-listed wallets. We do not offer crypto on-ramps or off-ramps for consumers.

Request a quote through the API or the Business Portal and you receive the rate for that moment, including the margin set in your agreement, with a quote token that locks it until it expires. The applied rate is recorded on each conversion.

Yes. Your account keeps a separate balance per currency — local currencies where you collect, plus the hard currencies and stablecoins you convert to or fund with — and the Business Portal shows activity by currency.

A pay-in is a payment from your customer. A Wire In is your own money: a transfer or a USDC or USDT deposit that funds your Localpayment balance, typically before sending payouts.

A Wire Out in fiat follows the processing time of the receiving bank and the rail used; stablecoin withdrawals are confirmed on-chain. You can follow each Wire Out in the Business Portal and by webhook.

FX conversions run from local to hard currency. To pay locally, fund your account in hard currency or stablecoins and payouts are executed in local currency from your balance under your agreement.

Yes. Refunds are available for card payments, virtual accounts and alternative payment methods. For card chargebacks, you can upload evidence for each dispute through the API or the Business Portal.

It depends on the method. Card refunds appear on the statement once the issuer posts them; refunds of bank transfers, QR and virtual-account payments are sent to the payer’s account over the local rail. Each refund has its own status and webhook.

Refund rules depend on the payment method. The refunds section of the docs states, for each method, whether partial refunds are allowed and within which time window.

The cardholder disputes a charge with the issuer, the amount is reversed and you are notified in the Business Portal and by webhook. You can upload evidence through the API or the portal within the deadline set by the card scheme; the issuer decides the outcome.

Bank payments do not have the card chargeback mechanism: once a transfer is confirmed, the funds are yours. If you need to return money, you issue a refund.

Offer local bank methods, enable 3D Secure on cards, keep proof of delivery, and respond to disputes with evidence on time. Our platform adds fraud controls such as velocity checks and risk scoring.

A refund is a return of funds you initiate. A return is a payout sent back by the beneficiary’s bank, for example because the account was closed. A chargeback is a card payment reversed by the issuer at the cardholder’s request.

POST /api/token/ exchanges your API username and password for an access token valid for 5 minutes and a refresh token valid for 24 hours. Send the access token as Authorization: Bearer on every call, from server-side code only, and allow-list your server IPs in the Business Portal.

There are no official server SDKs: the REST API works with any HTTP client, and the docs include a Postman collection. For card capture in the browser, the Smart Fields JavaScript SDK provides hosted card fields.

Send your own unique externalId with every transaction. Reusing it returns HTTP 409 Conflict instead of creating a second transaction, so retrying after a timeout is safe.

You configure an HTTPS endpoint in the Business Portal. Each notification is signed with HMAC-SHA256 of the raw body, sent in the x-Signature header. Return 200 quickly and process asynchronously; deliveries without a 200 are retried with exponential backoff.

Yes. Stage (api.stage.localpayment.com) mirrors production without real money, with test cards, a virtual-account payment simulator and payout test scenarios.

Yes. A public, read-only MCP server at docs.localpayment.com/mcp and an llms.txt index let your assistant work from the real API contract. Review generated code like any other code before it ships.

A direct REST API, a hosted WebCheckout page, payment links, an embedded iframe, the Smart Fields JavaScript SDK for card capture, batch uploads in the Business Portal and an MCP server for AI coding tools. The integrations page compares effort and PCI scope for each.

The web console for your team: monitor transactions, upload batch payouts, configure webhooks and IP allow-listing, manage users with custom roles and permissions, and approve payouts under double signature.

With standard HTTP status codes — 4xx for request errors and 5xx for server errors — plus an error code and message, and field-level details for validation errors. Log the error code with your externalId to speed up support.

Yes. The docs include a Postman collection with Stage and Production environments, example requests for every endpoint and authentication helpers.

Yes. The API limits request volume to protect the service. When you receive a limit response, back off exponentially instead of retrying immediately, and rely on webhooks rather than polling for status.

Once Stage testing, the security review and KYB are complete, you receive production credentials. Switch the base URL to api.v3.localpayment.com, allow-list your production IPs and configure your production webhook endpoint. The API contract is the same.

Compute HMAC-SHA256 over the raw request body with your webhook secret and compare it, using a constant-time comparison, with the hex value in the x-Signature header. Reject the notification if they differ.

Yes. Platforms, marketplaces and PSPs operate several merchants or entities through one integration. How accounts, balances and settlements are organized depends on your model — talk to sales about the setup.

Customer support is available 24/7 at support@localpayment.com. Security reports go to cybersecurity@localpayment.com, and customers in Brazil can reach our ombudsman at ouvidoria@localpayment.com.

status.localpayment.com shows the live availability of pay-in, payout and authentication services and of each country’s rails, plus incident history.

Write to support@localpayment.com. Customers in Brazil can reach our ombudsman at ouvidoria@localpayment.com, and anyone can use the ethics channel at https://www.contatoseguro.com.br/en/localpayment. The complaints policy is published in the legal section.

Localpayment processes payments for businesses, so the charge comes from a merchant you bought from. Contact that merchant first. If you cannot identify it, write to support@localpayment.com with the date and amount and we will help.

Yes. A technical team supports your integration from a kickoff call to go-live, including integration reviews and testing support, and support@localpayment.com answers 24/7.

Check status.localpayment.com for live availability and incident history, and write to support@localpayment.com with your externalIds and timestamps. Customer support answers 24/7.

docs.localpayment.com has the integration guides and the API reference. The developer hub on this site links the quickstart, sandbox, webhooks and AI tools pages.