Provider type: apm · On request
dLocal + Tranzify
dLocal is a licensed cross-border payment provider based in Montevideo that covers the local methods of Latin America: PIX and Boleto in Brazil, SPEI and OXXO Pay in Mexico, PSE in Colombia, Yape in Peru, Khipu in Chile and the Mercado Pago wallet across the region, with settlement in BRL, MXN, ARS, COP, PEN and CLP. Through Tranzify a client enables dLocal under its own contract, adds it to its routing rules and cascades it with EBANX; the integration is the platform's, not the client's.
- Currencies
- BRL, MXN, ARS, COP, PEN, CLP
- Supported operations
- deposit · payout · refund
- Website
- https://dlocal.com
What the integration covers
dLocal in the Tranzify catalogue covers PIX and Boleto in Brazil, SPEI and OXXO Pay in Mexico, PSE in Colombia, Yape in Peru, Khipu in Chile and the Mercado Pago wallet in Brazil, Mexico, Argentina, Chile, Colombia and Peru. PIX, SPEI, PSE, Yape and Khipu confirm within seconds or minutes; a boleto or an OXXO reference is paid in cash or in a banking app and confirmed by the next day. The settlement currencies are BRL, MXN, ARS, COP, PEN and CLP. The operations are pay-ins, payouts and refunds: a payout goes to a PIX key or a local bank account, and a refund returns to the payer through the method that took the payment where it allows one; the cash methods are pay-in only. Recurring payments are not part of this integration.
How a client enables it
A Tranzify client, a licensed PSP, acquirer or fintech, opens an account with dLocal under its own licence and contract; dLocal settles the funds to the client. The client enters the dLocal credentials in the terminal settings in the Tranzify back office, adds the terminal to its routing rules and cascades it with other providers of the same methods, EBANX for most of them, PagSeguro for the Brazilian ones, Conekta or Openpay for the Mexican ones, so that a declined payment is retried elsewhere. Tranzify routes every payment, verifies the dLocal callbacks before a status changes, journals every attempt and result and calls the merchant’s webhook. The integration is enabled on the client’s request and is built and tested against the dLocal sandbox before the terminal goes live.
How to connect
- 1Onboard with Tranzify and get your network, keys and back office.
- 2Enter your account with the provider in the terminal settings — Tranzify already speaks its API.
- 3Add routing rules: countries, currencies, amounts, BIN ranges, priorities and weights.
- 4Go live. Every payment, callback and retry is in the journal for five years.
Frequently asked questions
Which countries and currencies does dLocal cover?+
What does the client need?+
How is the integration enabled?+
See the platform on your own flows
Thirty minutes with an engineer, not a sales deck: your providers, your routing rules, your merchants' checkout.
- ✓ Not a financial institution
- ✓ Money never passes through us
- ✓ Built to PCI DSS requirements