ProtosPay
Book a demo
Payment orchestration · Latin America

Connect once. Change providers whenever you need to.

When your bank or PSP stops converting, moving to another one usually means a new contract, a new integration and months of engineering. With ProtosPay you integrate one API. We connect and maintain the banks and PSPs in each country, so switching or adding a provider is a setting, not a project.

Book a demo See how it works
  • No integration per country
  • No code change to switch
Your payment traffic · exampleMX · BR · CO
Your platform1 integrationProtosPayrouting · ledgerreconciliationMexicoBrazilColombiaBank A60%PSP B40%PSP C70%Bank D30%PSP E100%PSP Fstandby

All providers healthy. Traffic is split by approval rate and cost.
The problem

Your payment provider shouldn't be a one-way door.

Direct integrations lock you in. When approval rates drop, fees go up or a provider has an outage, the cost of leaving is so high that most companies stay and lose sales.

Switching a provider today 7 workstreams

  1. Find and negotiate with a new local provider Separate contract, KYC and onboarding
  2. Integrate a new API New auth, payloads and error codes
  3. Rebuild webhooks and status mapping
  4. Adapt reconciliation to a new file format
  5. Certify, test and run in parallel
  6. Migrate traffic and roll back if it fails
  7. Repeat for every country you operate in

Switching with ProtosPay 1 setting

  1. Provider contracts and onboarding Managed by ProtosPay
  2. Provider API integration Already connected and maintained
  3. Webhooks and status mapping One event format for every provider
  4. Reconciliation formats Normalized into one ledger
  5. Certification and testing Done once, on our side
  6. Change the routing rule in the dashboard Or let smart routing do it automatically
  7. Per-country repetition Same API in all 10 countries
How it works

You integrate with us. We integrate with everyone else.

Your team never builds or maintains a connection to a local bank or PSP. You choose one or several providers per country, and you can change that choice at any time.

  • 1integration

    One API for everything

    Pay-in, payout, cross-border, fiat and crypto through the same endpoints, the same events and the same reports.

  • Nproviders

    One or many per country

    Run a single provider in a country or several in parallel. Split traffic by percentage, method, amount or merchant.

  • 0code changes

    Switch without engineering

    Move traffic between providers from the dashboard or the API. Your checkout and backend stay the same.

Smart retries

When a provider fails, your sales don't.

ProtosPay watches every connection in real time. When approvals drop or a provider times out, we retry the payment on the next best route and move traffic away until it recovers.

With a direct integration, an incident means an on-call alert, an emergency change and lost revenue. With ProtosPay it is a line in your activity log.

  1. 14:02:10
    Approval rate drops on PSP E Colombia · PSE · 91% → 74% over 3 minutes
  2. 14:02:14
    Timeouts detected Payments start failing with retryable errors
  3. 14:02:14
    Failed payments retried on PSP F Same request, same idempotency key, approved
  4. 14:02:30
    New traffic routed to PSP F PSP E moved to standby until health checks pass
  5. 16:40:00
    PSP E recovers, traffic rebalanced Back to the routing rule you configured
  6. —
    Your team's action: none You get a notification and a full report
One view

Every country and every provider on one screen.

Volume, approval rate, cost and balance for all your countries, merchants and currencies, consolidated or broken down by provider.

Volume · last 30 days
US$ 18.4M
Approval rate
93.6%
Active providers
14
Recovered by retries
US$ 412k
Country Providers Approval Volume (USD) Avg. cost Balance
BrazilBRL 96.2% 7,920,400 0.9% R$ 2,104,330
MexicoMXN 93.1% 4,310,900 1.4% MX$ 9,882,100
ColombiaCOP 90.4% 2,640,200 1.8% COP 1.92B
ChileCLP 94.0% 1,780,500 1.2% CLP 310.4M
PeruPEN 91.7% 1,020,300 1.6% S/ 840,220
ArgentinaARS 88.3% 728,000 2.1% ARS 96.1M
Active provider Failover provider Paused Example data

Live in 10 countries

Local banks and PSPs already connected in each market.

  • Mexico MXN

    SPEI, OXXO, cards

  • Brazil BRL

    Pix, boleto, cards

  • Colombia COP

    PSE, Nequi, cards

  • Chile CLP

    Transfers, Webpay, cards

  • Peru PEN

    Yape, Plin, cards

  • Argentina ARS

    CVU transfers, cash, cards

  • Costa Rica CRC

    SINPE Móvil, cards

  • Ecuador USD

    Transfers, cards, cash

  • Guatemala GTQ

    Transfers, cards, cash

  • Panama USD

    Yappy, ACH, cards

Platform

Everything between your checkout and the bank.

Four layers, one platform. Use all of them or only the ones you need.

Move

Money in and out

  • Pay-inLocal methods in every country
  • PayoutTo bank accounts, wallets and Pix keys
  • Cross-border transfersCollect locally, settle in USD
  • Crypto and fiatStablecoins on the same rails
Route

The best path for each payment

  • Smart routing and retriesBy approval, cost and latency
  • Smart splittingSellers, partners and fees in one payment
  • Customizable checkoutYour brand, your methods
  • Geolocated checkoutChoose the region it runs in
Record

One source of truth

  • Smart LedgerDouble-entry and immutable
  • ReconciliationMatched against every provider
  • Multi-currencyA balance per currency
  • Multi-merchantBrands and sub-merchants under one account
See

Know what is happening

  • ObservabilityPer country, method and provider
  • NotificationsWebhooks, email and Slack
  • AI AssistantAsk about your payments in plain language
  • Developer docsAPI reference, sandbox and SDKs
Developers

Your code doesn't name a provider.

You send a payment to ProtosPay. Which bank or PSP processes it is a routing rule, so changing providers never touches your codebase.

  • One schema for every country, method and provider
  • One event format for webhooks, whoever processed the payment
  • Sandbox with simulated providers, outages included
routing-rules.json colombia · pse 
// Edit in the dashboard or via API. No deploy needed.
{
  "country": "CO",
  "method": "pse",
  "strategy": "best_approval",
  "providers": [
    { "id": "psp_e", "weight": 70 },
    { "id": "bank_g", "weight": 30 }
  ],
  "failover": ["psp_f"],
  "retry_on": ["timeout", "provider_unavailable"]
}

Your payment request stays the same before and after a switch. Only this rule changes.

Enterprise

Built for teams with strict requirements.

  • Fully isolated database

    A dedicated database and encryption keys per client. No shared tables.

  • Data residency

    Choose the region where your data and checkout run.

  • Access control

    Scoped API keys, allowed IPs and approval flows for payouts.

  • Audit trail

    Every action by every user and key, exportable.

  • Fraud screening

    Rules and risk scoring before a payment reaches a provider.

  • No single point of failure

    Multiple providers per country and redundant infrastructure.

Book a demo

Tell us which providers you use today.

We'll show you how your current setup maps to ProtosPay, which providers we can add in each country, and what a switch would take.