TLDR
- A generic global payout API like Stripe or Wise can reach Brazil and Mexico, but it often routes through correspondent banks, adding one to three days and FX markups that regional specialists avoid by connecting directly to PIX and SPEI.
- PIX, Brazil’s instant payment rail, settles 24/7 in seconds. SPEI, Mexico’s interbank system, clears in minutes. Providers without direct connections to these rails fall back to slower, more expensive alternatives.
- The vendors that matter most for LatAm payouts are dLocal, EBANX, Thunes, Rapyd, Payoneer, Conduit, and Mural, each with different strengths by country, rail, and use case.
- Country coverage is the first filter. No single provider covers every LatAm market with equal depth. Argentina and Venezuela require specialists; Brazil and Mexico have wider options.
- Pricing for LatAm payout APIs is almost never public. Budget for a mix of per-transaction fees, FX spread, and monthly platform minimums before shortlisting vendors.
The best Latin America payout APIs for paying sellers and contractors are dLocal, EBANX, Thunes, Rapyd, Payoneer, Conduit, and Mural. Each connects to local rails like PIX in Brazil and SPEI in Mexico, avoiding the correspondent-bank delays and FX markups that hurt global-first alternatives. The right choice depends on which countries your payees are in, your transaction volume, and whether you need API-first infrastructure or a managed payout service.
Why Does a Global Payout API Fail on LatAm Local Rails?
Most US platforms assume their existing payout stack handles Latin America. It does, technically. But “handles” and “handles well” are different things. A provider routing a payment to a Brazilian seller through SWIFT adds settlement delays and bank intermediary fees that PIX eliminates entirely. PIX settles in seconds, around the clock, including weekends and holidays. SWIFT does not.
Mexico’s SPEI operates similarly: near-instant interbank transfers that clear in minutes, with no correspondent bank in the middle. A provider that does not hold a direct connection to SPEI through a licensed Mexican financial institution is routing around the rail, not through it. That gap shows up as failed transactions, delayed settlements, and higher FX costs that your contractors or sellers absorb.
The deeper problem is regulatory. Brazil requires that foreign companies sending payouts comply with Banco Central do Brasil rules. Mexico has CNBV licensing requirements for domestic payment processing. Providers without local entities or banking partnerships in each country either pass compliance risk to you or limit the instruments available. That is the gap regional specialists fill, and why this decision is not simply “which API has the best docs.”
The FintechSpecs LatAm Rail Fit Test: How to Evaluate Any Payout API
Before reviewing specific vendors, it helps to have a consistent evaluation lens. The FintechSpecs LatAm Rail Fit Test is a four-check framework for cutting through vendor marketing on LatAm payout APIs.
Rail depth: Does the provider connect directly to PIX and SPEI, or does it route through a partner bank that adds a layer? Ask for documentation of their local banking relationships, not just a country flag on their coverage map.
Payee instrument breadth: Can your recipients receive funds to a local bank account, digital wallet, or cash pickup location? Brazil alone has contractors who primarily transact through Nubank or Mercado Pago. Coverage without instrument depth is partial coverage.
FX transparency: Does the provider disclose its spread at the time of transaction, or does it bundle the markup into the exchange rate with no disclosure? Spreads on BRL and MXN can range from under 1% to over 3% depending on the vendor and volume tier.
Compliance posture: Does the provider hold its own licenses in Brazil and Mexico, or does it rely entirely on banking partners? Providers with their own regulatory footprint in-country can handle edge cases like large contractor payments or politically exposed person flags without routing you to their compliance team every time.
Country and Rail Coverage Table
| Provider | Brazil (PIX) | Mexico (SPEI) | Colombia | Argentina | Chile | Peru | Best For |
|---|---|---|---|---|---|---|---|
| dLocal | Yes | Yes | Yes | Yes | Yes | Yes | Widest LatAm coverage, enterprise volume |
| EBANX | Yes | Yes | Yes | Limited | Yes | Yes | Brazil-first, established local rails |
| Thunes | Yes | Yes | Yes | Yes | Yes | Yes | Global multi-corridor with LatAm depth |
| Rapyd | Yes | Yes | Yes | Limited | Yes | Yes | Fintech wallet + local bank payout combos |
| Payoneer | Yes | Yes | Yes | Yes | Yes | Yes | Contractor and freelancer payouts at scale |
| Conduit | Yes | Yes | Yes | Limited | Limited | Limited | Stablecoin-to-local-bank, USD-native teams |
| Mural | Yes | Yes | Yes | Yes | Yes | Yes | USD/stablecoin payouts with local off-ramp |
| EBANX Pay (standalone) | Yes | Yes | No | No | No | No | Pure Brazil/Mexico payout without broader LatAm |
Which Provider Is Best for Brazil PIX Payouts via API?
dLocal
dLocal is the most complete option for platforms that need to pay sellers or contractors across multiple LatAm countries from a single API. Its Brazil coverage includes PIX, TED, and bank account transfers, and the company holds its own regulatory licenses in Brazil rather than relying entirely on a banking partner. For enterprise platforms processing high volume, dLocal’s account managers negotiate custom FX spreads and per-transaction fees directly. Pricing is not public as of October 2026. The trade-off is that dLocal is built for volume: smaller platforms often find the commercial minimums aggressive and the onboarding process slow relative to self-serve alternatives.
EBANX
EBANX started as a Brazil-focused payment processor before expanding across LatAm. Its PIX payout integration is one of the more mature in the market, with direct Banco Central do Brasil connectivity and support for both bank account and digital wallet payouts. EBANX also supports boleto bancário for contexts where a contractor does not have a bank account. Pricing is custom and negotiated by volume. For platforms where Brazil is the primary payout market and other countries are secondary, EBANX’s depth in Brazilian payment infrastructure is hard to match.
Rapyd
Rapyd takes a collect-and-disburse approach: it supports PIX payouts in Brazil and SPEI in Mexico alongside over 900 payment methods globally. The developer API is well-documented, which makes it a reasonable choice for product teams that want to build a LatAm payout flow without managing multiple regional provider integrations. Rapyd’s LatAm coverage is real, but it skews toward bank account deposits rather than cash or wallet payouts in smaller markets. Pricing is custom as of October 2026.
Which Provider Is Best for Mexico SPEI Payouts via API?
dLocal
On the Mexico side, dLocal’s SPEI connectivity is similarly strong. It supports CLABE-based bank transfers, which is the standard format for SPEI payments in Mexico, and handles tax ID (RFC) validation that Mexican regulations require for contractor payments above certain thresholds. Platforms paying Mexican contractors at scale will find the compliance handling particularly useful, since dLocal manages RFC validation in the payout flow rather than requiring your team to build it.
Payoneer
Payoneer approaches LatAm payouts differently from dLocal or EBANX. Rather than paying directly into a recipient’s local bank account, Payoneer credits the recipient’s Payoneer account, which they then withdraw to a local bank via SPEI in Mexico or PIX in Brazil. This two-step flow adds friction for recipients unfamiliar with Payoneer, but it dramatically simplifies compliance for the paying platform. Payoneer handles KYC on the recipient side. For US-based companies paying freelancers or gig workers who are already on Payoneer, the setup is fast. Payoneer’s fee structure includes a percentage-based fee per payout; the specific rate depends on the payout method and destination, and is disclosed in their public pricing materials.
Which Providers Work Best for Contractor Payouts Across Multiple LatAm Countries?
Thunes
Thunes is a Singapore-headquartered infrastructure provider that has built deep local rail connections across LatAm, Africa, and Southeast Asia. In Latin America, Thunes connects to PIX, SPEI, and local rails in Colombia, Peru, Chile, and Argentina. The company was recently highlighted in J.P. Morgan’s Xpedite Remit cross-border partnership, which signals the depth of its rail network. Thunes is infrastructure-first: you integrate once and route payouts to multiple corridors without managing separate provider relationships. It is not a self-serve product and requires a commercial agreement. For platforms paying contractors in five or more LatAm countries, Thunes reduces integration complexity meaningfully.
Mural
Mural is built for US companies paying international contractors and sellers in a way that blends stablecoin infrastructure with local off-ramps. A company sends USDC from a US account; Mural converts and delivers to the recipient’s local bank account in BRL, MXN, COP, or other LatAm currencies. This architecture is particularly useful when your treasury wants to hold USD exposure while paying locally, or when you are already using stablecoin infrastructure elsewhere in your stack. Mural’s country coverage spans most of LatAm. Pricing is not publicly listed as of October 2026. For a broader view of stablecoin payout options, the FintechSpecs guide to stablecoin payout platforms for contractor payments covers the infrastructure in more depth.
Conduit
Conduit occupies a similar niche to Mural: USD or stablecoin in, local currency out to a LatAm bank account. Conduit’s primary corridors include Brazil, Mexico, and Colombia, with the flow designed for B2B payments and contractor payouts rather than consumer remittance. The developer API is the product, and the documentation is oriented toward engineering teams building payout workflows into existing platforms. Conduit is a leaner product than dLocal or EBANX, with less coverage in smaller LatAm markets. For teams that want a clean API for the three largest LatAm markets and are comfortable with a stablecoin settlement layer, it is worth evaluating alongside Mural.
How Do FX Spreads and Fees Actually Work for LatAm Payouts?
Every LatAm payout API charges a combination of a per-transaction fee and an FX spread. The spread is where most of the cost hides. A provider showing a “0% fee” on their marketing page often builds a 1.5% to 2.5% markup into the exchange rate. On a $500 contractor payment converted to BRL, that is $7.50 to $12.50 in hidden cost per transaction.
Consider a platform paying 200 contractors in Brazil monthly at an average of $800 each. That is $160,000 per month in outbound payouts. A provider with a 2% blended FX spread and a $2 per-transaction fee costs roughly $3,600 per month in payout fees. A provider with a 0.8% spread and $3 per transaction costs $1,880. At scale, the spread differential dominates the per-transaction fee. This is why negotiating the FX markup separately from the per-payout fee matters, and why providers who disclose both numbers at the API response level (not just in the contract) make reconciliation far easier. The FintechSpecs cross-border payout fee comparison breaks down FX markups and per-payout pricing across major providers in detail.
Argentina adds another layer of complexity. Parallel exchange rates, capital controls, and restrictions on USD remittances mean that paying contractors in Argentina often requires a provider with specific in-country experience and legal structure. dLocal and Thunes both operate there, but success rates and effective rates vary based on the payment instrument and regulatory environment at the time of transfer. If Argentina is a significant market for you, test it specifically rather than assuming coverage implies smooth delivery.
What Is the Fastest Way to Pay LatAm Contractors as a US Platform?
PIX payouts to Brazil settle in seconds when the provider has a direct connection. SPEI payouts to Mexico typically clear within minutes during operating hours. The delay most US platforms experience is not in the local rail itself but in the provider’s own treasury operations: how fast they move USD from your account into their local currency float, and whether their float is sized to handle your volume without queuing.
Providers like dLocal and EBANX maintain in-country liquidity pools that allow same-session settlement without waiting for a cross-border wire to clear. Providers that do not maintain their own local treasury rely on correspondent transfers that can take 24 to 48 hours before the local rail leg even begins. This is the difference that shows up when a contractor in São Paulo asks why their payment has not arrived. For platforms where contractor satisfaction is tied to payout speed, asking the specific question “how do you fund your in-country liquidity in Brazil and Mexico?” separates real infrastructure from relabeled aggregators.
If instant payouts in the US are also on your roadmap, the FintechSpecs guide to instant payout providers for gig and creator platforms covers the domestic side of that infrastructure decision.
Comparing the 8 Best Latin America Payout API Providers
| Provider | PIX Payout API | SPEI Payout API | Pricing Model | Self-Serve Onboarding | Best Use Case |
|---|---|---|---|---|---|
| dLocal | Yes, direct | Yes, direct | Custom (enterprise) | No | High-volume multi-country LatAm payouts |
| EBANX | Yes, direct | Yes | Custom | No | Brazil-primary platforms, established rails |
| Thunes | Yes | Yes | Custom | No | Multi-corridor infra, single API for 5+ countries |
| Rapyd | Yes | Yes | Custom | Partial (sandbox) | Fintech platforms, wallet + bank payout combos |
| Payoneer | Via withdrawal | Via withdrawal | Percentage per payout | Yes | Freelancer and contractor payouts, payee KYC handled |
| Conduit | Yes | Yes | Not publicly disclosed | Partial | USD/stablecoin-to-local, Brazil/Mexico/Colombia |
| Mural | Yes | Yes | Not publicly disclosed | Partial | Stablecoin treasury + local LatAm payout delivery |
| EBANX Pay | Yes | Yes | Custom | No | Brazil and Mexico only, payment-focused platforms |
What Should Platforms Know Before Integrating a LatAm Payout API?
Onboarding timelines for enterprise LatAm payout providers are longer than most teams expect. dLocal, EBANX, and Thunes all require KYB on the platform side, meaning your company needs to provide corporate documentation, ownership structure, and often a description of payout use cases before an account goes live. Budget four to eight weeks for this process, not four to eight days.
Payee information requirements in LatAm are also stricter than in the US. For Brazil PIX payouts, you typically need the recipient’s CPF (individual tax number) or CNPJ (company tax number) and a PIX key, which can be a phone number, email, CPF, or random key. For Mexico SPEI, you need the recipient’s CLABE, an 18-digit bank code. Your payout API needs to validate these before submission, or your failure rate will be high. Most providers handle this validation, but you should confirm it explicitly rather than assuming.
Tax withholding rules vary by country and payee type. Some LatAm jurisdictions require the paying platform to withhold local income tax on contractor payments above certain thresholds. This is separate from US 1099 obligations. If you are scaling contractor payouts in Brazil or Mexico, this intersects with your broader tax compliance stack. The FintechSpecs guide to 1099 and tax compliance APIs for contractor payments covers the US side, but LatAm local withholding requires country-specific legal guidance beyond API coverage.
Frequently Asked Questions
What is the best API for PIX payouts to Brazil?
dLocal and EBANX both offer direct PIX payout API connectivity with in-country liquidity. dLocal is better for platforms paying across multiple LatAm countries from a single API. EBANX is often the better choice for platforms where Brazil is the dominant or only LatAm market. Both require a commercial agreement and custom pricing negotiation. Neither supports self-serve onboarding for production payouts as of October 2026.
Can I use Stripe to pay contractors in Brazil or Mexico via local rails?
Stripe supports payouts in Brazil and Mexico through its Connect product, but its PIX and SPEI coverage depends on the recipient’s bank and Stripe’s local banking partners in each market. Stripe does not disclose its specific PIX or SPEI settlement speed on its public pricing page. For platforms where local rail speed and cost optimization are priorities, Stripe is generally outperformed by regional specialists like dLocal or EBANX on LatAm-specific payout flows.
How much does it cost to send a payout to a LatAm bank account via API?
Most enterprise LatAm payout providers, including dLocal, EBANX, and Thunes, do not publish pricing publicly as of October 2026. Cost structures typically include a per-transaction fee plus an FX spread on the currency conversion. The spread on BRL and MXN can range from under 1% at high volumes to over 2.5% at lower volumes or with providers that do not disclose their markup. Request itemized fee breakdowns, including the FX spread, before signing any contract.
What is the difference between PIX and SPEI?
PIX is Brazil’s instant payment infrastructure operated by the Banco Central do Brasil. It settles 24 hours a day, seven days a week, including holidays. SPEI is Mexico’s interbank electronic payment system operated by Banco de México, which clears in minutes and operates during banking hours on business days. Both are direct local rails that bypass correspondent banking, but PIX offers broader 24/7 availability and supports a wider range of payee identifiers including phone numbers and email addresses as keys.
Is Payoneer a good option for paying LatAm contractors?
Payoneer works well for platforms paying freelancers or contractors who are already on the Payoneer network or willing to create an account. The key advantage is that Payoneer handles KYC on the recipient side, which reduces compliance burden for the paying platform. The trade-off is that recipients must withdraw from Payoneer to their local bank account rather than receiving funds directly, adding a step. For platforms where contractor experience matters and most recipients are already global freelancers, Payoneer is a practical choice.
What is Conduit and how does it differ from dLocal for LatAm payouts?
Conduit is an API-first payout provider that settles outbound payments in USD or stablecoins on the sending side and delivers to local bank accounts in Brazil, Mexico, and Colombia via local rails on the receiving side. dLocal settles in the source currency through a traditional banking infrastructure and manages currency conversion internally. Conduit is better suited for platforms already operating in a stablecoin or USD-native treasury model. dLocal is better for platforms that need broader LatAm coverage beyond three countries and have enterprise-level volume.
How long does a LatAm payout take to settle?
Settlement speed depends on the provider’s local liquidity and the rail. PIX payouts from providers with in-country BRL liquidity can arrive in the recipient’s account within seconds of API submission. SPEI payouts typically clear in minutes during Mexican banking hours. The delay most platforms experience comes not from the rail itself but from the provider’s treasury process of converting USD to local currency, which can add hours or a full business day if the provider does not maintain a standing local float.
Do I need separate integrations for Brazil and Mexico payouts, or can one API cover both?
dLocal, Thunes, Rapyd, and Mural all offer a single API that covers both Brazil and Mexico alongside other LatAm countries. This is one of their primary value propositions compared to building direct integrations with Brazilian and Mexican payment processors separately. A direct integration with a local Brazilian bank for PIX and a separate integration with a Mexican banking partner for SPEI would give you lower costs at very high volume but require two compliance relationships, two reconciliation streams, and two onboarding processes.
The Real Decision Point for US Platforms Expanding Into LatAm
The practical decision for most US platforms is not which provider has the best technology. PIX and SPEI connectivity is table stakes among the providers listed here. The real differentiators are liquidity depth, compliance posture, and how well the provider’s commercial model fits your volume. At under $500,000 per month in LatAm payouts, Payoneer or Rapyd often make more sense than dLocal simply because the onboarding and minimum volume requirements are more accessible. Above that threshold, the economics of negotiating direct FX spreads with dLocal or EBANX become compelling.
The stablecoin-to-local-rail path via Conduit or Mural is worth serious consideration if your company is already operating a stablecoin treasury or using USDC for other payment flows. The settlement architecture is genuinely different, and for the right platform it removes a currency conversion step on the sending side. For a broader view of how this infrastructure fits into a cross-border payout stack, the FintechSpecs guide to cross-border payout APIs for US platforms covers multi-region strategy in more depth.
The one consistent mistake to avoid is treating country coverage as the final evaluation criteria. A provider that lists 20 LatAm countries on their website but routes through correspondent banks in 15 of them delivers a materially worse outcome than a provider with direct connectivity in only five. Ask every vendor two questions before shortlisting: how do you fund your local liquidity in Brazil and Mexico, and what is your average settlement time on PIX and SPEI payouts. Those two answers tell you more than any feature matrix.
