Local payment methods in Latin America: PIX, SPEI and boleto

A corporate buyer in Mexico approves a foreign software purchase. The price arrives in dollars, their finance team runs on pesos, and the charge on an international card comes back declined. The sale dies at checkout, not in the product. For ISVs (Independent Software Vendors, software companies that sell their product to other businesses), each Latin American market drains the funnel through a different rail, and the vendor that ignores the local instrument loses the subscription before the software ever reaches evaluation. This guide is the country-by-country map of that rail and the local acquiring layer underneath it.

Before the map, one boundary that avoids confusion. This guide covers the local payment method and local acquiring: which rail the buyer pays through and how the transaction is matched and settled inside the country. The decision of who carries the tax role for the sale, the merchant of record, is a separate discussion and appears in merchant of record: how to choose. A vendor can accept a local payment method without being the merchant of record, and can be the merchant of record without offering the rail the buyer recognizes. The two decisions are independent.

One method caveat applies throughout. The regulatory and acquiring analysis of Latin American markets outside Brazil is preliminary and was not verified against each country's primary regulation. Every claim about SPEI, PSE, PIX, local cards and the acquiring layer is attributed to the corresponding official source (Banco de México, the Central Bank of Brazil, among others) and must be confirmed against the current rule before any operational or contractual decision.

Why local payment methods decide ISV conversion in Latin America

Local payment methods decide conversion because the Latin American corporate buyer pays through the instrument their finance team already operates, not the one the foreign vendor prefers. A dollar charge on an international card forces currency conversion, internal approval and a foreign-currency expense that freezes the budget. The domestic rail removes that friction.

The common reading treats a local payment method as a checkout detail. It is not. It is the condition for the order to exist. The buyer who cannot find a boleto or PIX may simply not buy, without opening a support ticket, and the ISV never learns how many sales it lost to a missing instrument.

The scale of the problem is well known in the market. The ABES study with IDC on the Brazilian software market records that software and services spending in the country accounts for roughly 1.5% of the global total (2024 edition), which gives a sense of the corporate volume crossing a border and facing the local instrument decision. The vendor that arrives with the right rail competes; the one that arrives with a dollar card fights over a smaller slice.

Worth separating two effects that are usually treated as one. The first is conversion: the local instrument gets the buyer to complete the purchase. The second is the cost of reaching it: accepting the instrument, matching the transaction and settling in local currency requires a structure in the country. The map below covers the first; the acquiring section covers the second.

The country-by-country map of the local instrument

Each Latin American market has a dominant rail, and the international vendor selling software has to offer what that country's finance team recognizes. Brazil runs on PIX and boleto with installments on cards; Mexico on SPEI and cards; Colombia on PSE; Chile on local cards, with Redcompra debit; Argentina on boleto and wallets. The table below summarizes the decision by country, as a preliminary analysis of markets outside Brazil.

Brazil is the most instructive case, because it offers three rails at once. PIX settles in seconds and became the standard transfer method, with the operational discipline that the Central Bank of Brazil documents in the rulebook for the arrangement, a preliminary analysis that does not replace the current rule. Boleto reaches the buyer who does not use a corporate card and depends on bank clearing. The installment card, in up to 12 payments for consumers, serves the larger purchase that finance prefers to spread across cash flow, even though the installment habit in B2B is smaller than in retail. Offering only one of the three leaves two of every three buyers outside.

Mexico and Colombia expose a similar point. The SPEI rules of the Banco de México require the sending participant to submit the transfer order within 30 seconds of informing the client of approval, a duty set out in Circular 17/2010, numeral 3.3, subsection a, since superseded by the system's current rules. That is a submission obligation, not a generic settlement deadline, and the current rule must be confirmed with Banxico before any operational use. Colombia solves the same problem with a different design, through PSE, a single-transaction online bank debit triggered by a button on the vendor's screen and authenticated by the buyer on every payment, with no stored mandate. In both cases, the ISV that accepts only international cards loses the purchase that the local finance team releases through a domestic rail.

In Chile and Argentina, the reading shifts from instrument to operation. Chile combines local cards, with credit and Redcompra debit, both card rails operated by domestic acquiring, so coverage depends on the local acquirer, not on an international scheme. Argentina has boleto as its clearing instrument and digital wallets gaining ground, and residual taxes on foreign card purchases plus currency rules for companies still add friction, but the currency controls were substantially dismantled from 2025. The vendor that enters with the same Miami billing across the region treats five markets as if they were one, and loses in each for the wrong reason.

How local acquiring supports the domestic rail

Local acquiring is the infrastructure that accepts the instrument in the country, matches the transaction with the right network and settles in local currency. It has two halves: matching, which routes the payment to the correct domestic acquirer, and settlement, which converts and makes the amount available. Without that layer, the local payment method does not exist for the buyer. The matching and settlement design described here is a preliminary analysis of the operation, not an exhaustive description of each market's regulation.

The direct path rarely delivers both halves. A foreign ISV that accepts PIX for a Brazilian client usually has matching without settlement, or an acquirer in one market with no coverage in the others. Opening a tax entity in each country solves settlement at the cost of a corporate, accounting and regulatory structure per market, one that rarely pays for itself before the operation gains volume.

The decision point is the routing design. The orchestration layer decides which rail a transaction takes after acceptance, and it connects directly to acquiring coverage: a rail enabled at checkout only converts if there is matching and settlement on the other side. The reader comparing that layer finds the design in payment orchestration: the layer above the gateway, and the next step, converting and settling the amount already accepted, is in cross-border settlement models.

This is where coverage through an agreement beats coverage through your own entity. Nexforce Marketplace operates local acquiring in every Latin American market, with the instrument each buyer recognizes, and the international vendor reaches that rail without opening an entity in the country. The ISV keeps the contract and program standards it already uses, receives up front, and does not carry the matching and settlement operation of each market. That is the point that separates the vendor selling across the region from the one selling only in Brazil.

What it costs to skip the local instrument

The cost of skipping the local payment method shows up in two accounts: the conversion lost and the cost of entering another way. The lost conversion is silent, because the sale that fails to close for lack of a boleto or a PSE does not produce an error, it produces abandonment. The cost of entering alone is explicit, and it lives in the structure per country.

The first number is abandonment. The buyer who sees a dollar price at checkout may need currency conversion, an internal budget line and a tax justification, steps that stretch the cycle past the tolerance of the purchase. The sale is lost not in the product but in the approval no one can push through. Each market declines for a different instrument, and the full pattern only appears on the country map.

The second number is the cost of building coverage. The alternative to the integrated rail is opening a local operation, with an entity, accounting and a regulatory obligation in each market. The vendor that does this pays for fixed infrastructure against volume that starts out variable. The vendor that stays on the international card pays in conversion. Both routes have a cost, and the mistake is not measuring both.

There is also a recurrence cost. Software is a subscription, and the charge repeats every month. In Brazil, PIX Automático is the instrument designed for recurring debit, under the rules of the Central Bank of Brazil, a preliminary analysis subject to the current rule, and the vendor that needs to keep the subscription active finds the mechanism in PIX Automático: recurring payments for SaaS. The absence of the recurrence rail does not cost one sale, it costs the entire base month after month.

One caveat applies to Colombia. PSE is a single-transaction debit, authenticated by the buyer, and it does not carry a subscription; Colombian recurrence requires a tokenized card or a direct-debit mandate at the bank level, not PSE.

The sequence to cover local payment methods in each market

The sequence below assumes that the local instrument is conversion infrastructure, not a checkout item added at the end. The order matters because each step depends on the previous one, and the vendor that reverses the logic buys coverage before knowing which market sustains the volume.

1. Map which Latin American markets already have buyers for the product and which instrument dominates each one, starting with the five on the map above.
2. Define, for each market, whether the charge needs recurrence, a one-time payment or installments, because the answer changes the instrument and the settlement design.
3. Choose the routing design that connects the checkout instrument to local acquiring, to avoid an enabled rail with no matching and settlement behind it.
4. Decide between coverage through your own structures and integrated coverage, comparing the fixed cost of an entity per country against expected volume.
5. Align the vendor's reception with the buyer's charge, so the ISV receives without carrying the receivable of each market.
6. Measure conversion by market after launch, because abandonment from a missing instrument does not show up in an error log.

The sixth step is usually the most neglected. Without measurement by market, the vendor cannot tell the sale that failed on price from the sale that failed for lack of a boleto. Both show up as the same decline at the end of the quarter, and only one of them is fixed by offering the local rail.

What the international ISV has to decide first

The decision that precedes all the others is not which instrument to offer, but which channel reaches the buyer in each market. The international vendor has two paths: operate local distribution and billing on its own, with the per-country structure that requires, or reach a channel that already operates the local rail and delivers the buyer on the instrument they recognize.

The first path charges in structure and time. The vendor that chooses to operate alone carries entity, acquiring and compliance in each market, and that bill grows with the number of markets. The second charges in a fee and keeps the operation lean. Nexforce Marketplace is the channel on the second path: the international ISV sells in Latin America through local infrastructure, on the instrument each market uses, without opening a foreign tax entity and at no cost for the ISV to enter. The buyer pays in PIX, boleto or local card depending on the country, and the vendor receives without carrying the receivable.

The choice between the two paths depends on volume and the speed intended per market, and the honest answer is that it changes with stage. Early on, integrated coverage wins on fixed cost. At scale, your own structure is justified only where volume is high and stable. Whoever treats the region's five markets as one is deciding in the dark, because each one drains the funnel through a different rail.

Frequently asked questions about local payments in Latin America

What is a local payment method in Latin America? It is the instrument buyers in that country use every day, such as PIX and boleto in Brazil, SPEI in Mexico, PSE in Colombia, local cards with Redcompra debit in Chile, boleto and wallets in Argentina. Offering it is the condition for the corporate buyer to complete the purchase without currency conversion or foreign-currency approval.

Why is accepting international cards not enough? Because much of the region's corporate payment flow runs through a domestic rail. Local finance releases the purchase through PIX, boleto, SPEI or PSE, and a dollar card requires conversion, budget and justification that stretch the cycle. The vendor that accepts only cards removes those buyers from the funnel.

What is local acquiring and why does it matter to the ISV? It is the infrastructure that accepts the instrument in the country, matches the transaction with the correct acquirer in the matching step and settles the amount in local currency in settlement. Without both halves, the instrument appears at checkout but does not convert, because there is no domestic rail to process the payment.

Does the international ISV have to open a tax entity in each Latin American country? Not necessarily. Coverage through your own entity costs a corporate, accounting and regulatory structure per market, and it rarely pays for itself before volume. A channel that already operates local acquiring in every market, such as Nexforce Marketplace, delivers the same rail without requiring an entity abroad.

How does Nexforce Marketplace cover the local payment method for the ISV? The international vendor sells through Nexforce's local infrastructure, with the instrument each market recognizes and reception without carrying the receivable of each market. The ISV keeps its own contract and program standards, and the buyer pays in PIX, boleto or local card depending on the country.

References and Further Reading

• Central Bank of Brazil, PIX and PIX Automático, official documentation at bcb.gov.br (preliminary analysis; confirm the current rule).
• Banco de México, Reglas del Sistema de Pagos Electrónicos Interbancarios (SPEI), Circular 17/2010, numeral 3.3, subsection a, superseded by current rules, at banxico.org.mx (preliminary analysis).
• ABES/IDC, Mercado Brasileiro de Software, 2024 edition, abes.org.br.
• Local currency payments: selling SaaS in Latin America
• How to sell SaaS in Latin America: the international ISV map

Where to go next

The local payment method is not a checkout item, it is the conversion infrastructure of the international vendor in each Latin American market. The ISV that treats the five markets as one, with the same dollar billing, loses the sale before the product reaches evaluation. What decides conversion is offering the rail the buyer recognizes, with local acquiring behind it.

The practical decision comes down to building that coverage on your own, with the per-country structure it requires, or reaching a channel that already operates local payment methods across the region. Nexforce Marketplace is that channel for the international ISV that wants to sell in Latin America: a local instrument in each market, reception without carrying the receivable, and no entry cost for the vendor. Details of the model are at nexforce.ai/marketplace.