Cross-Border Payments in Latin America: A B2B SaaS Guide
Cross-border payments are the single largest source of revenue leakage for B2B SaaS companies selling into Latin America. Between 20% and 40% of the transaction value evaporates before the customer even notices (aggregated data from Nexforce Marketplace clients, 2025-2026). The loss is not in the product price. It lives in payment friction: predatory FX spreads, credit card rejections, poorly structured taxes, and the absence of local payment methods. This guide maps the infrastructure decisions that prevent the bleed.
What are cross-border payments and why does B2B SaaS suffer the most?
Cross-border payments are transactions where buyer and seller operate in different countries, each under distinct fiscal and regulatory jurisdictions. The buyer pays in local currency. The seller receives in its operating currency. Between them, multiple intermediaries take a cut: the card issuer, the acquirer, the card network, the correspondent bank, the FX platform, and the payment gateway.
B2B SaaS suffers more than B2C because the tickets are large (annual contracts from USD 10,000 to USD 500,000), the decision cycle is long, and a payment rejection at contract closing is a terminal event. An ecommerce store can lose a USD 30 sale and survive. A B2B seller that loses an USD 80,000 renewal because the payment failed on the due date gets no second chance.
The B2B SaaS payment architecture was designed for mature markets. International credit card as the sole method, dollar-denominated billing, and a gateway like Stripe solve the problem in the United States and Europe. Latin America breaks every one of those assumptions.
See also: Why global SaaS loses money in Latin America without realizing it
How does B2B cross-border payment infrastructure work?
A typical B2B SaaS cross-border transaction crosses six layers before the net amount reaches the seller:
-
Payment initiation: the buyer enters payment details (credit card, boleto, Pix, wire transfer) at a checkout or receives a digital invoice.
-
Payment gateway: the seller's first interface. Captures, tokenizes, and routes the transaction. Stripe, Adyen, dLocal, and EBANX are gateways with Latin American presence.
-
Local acquirer: processes the transaction in the buyer's country. Without a local acquirer, the transaction is flagged as international by the card issuer, which spikes rejection rates and costs.
-
Foreign exchange (FX): the local-currency amount (BRL, MXN, COP) must be converted to the seller's currency (USD, EUR). The applied exchange rate is not the interbank rate. It includes the bank spread, the card network spread, and the gateway margin.
-
Cross-border settlement: the converted amount travels between jurisdictions. Correspondent banks charge wire transfer fees. Settlement can take 2 to 7 business days.
-
Fiscal and regulatory compliance: each country imposes its own rules. In Brazil, IOF tax on international transactions applies at every stage. Correct fiscal structuring determines whether the customer pays tax once or three times.
Each layer multiplies the friction. The customer gets a poor experience. The seller gets an invisible discount on gross revenue.
What are the main payment bottlenecks in Latin America?
The bottlenecks are not peripheral. They are structural. Each reduces cross-border revenue independently. They compound.
1. International credit card rejection
Approval rates for Latin American-issued cards in cross-border transactions are 30% to 50% lower than domestic transactions, according to the EBANX Beyond Borders 2025 report. Brazilian, Mexican, and Colombian issuing banks block international transactions by default as an anti-fraud mechanism. The buyer must manually enable the function in their banking app, a step many abandon.
For a B2B SaaS seller, every checkout authorization failure is a lead that does not convert. There is no effective automatic retry without local routing.
See also: Payment gateways in Latin America: a full comparison
2. Compounded FX spread
The cumulative FX spread on a typical cross-border transaction can reach 6% of the sale value. The issuing bank applies a spread. The card network applies another. The gateway applies a third. Each layer charges between 1% and 2.5% on the exchange, and the compounded total is opaque to the seller.
A USD 120,000 sale loses roughly USD 7,200 to cumulative FX spread alone, before taxes.
3. Taxes on international transactions
Brazil taxes cross-border transactions with IOF of up to 6.38% when paid by credit card, per current Banco Central do Brasil regulation (2026). Colombia applies withholding tax on payments to foreign entities. Mexico requires a specific fiscal receipt (CFDI) to deduct foreign software expenses.
Without correct fiscal structuring, the customer pays more tax than necessary and the seller loses competitiveness. In some cases, the tax burden makes foreign software more expensive than inferior local alternatives.
See also: Cross-border SaaS taxation in Brazil: a fiscal guide
4. Absence of local payment methods
Credit cards cover less than 30% of B2B transactions in Latin America. The rest use boleto bancario (Brazil), local bank transfers (SPEI in Mexico, PSE in Colombia), Pix (Brazil), and direct debit. A gateway that does not accept local methods excludes 70% of enterprise buyers.
Pix, in particular, is already the most used payment method in Brazil for mid-ticket B2B transactions. Febraban data (2025) shows B2B transaction volume via Pix grew over 80% in 2024, consolidating as the preferred method for Brazilian companies paying software vendors. It is instant, incurs no additional cost beyond standard TED-level taxation, and provides full fiscal traceability.
See also: Pix for B2B: the definitive guide for SaaS companies
5. Settlement time and cash flow
A cross-border transaction via international credit card takes 5 to 15 business days to settle in the seller's account. With boleto or wire transfer, the timeline is longer. For a B2B SaaS with customers paying quarterly or annual subscriptions, this cash flow mismatch pressures working capital.
Types of cross-border payment infrastructure for B2B SaaS
The choice of payment architecture determines how much cross-border revenue reaches the seller and how many buyers can actually pay.
| Model | How it works | Typical cost (as % of revenue) | Approval rate in LatAm | Best for |
|---|---|---|---|---|
| Pure international gateway (Stripe, Adyen) | Payment processed as an international transaction. Seller's currency. No local acquirer. | 3% to 5% (including FX) | 50% to 70% | Small tickets, customers with active international cards |
| Gateway with local acquirer (dLocal, EBANX) | Processing via local acquirer. Buyer's currency. Backend FX conversion. Local methods. | 2% to 4% (including FX) | 85% to 95% | Mid-sized tickets, multiple LatAm markets, conversion priority |
| Merchant of Record (MoR) | MoR assumes the transaction fiscally. Invoices in the buyer's country, collects local taxes, issues receipt. Pays the seller in USD. | 5% to 8% (includes taxes) | 90% to 98% | High-ticket contracts, operations requiring full fiscal compliance and local invoicing |
| Orchestration layer (Nexforce Marketplace) | A single integration. Routes payment through the optimal local rail. Structures the transaction fiscally. Settles in USD to the seller's account. | Variable by volume and geography | 90% to 98% | B2B SaaS companies with recurring contracts above USD 50,000/year |
The pure international model is the easiest to implement. It also leaks the most revenue. The MoR model is the most thorough for compliance. And the most expensive if used as the only layer. The orchestration layer solves the trade-off: one integration that activates the right local rail by country and ticket size, without multiplying contracts across different gateways.
See also: Merchant of Record vs Payment Orchestration: which one to choose?
How to choose the right payment architecture for B2B SaaS
The decision follows five criteria. The order matters: the fourth depends on the third, which depends on the second.
1. Cross-border contract volume and average ticket.
For contracts below USD 10,000/year, an international gateway with dollar-denominated checkout is sufficient. Friction exists, but the cost of more sophisticated infrastructure does not pay for itself. Starting at USD 50,000/year, each percentage point lost to FX spread and rejection represents thousands of dollars. Investment in a local acquirer or orchestration layer is justified.
2. Target countries and regulatory complexity.
If the SaaS sells only to Brazil, a gateway with a local Brazilian acquirer solves the problem. If it sells to Brazil, Mexico, Colombia, Chile, and Argentina, each country demands a different acquirer, settlement method, and fiscal treatment. Multiplying gateway contracts by country is operationally unviable. The orchestration layer becomes mandatory.
3. Fiscal structure of the operation.
A company with a legal entity in each country can invoice locally and pay taxes in each jurisdiction. A company without a local entity needs a Merchant of Record or a service import structure the customer can deduct. The fiscal architecture defines which payment model is legally viable, not just economically preferable.
4. The customer's need for a local tax receipt.
In Brazil, B2B companies require a nota fiscal to deduct software expenses as operational costs. Without it, the customer pays for the software with taxable profit, which eliminates much of the tool's economic advantage. If the SaaS does not issue a Brazilian nota fiscal, it loses the customer to a competitor that does, regardless of product quality.
5. Projected scale for the next 18 months.
Payment architecture is an infrastructure decision. Migrating from a pure international gateway to MoR or orchestration demands integration rework and renegotiation of customer contracts. If Latin American expansion is structural, choose the final architecture from day one. The cost of anticipation is lower than the cost of migration.
What does it cost to run cross-border payments and where does the money disappear?
The total cost of a typical B2B cross-border transaction breaks down into five categories. The PCMI Cross-Border Payments report (2025) estimates the cross-border payments market in Latin America surpassed USD 200 billion in 2024, with an average loss of 3% to 8% in friction for B2B transactions. A USD 100,000/year sale loses between USD 5,000 and USD 20,000 in payment friction, depending on the chosen architecture.
Processing fee (gateway + acquirer): 1.5% to 3.5% on the transaction value. International gateways charge more for cross-border risk. Local acquirers reduce the fee because the transaction is treated as domestic.
FX spread: 1% to 6% on the converted amount. The interbank rate is the benchmark. Each intermediary (bank, card network, gateway) adds its margin. The compounded FX spread is the largest source of invisible loss.
Taxes (IOF, withholding, VAT): range from 0% to 38% depending on the country, payment method, and transaction fiscal structure. Correct structuring can reduce the tax burden by 15 to 25 percentage points.
Settlement fees (wire, SWIFT, TED): USD 15 to USD 50 per transaction. Relevant for small tickets. For annual contracts above USD 50,000, they dilute to a negligible percentage.
Rejection and hidden churn: the invisible cost. Every rejected payment represents a customer who either gives up or delays. For a B2B SaaS with a 60-day sales cycle, losing a contract at the last step because the payment failed is a cost no gateway dashboard reports.
Common mistakes in B2B international payment strategy
Treating cross-border payments as a gateway commodity.
The root mistake. Gateways were not designed for high-ticket B2B transactions across multiple jurisdictions. Stripe is excellent at what it does. It was not built to process a BRL 80,000 boleto with a nota fiscal. Using the wrong tool is not an integration problem. It is an architecture problem.
Billing in dollars and ignoring the buyer's local currency.
The Brazilian buyer sees a USD price, mentally converts it to BRL at a rate they do not control, adds the IOF their bank will charge, and decides the currency risk is not worth it. The purchase decision dies before reaching checkout. Offering a price in local currency reduces abandonment from FX friction by up to 40%.
Operating without a local acquirer in relevant markets.
A transaction processed in the United States or Europe and presented to a Brazilian issuer is flagged as international. Brazilian banks block international transactions by default. Without local processing, the seller systematically loses customers who have the ability to pay but whose bank rejected the transaction.
Assuming a legal entity solves the fiscal problem.
Opening an entity in Brazil solves invoicing. It does not solve transfer pricing structure, the taxation of profit repatriation, or compliance with each country's rules. The legal entity is a prerequisite, not the full solution.
Ignoring Pix and local transfers as a B2B method.
Pix is already the preferred payment method for B2B transactions in Brazil. Transfers like SPEI in Mexico and PSE in Colombia are used for software payments by companies that do not operate with credit cards. Excluding these methods is excluding the majority of buyers.
FAQ
What is the difference between a payment gateway and a Merchant of Record?
The gateway processes the technical transaction. The MoR assumes the transaction legally: invoices the customer in local currency, collects taxes in the buyer's country, issues the fiscal document, and remits the net amount to the seller. The gateway is a pipe. The MoR is the legal seller.
Do I need a legal entity in every Latin American country to sell B2B SaaS?
No. A Merchant of Record or an orchestration layer that structures the service import allows you to operate without a local entity. Your own entity is only necessary when volume or fiscal strategy justifies the cost of maintaining a local operation.
What impacts cross-border conversion more: price or payment method?
Payment method. The buyer decides on price before reaching checkout. At checkout, what makes them abandon is a method they do not have (international credit card) or a surprise cost (IOF, FX spread) they did not anticipate.
How much does it cost to implement a payment orchestration layer?
It depends on volume and the number of countries. Technical integration takes days, not months, because the orchestration layer exposes a single API regardless of how many gateways and acquirers run on the backend. The main cost is the per-transaction fee, which ranges from 1% to 4% depending on geography and the payment method used.
Is it worth accepting cryptocurrency for B2B cross-border payments?
Not for B2B SaaS in Latin America in 2026. Currency volatility adds operational risk, fiscal compliance with crypto assets is uncertain across most Latin American jurisdictions, and B2B companies do not pay software vendors with crypto. Stablecoins solve the volatility but do not solve the tax receipt.
What changes with Drex (Brazil's digital real) for B2B cross-border payments?
Drex is a CBDC (central bank digital currency) in pilot phase. Once operational, it will enable programmable settlement of B2B cross-border transactions with near-zero cost and native fiscal traceability. For B2B SaaS operating in Brazil, Drex has the potential to eliminate FX spread and settlement delays for real-denominated transactions. It is not operational reality in 2026, but it is the most concrete signal that B2B payment infrastructure in Latin America is under rapid transformation.
The layer that removes friction without multiplying complexity
Every bottleneck described in this guide has an isolated technical solution. The problem is orchestrating all of them simultaneously. A local gateway solves card rejection. A MoR solves the tax receipt. An FX structure solves the spread. Contracting each piece separately is operationally unviable: contracts with different gateways by country, divergent settlement flows, fragmented fiscal reports.
Nexforce Marketplace operates as the orchestration layer for B2B SaaS cross-border payments in Latin America. A single integration activates the optimal local payment rail by country, ticket size, and the buyer's fiscal profile. The Marketplace structures the transaction to minimize the tax burden, processes the payment in the local method the customer prefers, and settles the amount in USD to the seller's account. The tax receipt issues in the same flow.
The result: the B2B SaaS seller does not have to choose between integration simplicity and local payment coverage. The orchestration layer delivers both. The friction disappears. Cross-border revenue stops being an accounting loss and becomes an expansion lever.
References and Further Reading
- EBANX Beyond Borders 2025: cross-border payment trends in Latin America
- Febraban 2025: B2B Pix transaction data in Brazil
- PCMI Cross-Border Payments 2025: cross-border payment market analysis
- Banco Central do Brasil 2026: IOF and international transaction regulation