Why Localpayment
Local by design. Built for the way each market pays.
Most routes into Latin America stop at routing. We pair a licensed, registered or supervised presence in 18 countries and local rails in 14 with a single integration, so your payments run on the rails customers already use.
- 18 countries
- Local rails in 14
- Approval rates above 99%
- 24/7 support
18 countriesLocalpayment in numbers
- Countries with licensed, registered or supervised presence
- 18
- Countries with local payment rails
- 14
- v4.0.1
- PCI DSS
- Type II
- SOC 2
What sets us apart
Six reasons businesses build on Localpayment
From the license to the last webhook, the pieces that decide whether a payment works locally are in the same place.
Local methods by market
Pix, SPEI, PSE, Bre-B, CVU transfers, QR codes and cards in Argentina, Colombia, Mexico and Peru: the methods each market already uses.
Virtual accounts
Give every customer a unique local account number (CLABE, CVU, CCI or Pix key) and reconcile incoming payments automatically.
Local payouts
Pay out to bank accounts and wallets on local rails, with double-signature approval.
FX with rate lock
Convert within local market hours and lock the rate with a quote token before you execute.
Reporting
Balance, activity and reconciliation reports in the Business Portal and by API, plus real-time webhooks.
One API + Business Portal
One integration for pay-ins, payouts, virtual accounts and FX, managed from one Business Portal. New markets are enabled by configuration.
Two models
An orchestrator routes. Localpayment holds the local entities.
A general comparison of two ways to reach Latin American customers. Check each provider’s own license and coverage details.
Orchestrator only
- Local entitiesThe licensed or registered entity in each market is usually a third party.
- Local railsRoutes to other providers, so coverage and uptime depend on them.
- SettlementSettlement timelines and currencies depend on each underlying provider.
- ReportingReports and reconciliation may be split across several providers.
Localpayment
- Local entitiesA licensed, registered or supervised presence in 18 countries, published country by country.
- Local railsLocal rails in 14 countries behind one API.
- SettlementOne settlement relationship across pay-ins, payouts and FX.
- ReportingOne set of reports and reconciliation in the Business Portal and by API.
Developer experience
Start building the day the partnership starts
Stage (sandbox) credentials are issued at the start of the partnership, so your team can build while the compliance review runs.
- Stage mirrors production without real money, with test cards and payment simulators
- HMAC-signed webhooks and idempotent requests with externalId
- A public, read-only MCP server and llms.txt for AI coding assistants
- Postman collection and plain cURL and Node.js examples — no SDK lock-in
How it starts
From first call to first live payment
Four steps, and your engineers do not wait for the paperwork.
Agreement
Tell us your countries, methods and flows and sign the agreement. KYB runs under the requirements of the authorities that supervise us.
Stage credentials
Stage (sandbox) credentials are issued at the start of the partnership.
Test
Test your integration with test cards and payment simulators that mirror production.
Go live
Go live in weeks. New markets are enabled by configuration, with no reintegration.
Security and compliance
Certified, and verifiable
Independent validation you can request through the Trust Center.
PCI DSS v4.0.1
Card data is handled in a PCI DSS-validated environment, with hosted fields that keep it off your servers.
PCI DSS v4.0.1 —SOC 2 Type II and ISO 27001
A SOC 2 Type II report and ISO 27001 certification cover security controls and the management system.
SOC 2 Type II and ISO 27001 —Encryption and access controls
TLS 1.2+, AES-256 at rest, AWS KMS key rotation, MFA, RBAC, IP allow-listing and double-signature payouts.
Encryption and access controls —
Aleph Group
Part of Aleph Group, an integrated digital and payments ecosystem
Localpayment is part of Aleph Group, which serves 26,000+ advertisers across 55+ platforms in 130+ markets. Those figures describe Aleph Group, not Localpayment on its own.
- Payments in the markets you enter
- Digital media and activation through Aleph
- One partner conversation for both
Media → payments
Activation funnel
- Impressions2.4M
- Sign-ups86K
- Paying users21K
Questions about Localpayment
How is Localpayment different from a pure orchestrator?
An orchestrator routes to other providers. Localpayment pairs a licensed, registered or supervised presence in 18 countries and local rails in 14 with one API, so the rails, the regulatory status and the support team sit in the same place.
Which countries do you cover?
Eighteen countries across Latin America and Canada. The coverage page lists each one with its license status, local rails and currencies.
Do we have to integrate again for each new market?
No. Pay-ins, payouts, virtual accounts and FX share one API. New countries and methods are enabled by configuration.
What approval rates can we expect?
Approval rates above 99%, driven by local methods, native currencies and smart routing across the methods you enable. Results vary by market and method mix.
Which certifications do you hold?
PCI DSS v4.0.1 and ISO 27001 certifications, plus a SOC 2 Type II report. Reports and documentation can be requested through the Trust Center.
How does FX work?
Conversions run within local market hours between local currencies and hard currencies such as USD, EUR and GBP. You see the exact rate before you execute and can lock it with a quote token.
What support do we get?
Customer support 24/7 at support@localpayment.com, a public status page and documentation with a Postman collection, cURL and Node.js examples.
Go local with Localpayment
Tell us your markets and flows. We will show you how the rails, the API and the team fit together.