B2B Payment Processing in Latin America: Infrastructure Guide

Most ISVs (Independent Software Vendors, companies that sell their software to other businesses) entering Latin America model revenue without modeling processing. They project pricing, positioning, and sales headcount. They ignore the layer that turns a signed contract into cash in the bank.
The mistake is expensive. A B2B cross-border transaction processed via international card without local acquiring loses 20 to 30 percentage points of approval versus domestic processing. A USD 50,000 invoice settled via traditional wire transfer faces 2 to 4 business days of FX float. A checkout that does not offer PIX in Brazil or PSE in Colombia simply does not close.
B2B payment processing in Latin America is an infrastructure problem. Not a financial architecture problem. This guide covers the layer the ISV touches: gateways, PSPs, approval rates, routing logic, and the payment methods that determine whether the sale goes through or fails.
What Is B2B Payment Processing Infrastructure?
B2B payment processing infrastructure is the set of systems that executes a commercial transaction from the moment the buyer authorizes payment to the moment the supplier receives settled funds. It includes gateways, payment service providers (PSPs), local acquirers, card networks, real-time payment systems (such as PIX and SPEI), and transaction routing mechanisms. For a global ISV selling SaaS or services in Latin America, processing infrastructure is the difference between a sale that closes and one that fails at checkout.
The critical distinction: the cross-border payments guide covers architecture -- currency corridors, tax structure, Merchant of Record models. Processing infrastructure covers operations: which systems process the transaction, at what approval rate, in what timeframe, and through which route.
How Does B2B Payment Processing Work in Latin America?
A cross-border B2B transaction in Latin America follows a five-stage flow. At each stage, an infrastructure decision determines the transaction outcome.
Stage 1: Capture. The buyer enters payment details at the ISV's checkout. If the checkout accepts only international cards, 30% to 40% of transactions are declined before reaching the issuer. Local networks such as Elo and Hipercard (Brazil) or Carnet (Mexico) do not run on international rails. A checkout that integrates local methods eliminates this loss at the source.
Stage 2: Routing. The gateway decides where to send the transaction. The routing decision defines both approval and cost: processing via local acquiring reduces decline rates by up to 30 percentage points. Processing via cross-border acquiring is simpler to integrate but sacrifices approval. Intelligent routing -- multi-acquirer, with automatic fallback -- is the standard for platforms operating at scale in the region.
Stage 3: Authorization. The card issuer (or the bank in the case of PIX and SPEI) approves or declines. The approval rate depends on three factors: whether the acquiring is local, whether the card BIN has a positive history in the region, and whether the amount fits the buyer's spending profile. For PIX and SPEI, authorization is instant and irrevocable. There is no chargeback.
Stage 4: Settlement. Funds leave the buyer's account and enter the settlement chain. Cross-border cards settle from T+2 to T+7. PIX and SPEI settle in real time, 24/7. The timing difference directly affects the ISV's working capital.
Stage 5: Payout. The ISV receives funds in its preferred currency. If the PSP operates as a Merchant of Record, the ISV receives a single consolidated payout, with tax documentation already processed. If it operates as a pure gateway, the ISV receives funds on its own and assumes the tax complexity.
Nexforce Marketplace operates across all five stages. Capture is local (PIX, boleto, domestic cards). Routing is native. Settlement is in BRL with locked-in FX rate. Payout reaches the ISV with an electronic invoice and a 9.25% PIS/COFINS tax credit for companies under Brazil's Lucro Real tax regime.
Gateways and PSPs in Latin America: Who Operates and Who Delivers
The B2B processing market in Latin America splits into three infrastructure categories. The ISV must decide which category -- or which combination -- supports its operation.
[IMAGEM TECNICA type: comparison-table title: B2B PSPs and Gateways in Latin America data: |
| PSP | LatAm Coverage | Local Acquiring | Native MoR | Native Local Methods | Best For |
|---|---|---|---|---|---|
| dLocal | 17 countries | Yes, via own licenses | Yes | PIX, SPEI, PSE, OXXO, Boleto, MODO, Yape | ISVs needing full coverage without a local entity |
| Adyen | Brazil, Mexico | Yes, in both markets | Via Adyen for Platforms | Local cards, PIX, SPEI | Marketplaces and platforms with B2B volume in the two largest markets |
| Stripe | Brazil (limited), Mexico (limited), Colombia (beta) | Partial | No | Cards only | ISVs invoicing via Stripe Billing with volume concentrated in mature markets |
| EBANX | 15+ countries | Yes, in Brazil | Yes, EBANX for Business | PIX, Boleto, SPEI, PSE, OXXO | ISVs with B2C or SME average ticket; B2B expansion underway |
| Kushki | 12+ countries | Yes, via unified API | Partial | Local cards, transfers, wallets | ISVs seeking a regional Stripe alternative with a standardized API |
| PayU | 7 countries | Yes, in key markets | Via PayU Enterprise | PSE, PIX, OXXO, local cards | ISVs focused on Colombia, Mexico, and Brazil |
| Nexforce Marketplace | Brazil (LatAm expansion) | Yes, local Brazil | Yes, native for software | PIX, boleto, local cards, installments | International ISVs selling SaaS in Brazil without a local entity |
| source: dLocal country pages (2025), EBANX, Adyen, Nexforce product reference | |||||
| language: en | |||||
| ] |
The operational difference that matters is not in the list of covered countries. It is in three dimensions that determine the transaction outcome.
Dimension 1: Local acquiring vs. cross-border. A PSP with local acquiring in Brazil processes domestic cards (Elo, Hipercard) directly on local rails. A PSP without local acquiring processes everything as a cross-border transaction and loses 20 to 30 percentage points of approval. For ISVs with a B2B ticket above USD 10,000, this difference represents revenue lost at the most expensive stage of the funnel: payment.
Dimension 2: Native MoR vs. pure gateway. A PSP with native Merchant of Record acts as the legal seller of the transaction: issues the invoice, withholds taxes, assumes regulatory responsibility. A pure gateway routes the transaction, but the ISV remains the legal seller and bears sole responsibility for tax obligations in each country. For international ISVs, the MoR eliminates the need to open a CNPJ in Brazil, an RFC in Mexico, or a RUT in Chile.
Dimension 3: Local method coverage. International cards cover less than 50% of digital B2B volume in Latin America. PIX already represents 51% of all payments in Brazil. PSE processes 34% of online purchases in Colombia. SPEI is the dominant real-time transfer rail in Mexico. A PSP that integrates only international cards is processing the minority of transactions.
Choosing a PSP for B2B processing in Latin America is, in practice, a decision about how much local infrastructure the ISV is willing to buy versus how much it is willing to outsource.
Approval Rates by Country: What the ISV Needs to Measure
Approval rates in Latin America are not a single regional number. They vary by country, payment method, and acquiring type. An ISV measuring an aggregate approval rate is looking at the wrong metric.
Brazil. PIX: effective approval of 100% (instant and irrevocable transaction, no chargeback mechanism). Domestic card with local acquiring: 75% to 90%. International card without local acquiring: 55% to 70%. Boleto: invoice generation near 100%, with default risk between 5% and 15% depending on buyer profile.
Mexico. SPEI: 100% approval (real-time interbank transfer). Debit card with local acquiring: 80% to 92%. International card without local acquiring: 60% to 75%. OXXO (cash voucher): invoice generation above 95%, but limited to tickets below USD 500.
Colombia. PSE: approval above 95% (authentication via bank login). Local card: 70% to 85%. Cross-border international card: 50% to 70%. Bre-B, launched in October 2025 as Colombia's PIX equivalent, should further increase real-time transfer approval rates.
Argentina. Currency volatility and capital controls make processing the region's most complex market. Local card in pesos: 65% to 80%. International card: highly variable, subject to declines for fraud suspicion and FX restrictions. MODO, the banking consortium's digital wallet, processes over 50% of Argentine e-commerce and operates with less friction than cards.
Chile. The region's highest banking penetration. Local card: 80% to 92%. Cross-border card: 70% to 85%. The gap is smaller than in other markets, but local acquiring still delivers a 10 to 15 percentage point gain.
Peru. Debit card: dominant in B2B. Yape, BCP's digital wallet with on-file integration since October 2025, grows as an alternative. Cross-border card: 65% to 80%.
The rule is consistent across all markets: transactions processed via local acquiring approve more, and transactions via real-time rails (PIX, SPEI, PSE, Bre-B) approve virtually every time. For the ISV, the infrastructure decision with the greatest revenue impact is not which PSP to contract. It is whether processing will be local or cross-border.
Transaction Routing: How Systems Decide Where to Process
Transaction routing is the logic that determines which acquirer, network, and method each payment will run through. In the North American or European market, routing is a solved problem: two or three acquirers cover 90% of volume. In Latin America, routing is the processing infrastructure's competitive differentiator.
Four routing architectures operate in the region:
1. Single acquirer. The transaction always goes to the same acquirer, regardless of card BIN, amount, or country. It is the simplest model to integrate and the most fragile: if the acquirer declines, the transaction dies. Stripe predominantly operates on this model in Latin America.
2. Multi-acquirer with fallback. The transaction is sent to the primary acquirer. If declined, it is resent to a secondary acquirer. Fallback recovers part of the transactions lost on the first attempt. dLocal and Adyen operate with multiple acquirers per market.
3. Payment-method routing. The transaction is routed based on the method the buyer selects. PIX goes directly to the SPI (Brazilian Central Bank's Instant Payment System). SPEI goes directly to Banco de México. An Elo card goes to a local acquirer that processes that network. A cross-border Visa card goes to the international acquirer. This model eliminates the bottleneck of sending all methods through a single rail.
4. AI-driven dynamic routing. Machine learning models trained on transaction data by market, BIN, and amount decide in real time which acquirer to send each transaction to. The model learns continuously: if Acquirer A has an 85% approval rate for Itau BINs on transactions above BRL 10,000, the engine routes those BINs to A. If B drops to 70%, the engine migrates traffic automatically. dLocal positioned AI-driven routing as a differentiator in its 2026 predictions.
For the ISV, AI-driven dynamic routing is the infrastructure that turns approval rate from a passive metric into an active revenue lever. A 5-percentage-point approval gain on a USD 1 million B2B sales operation represents USD 50,000 in revenue that static routing would have lost.
Local Payment Methods and Their Impact on B2B Processing
The Latin American B2B buyer does not pay like a North American or European buyer. A corporate credit card is not the default method. What closes the transaction is the method the buyer already uses daily.
PIX (Brazil). 177 million users, 51% of all payment volume in the country. For B2B, Pix Automático, launched in June 2025, enables recurring billing with pre-scheduled debits, solving the SaaS renewal problem. The transaction is instant, irrevocable, and chargeback-free. For the ISV, PIX means immediate receipt and zero dispute risk.
SPEI (Mexico). Banco de México's electronic interbank payment system. Real-time transfers, 24/7. For B2B, SPEI covers high-value transfers with immediate settlement. It is the dominant rail for business-to-business payments in Mexico.
PSE (Colombia). Pagos Seguros en Linea. The buyer is redirected to their bank's internet banking portal, authenticates the transaction, and the debit is processed in real time. It processes 34% of all online purchases in Colombia and over 95% of bank-transfer-based transactions. For Colombian B2B, it is the de facto method.
Boleto (Brazil). An offline method that generates a payment document cashable at banks, lottery shops, and apps. For B2B with clients operating on cash flow who prefer scheduled payment, boleto remains relevant, particularly for tickets between BRL 2,000 and BRL 20,000.
OXXO (Mexico). A cash voucher paid at over 22,000 convenience stores. Capped at tickets of approximately USD 500, it has restricted B2B application. Relevant for ISVs selling to Mexican micro and small businesses.
MODO (Argentina). The Argentine banking consortium's digital wallet. It processes over 50% of the country's e-commerce. For B2B in Argentina, it is the lowest-friction method in a high currency-volatility environment.
Bre-B (Colombia). Launched in October 2025 as Colombia's PIX equivalent. An interoperable real-time payment system across all banks. Still in the adoption phase, it should accelerate the migration from traditional bank transfers to instant rails.
The operational takeaway: a B2B checkout that only offers international credit cards is addressing less than half of Latin America's payment volume. Processing infrastructure that integrates local methods is not a competitive differentiator. It is the entry condition.
How to Choose Processing Infrastructure for Latin America
The processing infrastructure decision for ISVs selling B2B in Latin America follows five elimination criteria. If the first criterion is not met, the rest are irrelevant.
1. Local acquiring in target markets. Without local acquiring in Brazil and Mexico, the region's two largest markets, the ISV leaves 20 to 30 percentage points of card approval on the table. The question to ask a PSP is not "do you operate in Brazil" but "do you process via local Brazilian acquiring, with a direct connection to Elo and Hipercard rails?"
2. Native payment methods, not via third parties. The PSP must integrate PIX, SPEI, and PSE directly, through connections to central banks, not through an intermediary processor that adds latency and a point of failure. Local methods integrated via third parties lose the approval advantage that justifies their adoption.
3. Merchant of Record or gateway model. For ISVs without a local entity, MoR is mandatory. It solves invoicing, tax withholding, and regulatory compliance without requiring a CNPJ or its equivalent in each country. For ISVs with a local entity, a gateway may suffice, but demands in-house tax operations. Payment orchestration across multiple PSPs is the path for ISVs already operating with a local entity and seeking to optimize routing.
4. Dynamic or static routing. Static routing is acceptable for volumes below USD 100,000 per month. Above that, the difference between dynamic and static routing pays for the migration within one quarter, through approval gains.
5. Payout speed. PIX and SPEI settle in real time, but payout to the ISV depends on the PSP's structure. A PSP operating as MoR consolidates payments and pays out on T+1 or T+2. A gateway that settles per transaction can generate multiple daily credits -- useful for working capital, complex for accounting reconciliation.
Nexforce Marketplace operates with local acquiring in Brazil, native PIX and boleto integration, a MoR model with BRL invoicing, and consolidated payout. For international ISVs selling SaaS in Brazil, this infrastructure delivers local-processing approval rates without requiring the ISV to open a CNPJ, hire Brazilian accounting, or build an in-country tax operation.
Common Pitfalls in B2B Payment Processing in Latin America
ISVs entering Latin America commit four infrastructure errors consistently. These are premise errors, not execution errors.
Pitfall 1: Assuming integration with a global PSP solves Latin America. Stripe, Adyen, and PayPal operate in the region, but with partial coverage. Stripe lacks local acquiring in most Latin American markets. PayPal has low B2B adoption. Integration with a global PSP is necessary, but insufficient. The correct question is: does this PSP process locally in my three main Latin American markets?
Pitfall 2: Measuring aggregate approval rate. An aggregate approval rate hides variation by method and country. An ISV with 85% aggregate approval may have 95% on PIX in Brazil and 60% on cross-border cards in Mexico. The aggregate metric does not show where revenue is being lost.
Pitfall 3: Ignoring the invoice as part of infrastructure. In Brazil, a B2B transaction without an electronic invoice (NF-e) is not a completed transaction. It is a transaction pending regularization. The invoice is not an accessory document; it is part of the processing rail. A PSP that does not issue NF-e in BRL is delivering half the infrastructure.
Pitfall 4: Treating FX as an operational detail. The FX spread on cross-border transactions in Latin America ranges from 2% to 4%, above the 0.5% to 1% prevalent in developed corridors. A USD 100,000 invoice processed monthly loses USD 24,000 to USD 48,000 per year in spread alone. Locking in the exchange rate at the time of the transaction is not a convenience; it is margin protection.
FAQ: B2B Payment Processing in Latin America
Do I need a Brazilian CNPJ to process B2B payments locally?
No. A PSP operating as Merchant of Record processes the transaction as the legal seller, issuing invoices in its own name and forwarding funds to the ISV. The ISV does not need to open a CNPJ, hire accounting, or register with the Central Bank. Nexforce Marketplace operates on this model for international ISVs selling SaaS in Brazil.
What is the practical difference between a gateway and a PSP with local acquiring?
A gateway routes the transaction to an acquirer. A PSP with local acquiring is itself the acquirer, or has a direct connection to the domestic acquiring network. The practical difference: the gateway depends on third parties to approve the transaction; the PSP with local acquiring controls the full cycle and delivers a higher approval rate.
Does PIX replace credit cards for B2B in Brazil?
For medium and high-ticket B2B transactions, PIX is progressively replacing cards. It is instant, irrevocable, has no chargeback, and carries no interchange fee. Pix Automático solves recurring billing. What still keeps cards relevant is installment payments. 58% of retail transactions in Brazil use installments, and the B2B buyer expects the same flexibility.
Does processing B2B payments via boleto still make sense in 2026?
For tickets between BRL 2,000 and BRL 20,000 with cash-flow-driven clients, yes. Boleto allows the buyer to schedule payment within their financial cycle. The cost is settlement delay (T+1 to T+3) and default risk. For ISVs with monthly recurring revenue, Pix Automático is superior.
How much does it cost to build proprietary processing infrastructure in Latin America?
Opening a legal entity and obtaining a processing license in one Latin American country costs USD 50,000 to USD 200,000 in legal and regulatory expenses, with a 6-to-18-month timeline. The Merchant of Record model -- outsourcing infrastructure to a PSP already operating with local licenses -- eliminates that upfront investment and reduces time to market to weeks.
Nexforce Marketplace: Native Processing for Latin America
Nexforce Marketplace's processing infrastructure solves the Latin American equation in a single integration. The international ISV connects its checkout once and accesses local processing in Brazil with domestic acquiring, native methods, and integrated tax compliance.
What this means in practice:
Local capture. The checkout accepts PIX, boleto, and domestic cards, processed on Brazilian rails, with local-acquiring approval rates. No transaction loss from international card declines.
BRL invoicing. Every transaction generates a domestic NF-e (electronic invoice). The Brazilian buyer receives the tax document their accounting requires. The Nexforce invoice enables companies under Brazil's Lucro Real tax regime to recover a 9.25% PIS/COFINS credit, a fiscal benefit that direct importation rarely captures. Companies under the Lucro Presumido regime benefit from the locked-in FX rate, the BRL invoice, and operational simplification, without the tax credit.
FX rate lock. The exchange rate is fixed at the time of the transaction, eliminating exposure to BRL volatility. The spread is reduced compared to traditional cross-border processing.
Consolidated payout. The ISV receives funds in its preferred currency, with a consolidated payout and reconciliation report. No multiple daily credits. No accounting complexity.
For international ISVs selling SaaS in Latin America, Nexforce Marketplace delivers the processing infrastructure that turns payment approval from a bottleneck into a competitive advantage, without requiring a local entity, without minimum volume thresholds, and without the bureaucracy of building an in-country operation.
References and Further Reading
- dLocal: From local to interoperable, 5 predictions for payments in 2026
- dLocal: Payment methods and processors in Brazil
- dLocal: Payment methods and processors in Mexico
- dLocal: Colombia launches Bre-B, the new real-time payment system
- Cross-Border Payments in Latin America: SaaS B2B Guide
- Payment Orchestration: What It Is, Platforms, and How to Choose
- Nexforce Marketplace: Software & AI in Local Currency

Sell software in Latin Americawith no setup and saving 50%
Distribute your SaaS through the Nexforce platform scaling sales channels in a simple way
Run SimulationRelated articles

When to Use a Software Distribution Marketplace: Decision Guide
Decision guide: when to use a software distribution marketplace vs selling direct. Readiness signals, cost-benefit analysis, and ideal scenarios for ISVs.
Read more
Cloud Marketplace Guide for ISVs: AWS, Azure and Google Cloud
Complete guide for ISVs: listing mechanics, revenue share comparison, and GTM strategies for AWS, Azure, and GCP marketplaces.
Read more
Cloud Marketplace LatAm: Channels, Partners, and Compliance
Cloud marketplaces (AWS, Azure, GCP) in Latin America: distribution channels, local partners, tax compliance, and cost analysis for B2B software procurement.
Read more