EBANX Guide: Latin American Local Acquiring, Tax IDs, and Settlement Paths

EBANX Guide: Latin American Local Acquiring, Tax IDs, and Settlement Paths

Collecting in Latin America is easy to misread as a technology problem. Teams see many local payment methods sitting on local banks and local clearing institutions and conclude that one aggregating interface will solve it. What actually blocks overseas sellers is a different layer: local tax ID and invoice requirements. CPF and CNPJ in Brazil and RFC in Mexico are not optional fields in the payment flow; they are prerequisites for completing a lawful transaction locally. This guide works from that barrier and explains what a local acquirer does and does not take on, and how settlement paths and responsibility boundaries should be defined in the contract.

1. Where It Fits: Local Acquiring and Settlement in Latin America

1.1 The problem it solves

Payment structure in Latin America differs sharply from mature markets. In Brazil, bank slip methods and instant transfer methods have long carried a large share of volume, interwoven with card usage and instalment habits. Mexico shows a different structure, where cash networks and bank transfers take a meaningful share while cards remain mainstream but not exclusive. Behind these methods sit local banks and local clearing systems that an overseas team cannot easily connect to on its own.

The first value of a local acquirer is here: it holds local channels and local settlement paths, so an overseas seller does not have to build acquiring infrastructure locally. The second value sits in the tax ID and invoicing step, because a local acquirer is usually able to process transactions and issue invoices through a local entity, which is decisive for sellers without a local tax ID. EBANX, which started in Brazil with Latin America as its main market, sits exactly in this category, covering mainstream local methods with local acquiring and settlement.

1.2 What it is not

First, it is not your tax agent. What it can do and what it is willing to take on are defined by contract rather than by product documentation. Reading onboarding a local acquirer as transferring tax responsibility is the most expensive misreading in this field.

Second, it is not one integration for the whole region. Latin American countries differ widely in tax systems, payment method structure and regulatory requirements. What works in Brazil does not carry over to Mexico, and Mexican practice does not carry over to the Andean markets.

Third, it is not a global acquiring platform. Multi-region, multi-currency acquiring with unified online and offline management and multi-entity settlement belongs to a different product category. For the wider regional picture start with the Local Payment Methods by Region Guide.

2. Onboarding and Entity Requirements

2.1 What onboarding actually looks at

A foreign entity applying for Latin American local acquiring is reviewed on four things: how explainable the business model is, how verifiable the website and product are, expected volume and category risk, and what form of local identity or tax arrangement you can offer.

The first is the most underestimated. The reviewer has to judge what you sell, to whom, whether the refund policy is clear and whether a usable support channel exists, from a page a third party can reach. The second is examined more closely in Latin America, because local regulators pay closer attention to cross-border transactions, so whether material is structured directly affects the number of rounds. The third sets the pace of onboarding, since higher-risk categories need more explanation. The fourth is the core of this article and is covered in the next section.

2.2 Tax IDs and invoices: who carries what

This is the real barrier to collecting in Latin America. In Brazil the personal and legal entity tax numbers are CPF and CNPJ, and both transactions and invoices touch them. In Mexico, RFC is the core tax identifier. A seller without these simply gets stuck on local channels.

The value of a local acquirer is using a local entity and local settlement path to open that route. But opening the route is not transferring it. The responsibility boundary has to be confirmed item by item: who files tax, who issues invoices to end buyers, who responds when a buyer asks for an invoice, who receives tax enquiries, and how disputes and refunds offset for tax purposes. The answers depend on the contract structure, not on the provider's reputation.

The table below breaks the market, the method, the prerequisite and the bearer apart. Fill every cell before signing, and treat any cell you cannot fill as a risk point.

The value of this table is not in the answers but in forcing the questions out. Anything left vague in the contract becomes an incident at some point in operations. For the overall tax framework see the VAT and Sales Tax Compliance Guide, and for entity and account design see the Cross-Border Seller Entity and Account Structure Guide.

3. Integration and Account Structure

3.1 Account structure for local acquiring

The account structure for Latin American local acquiring is usually more complex than card acquiring, because one transaction runs along four lines at once: payment method, tax ID, invoice and settlement currency.

The payment method line decides what the buyer sees. The tax ID line decides whether the transaction is accepted by the local system. The invoice line decides whether the buyer gets compliant documentation. The settlement currency line decides in what form and under whose account name the money lands. When assessing the structure, confirm that these four lines can be configured separately rather than being bound into one bundle.

With a scheme such as EBANX, you should be able to draw the whole chain before integrating: in which market the buyer pays with which method, under which entity the transaction occurs, who issues the invoice, in which currency settlement reaches which of your accounts, and whether refunds return the same way or take another route. If the diagram cannot be drawn, reconciliation and tax filing will break later.

3.2 Three things the server must get right

Whichever acquirer you integrate, the server has to get three things right: idempotency, the state machine and reconciliation.

Idempotency means the same creation request arriving twice must not produce two payments. Webhooks from Latin American local methods are often delayed and can be delivered more than once, so a creation endpoint without an idempotency key easily produces double payments on one order. For patterns see the Payment Order Number and Idempotency Design Guide.

The state machine means created, awaiting payment, in progress, succeeded, failed, expired, refunding, refunded and partially refunded states must close properly. Bank slip and cash network methods confirm asynchronously and can sit in an intermediate state for a long time, so a poorly designed state machine produces a mass of pending orders.

Reconciliation means order records must match the settlement report line by line. The difficulty in Latin America is currency and entity: the settlement currency, the settling entity and your own bookkeeping entity may not be the same, and inconsistent rules are the most common source of operational incidents.

4. Core Capabilities and Market Coverage

4.1 What is covered is method types

When assessing Latin American local acquiring, do not ask how many payment methods are supported. Ask which of the lead methods in your target market are supported, and how deep that support goes.

The lead methods in Brazil are bank slip and instant transfer. The former depends on the buyer completing payment on the banking side with delayed confirmation, while the latter is closer to real time. Among Mexican lead methods, cash networks and bank transfers take a meaningful share, and cash methods have confirmation and refund paths very different from cards. The two families place very different demands on the state machine, support scripts and refund process.

Coverage should therefore be assessed at method level rather than country level. A provider doing deep work in Brazil tells you nothing about its performance in Mexico, and the reverse.

4.2 Three forms of settlement path

Latin American settlement paths fall into roughly three forms, each with different operational meaning.

The first is local currency settlement, where the transaction completes locally in local currency and settles in that currency into your local account. The money path is short, but it requires either a local account or the ability to accept local currency settlement through the provider. The second is cross-border settlement, where the transaction completes locally and funds are remitted in an agreed currency to your overseas account; the path is longer but the organisation is simpler. The third is a hybrid, with some markets on local settlement and others on cross-border.

The three forms affect cash flow and reconciliation very differently. For multi-currency pricing and settlement currency choices see the Multi-Currency Payment Account Guide. Before choosing, confirm which form your finance and tax teams can actually handle.

5. Fee Structure and Real Cost

5.1 Fee components

Fees for Latin American acquiring are not one number but a set of components.

Current rates and conditions belong to the official quote and the signed contract. Any percentage appearing in an article will go stale, and budgeting from old numbers is the most common error of all.

5.2 How to judge the real cost

Comparing headline rates side by side is the easiest mistake at this stage. The right method is to build a transaction mix that matches your business: the same payment method share, the same market distribution and the same amount bands, then compare total cost and final received amount.

In Latin America two extra dimensions must be included.

The first is the cost of tax ID and invoicing services. Where the provider takes the transaction and issues invoices through a local entity, that capability usually shows up inside the price structure rather than as a separate line. Comparing transaction rates alone leads to the wrong conclusion. The second is the cost of refunds and disputes. Cash method refunds take unusual paths and dispute evidence requirements differ; for the process see the Chargeback Reason Codes and Evidence Playbook.

Comparing fees without conversion and compliance cost usually produces a biased conclusion.

6. How It Divides Work With Other Options

6.1 Against global acquiring platforms

The strengths of a global acquiring platform are mature interfaces, complete documentation and standardised multi-currency support, which suits teams with engineering capacity that want payment logic under their own control. In Latin America their local method coverage depends more on partner channels; the method list may be sufficient, but depth on tax ID and invoicing may not match a local acquirer.

When evaluating this class, compare the market focus and settlement structure of Adyen and PayPal side by side.

A pragmatic combination is to run main card volume and mature-market business on a global platform while filling local methods and the tax ID and invoicing step in Latin America with a local acquirer. The cost is two reconciliation flows, two state machines and two dispute processes, which takes extra engineering to abstract.

6.2 Against merchant of record models

Another common route in Latin American business is the merchant of record model. Under it the platform sells to the end buyer in its own name, taking on invoicing, tax and part of dispute responsibility, while the seller settles on agreed terms. This is a different responsibility structure from local acquiring.

The difference is who answers to the end buyer. Under local acquiring the seller remains the selling party and invoicing and filing responsibility must be agreed separately. Under merchant of record the platform is the selling party and seller responsibility is shifted forward, at the usual cost of a higher all-in cost and weaker control over pricing.

Both models work, but they cannot be understood as interchangeable. Which one to pick depends on your capacity to take on tax obligations and your tolerance in the margin structure; for the mechanics see the Merchant of Record Platforms Guide.

For the wider regional picture see the Latin America Payment Guide, and for licensing and compliance on the onboarding side see the Payment Compliance and Licence Filing Guide.

7. Who It Fits and Who It Does Not

7.1 Good fit

First: teams whose main incremental market is Latin America but which have no local tax ID or entity. The value of a local acquirer is most direct here, using the provider's entity and settlement path to make selling possible at all.

Second: teams that need to cover several local methods without contracting separately in each country. Fragmentation in Latin America is high, and country-by-country onboarding quickly outweighs the technical cost.

Third: teams in the market validation stage that have not committed to long-term local investment. At this stage solving collection first and leaving the long-cycle entity and tax ID questions for later is the more realistic order.

7.2 Weak fit

First: teams that hold tax and compliance entirely in-house and want the selling entity to remain their own at all times. Local acquiring still works, but the responsibility boundary has to be written very precisely, or filing and invoicing will keep coming back.

Second: teams that only need mature-market business and treat Latin America as a tiny slice. Carrying extra reconciliation and tax complexity for a tiny increment does not pay off.

Third: large enterprises needing unified acquiring across regions with multi-entity settlement. Those needs sit closer to enterprise acquiring or a global platform, not a single-region local acquirer.

Fourth: teams treating full compliance and tax outsourcing as the goal. A local acquirer changes channels and settlement paths, not your tax obligations.

8. Rollout Notes and Common Misreadings

8.1 Rollout notes

The last point matters most. Complexity in Latin American business lands mainly on finance and tax, and if those two lines come in late, earlier technical choices usually need rework.

8.2 Common misreadings

The first misreading is assuming that onboarding a local acquirer transfers tax responsibility. Whether responsibility moves depends on the contract structure and on whether a merchant of record model is actually in place. Under most local acquiring arrangements the seller remains the selling party, and tax and filing duties do not disappear because the channel changed.

The second misreading is assuming Latin America can be served with one integration for the whole region. Tax systems, lead methods and regulatory requirements differ widely. Getting Brazil right does not mean getting Mexico right, and Mexico does not mean the Andean markets.

The third misreading is assuming a local method is just one more button. Slip, instant transfer and cash methods differ in confirmation timing, refund path, reconciliation rules and support scripts. Treating them as card variants is where things break most often in the first quarter after go-live.

More acquiring and local payment options are listed under Payment, organised by acquiring capability, local method and market region.

Note: this article is based on public information and general provider mechanics. Current rates and onboarding conditions are subject to the provider official pages and the signed contract.

Source: 16IDC original. Product capabilities, pricing and eligibility requirements follow the relevant providers’ official documentation and contract terms.