how to orchestrate LATAM cross-border payments
Treat the region as nine regulators, not one checkout. The work is: choose the rail the customer already uses, collect under a license that is allowed to move that money, settle in the currency that rail pays, and keep a single view of what happened. CoralCommerce does the routing, cascade and reporting. The licensed partner in each market does the regulated part.
- Integrate once. Connect to CoralCommerce through the hosted or headless API (JSON or XML). That is the only engineering event. New countries are connector activations, not new builds.
- Pick the markets, not the continent. Live coverage today is Brazil, Mexico, Colombia, Argentina, Chile, Peru, Ecuador, Panama and Costa Rica. Activate only the countries you will actually collect in.
- Apply to the licensed partner in each market. CoralCommerce does not hold, move or custody client funds. Upstream partners accept the merchant; we then activate the connector for that partner, method and currency.
- Collect on the local rail. Pix in Brazil. SPEI in Mexico. Elo, Hipercard, Naranja, Cabal, Webpay and the international card networks where they are the habit. Bank transfers where they are. Instalments are a normal consumer habit in several markets, so a checkout that can only take a single full-value charge will simply not capture that volume.
- Route, then cascade. Channel rules send each attempt to the connector best suited to that method, currency and region. If that connector cannot complete, the next active one can take the attempt. Reconciliation shows approval rates and decline reasons per connector.
- Settle the way the market allows. Multi-currency settlement is built per market, not adapted from a single-currency model. The merchant owns the commercial agreement with each sponsor, so rates and settlement terms stay visible.
- Reconcile in one place. Approvals, declines, fees, settlements and chargebacks across every Latin American connector sit in one reporting layer. Finance should not need five portals to close a period.
the rails that decide whether the checkout converts
| Market | Named rail or scheme | What the orchestrator must do |
|---|---|---|
| Brazil | Pix; Elo; Hipercard | Collect instant bank-to-bank as a first-class method, presented alongside cards rather than behind a redirect. |
| Mexico | SPEI | Match interbank transfers around the clock, with local acquiring behind them. |
| Argentina | Naranja; Cabal | Local card schemes sit beside Visa and Mastercard, so a stack that only recognises the international networks will turn away customers who would have paid. |
| Chile | Webpay | The domestic card rail is the checkout here, and should be presented as the primary option. |
| Colombia, Peru, Ecuador, Panama, Costa Rica | Local acquiring + cards + bank transfer | Own regulator, own partner, own connector. A Brazil Pix build does not travel. |
We do not claim every informal rail in the region. The list above is what CoralCommerce already publishes as supported. If a buyer needs a rail we have not named, that is a connector conversation — new connectors are added for clients at no additional platform cost, subject to a licensed partner existing.
who offers local payment processing in LATAM markets
The processors are the licensed institutions in each country. The orchestrator is who makes them usable from one integration. CoralCommerce offers local payment processing in LATAM markets in that second sense: we connect you, we do not become the licensee. The longer regional brief is on payment orchestration in Latin America.
holding client funds and orchestrating payments are two different businesses, and plenty of good companies do the first one well. we only do the second, in every market we operate, including these nine.