Skip to content

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 payins, virtual accounts, payouts and FX through one API, and offer them to their own customers.

Talk to partnershipsPartner program
  • Local rails
  • Virtual accounts per sub-merchant
  • Funding by wire, USDC or USDT
Coverage
CanadaArgentinaChileDominican RepublicMexicoUruguayBrazilBoliviaPeruColombiaPanamaCosta RicaNicaraguaHondurasEl SalvadorGuatemalaEcuadorParaguay

Delivering results for global businesses

  • Airwallex
  • LianLian Global
  • PayPal
  • XTransfer
  • TransferMate
  • PingPong
  • Global66
  • Skyee
  • TransFi
  • GCC Remit
  • Nium
  • Routefusion
  • Trolley
  • Cadana
  • neomoney
  • Rapyd
  • TerraPay
  • CurrencyBird
  • Ontop
  • Thunes
  • Triple-A
  • Xtract
  • Payoneer
  • Noah
  • Ksher
  • Manteca

Market figures

The volume your merchants expect you to handle

Public figures from official and industry sources. Each one links to its source.

Why Localpayment

One partner for every Latin American rail

Skip the licenses, the rail-by-rail integrations and the sub-merchant plumbing, and offer payins, virtual accounts, payouts and FX to your customers through one API.

Talk to our sales team

Tell us your markets and volumes, and we’ll design the integration with you.

Contact sales

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. 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. 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. 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. 3

    LocalpaymentYour platform:

    Signed webhook

    Each status change is signed with HMAC-SHA256 and carries your external ID. Reply 200, process asynchronously, deduplicate.

  4. 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. 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. 6

    Your platformLocalpayment:

    Order the payout

    POST /api/payout/ per merchant . Add requireAuth when you want a second approver.

  7. 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.

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. We work with PSPs and gateways, orchestrators, banks and neobanks, digital wallets, cross-border B2B platforms and money-transfer operators.

  • Direct REST API: one integration for payins, 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
Talk to partnerships

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
Webhooks guide
// 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.

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 local currencies, with local rails. The coverage page lists the methods country by country.

How do we pay out to our merchants?

With POST /api/payout/, with one API call per payout, on real-time rails such as Pix, SPEI, Bre-B, COELSA, TEF and CCE. Add requireAuth when you want a second approver, 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. Stage credentials arrive at the start of the partnership, and the first market can go live in weeks.

Keep exploring

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.

Contact salesGo to our docs

How can we help?

Download your copy

Leave your details and get the full edition instantly.