Experts in Latin American payments

Payments that
route themselves
across Latin America.

Key2Pay is the payment infrastructure for LATAM. Cards, PIX, SPEI, PSE, cash and wallets behind a single API — with routing, retries and settlement that run themselves, so your team stops babysitting failed transactions.

Create account Talk to sales →

Countries live

add figure

Approval rate

add figure

Processed volume

PCI DSS certified

ROUTING DECISION
{{ routeLine }}
{{ routeMeta }}

Local methods, one contract

Smart routing

Every transaction picks its own acquirer.

Issuer behaviour in LATAM changes by hour, BIN and city. Key2Pay scores each acquiring path on live approval data, cost and settlement speed — then sends the transaction down the lane most likely to clear. Declines are retried on a different rail in milliseconds, not the next day.

LIVE LANES

{{ routeClock }}

{{ l.ms }}

              → {{ routeLog }}
            

Reconciliation & settlement

Books that close themselves.

Eight acquirers, four currencies, a dozen settlement files. Key2Pay matches every payout line to the original transaction, flags the exceptions worth a human, and pushes clean journal entries to your ERP.

{{ c.k }}

Cashier integrations

Already live in the cashiers you use.

If your payment orchestration already runs through a cashier, Key2Pay is one more provider to switch on — no new integration on your side.

Coverage

Local acquiring in ten markets.

Domestic entities, domestic settlement, domestic approval rates — not a cross-border gateway wearing a local badge.

{{ c.name }} SETTLES {{ c.settle }}

Developers

One API for the whole region.

Idempotent REST, signed webhooks, sandbox with real rail behaviour per country, SDKs for Node, Python, PHP, Go and Java. Payouts use the same object model as pay-ins.

Read the docs Get sandbox keys

POST /v1/payments

{{ codeSample }}

Start collecting in LATAM this quarter.

Sandbox in minutes. Local acquiring contracts handled by us.

Create account Talk to sales

Four modules. One ledger.

MULTI-USER PER SHOP

Every shop, its own team.

Invite as many users as you need per shop and give each one only what their job requires — finance sees settlements, support sees disputes, developers see keys.

DYNAMIC HELP CENTRE

Answers built into the product.

Our own help centre lives inside the dashboard: searchable guides, per-country method walkthroughs and decline-code explanations, updated as the rails change.

why was my PIX payment declined?

Priced per market, quoted per volume.

Local acquiring rates differ by country and method, so we quote against your real mix instead of publishing one misleading number.

{{ p.price }}

{{ sc.k }}

{{ subRowsHeadA }}
{{ subRowsHeadB }}

Change my cookie choice Current setting: {{ cookieState }}

Payments that
route themselves
across Latin America.

Every transaction picks its own acquirer.

Books that close themselves.

Already live in the cashiers you use.

Local acquiring in ten markets.

One API for the whole region.

Start collecting in LATAM this quarter.

Four modules. One ledger.

Market by market.

Build against real rail behaviour.

Priced per market, quoted per volume.

{{ subTitle }}

Payments thatroute themselves across Latin America.

Every transaction picks its own acquirer.

Books that close themselves.

Already live in the cashiers you use.

Local acquiring in ten markets.

One API for the whole region.

Start collecting in LATAM this quarter.

Four modules. One ledger.

Market by market.

Build against real rail behaviour.

Priced per market, quoted per volume.

{{ subTitle }}

Payments that
route themselves
across Latin America.