Merchant of Record in Brazil: The Complete SaaS Guide

A Brazilian SaaS company selling to the United States and Europe faces a problem no API integration solves: who is the legal seller on each transaction?

The answer determines who collects tax, who assumes chargeback liability, whose name appears on the customer's invoice, and who answers to tax authorities in each jurisdiction. For companies selling subscriptions across 10, 20, or 50 countries, the answer "the company itself" means maintaining legal entities, bank accounts, and tax registrations in every one of them. The Merchant of Record model shifts that burden to a specialized operator.

What is a Merchant of Record?

A Merchant of Record (MoR) is the legal entity that acts as the actual seller in a digital transaction. The MoR processes the payment, issues the invoice, collects and remits taxes owed in each jurisdiction, handles chargebacks and disputes, and assumes legal liability for the transaction before the customer and tax authorities. The product provider, the SaaS company, maintains the customer relationship, sets the price, and delivers the service, but the MoR appears on the card statement and the invoice.

The model exists because selling software globally demands legal and tax infrastructure most companies lack. For every country with customers, the seller needs a local legal entity, tax registration, a bank account in the local currency, and working knowledge of applicable tax law. Each entity takes over two years to establish and can cost up to USD 2 million, according to industry estimates. The MoR eliminates that need: a single entity (the MoR) processes transactions on behalf of hundreds of providers.

Paddle, one of the leading global MoRs, defines the model from a simple distinction: the MoR is the legal reseller of the product, not the technical processor of the payment. The difference is legal scope, not technology.

How does the Merchant of Record model work in practice?

In practice, the MoR intermediates two transactions. The first, between the end customer and the MoR: the customer buys the product, the MoR processes the payment, issues the invoice, collects the tax, and transfers the net amount to the provider. The second, between the MoR and the provider: the MoR buys the product from the provider and resells it to the end customer. The customer never contracts directly with the provider.

The operational flow follows five steps:

1. The customer visits the provider's website and selects a subscription plan
2. Checkout is processed through the MoR's infrastructure, which identifies the buyer's tax jurisdiction and applies the correct rate
3. The MoR authorizes the transaction, processes the payment via gateway, and performs settlement
4. The MoR calculates, collects, and remits taxes to each jurisdiction where the sale occurred
5. The provider receives the net amount, in local currency or dollars, with a consolidated sales report

The provider maintains control over pricing, the product, and the customer relationship. The MoR is invisible in the software experience; its presence appears only on the buyer's bank statement and in the transaction's tax structure.

What is the difference between a Merchant of Record, a payment gateway, and a PSP?

The MoR operates one layer above the gateway and the payment service provider (PSP). The difference is legal liability, not technology.

The payment gateway is a pipe: it transports the transaction between the customer and the acquirer. The PSP provides the technical infrastructure to process payments, but tax and legal liability remain with the selling company. The MoR replaces the company as the legal seller. It is a difference in legal architecture, not software.

For a Brazilian B2B SaaS company, this distinction has practical consequences. With a gateway or PSP, the company must register for tax purposes in every country where it has customers, understand local VAT/GST regulations, issue compliant tax documentation, and respond to audits. With a MoR, those obligations transfer to the operator.

What do Paddle, FastSpring, and Stripe Managed Payments offer?

The MoR market for SaaS is dominated by three global operators. Each has specific advantages, and the choice depends on the company's profile, the markets it sells into, and its average transaction value.

Paddle and FastSpring are mature operators with infrastructure tested at scale. Stripe Managed Payments is the most relevant entrant: it comes with Stripe's merchant base and local payment method coverage. None of the three, however, solves the Brazilian tax layer.

What global MoRs don't solve for Brazilian companies

Brazilian SaaS companies selling internationally encounter a specific gap with global MoRs. They solve the sale: they process payment, collect VAT/GST in each country, and issue an invoice. They do not solve the tax reality on the Brazilian side: the company still needs to issue a Brazilian nota fiscal, pay taxes on incoming revenue, and demonstrate compliance to Brazil's federal tax authority (Receita Federal).

A sale processed by a MoR is legally an export of services. The Brazilian company receives the net amount in an international account, converts it to Brazilian reais (BRL), and must issue an export invoice (NFS-e), calculate IRPJ/CSLL according to its tax regime, and maintain segregated accounting between domestic and international operations. The MoR delivers a sales report. Brazilian compliance remains the provider's responsibility.

For companies on the Lucro Presumido regime (presumed profit), a global MoR is a pragmatic solution: export of services is taxed with a 32% presumption for IRPJ and CSLL, with no PIS/COFINS (exports are immune, per Law 10.637/2002, art. 5, II, and Law 10.833/2003, art. 6, II). The additional complexity is accounting: maintaining export documentation, proving foreign currency inflow, and correctly issuing the NFS-e. For companies on the non-cumulative Lucro Real regime, exports do not generate PIS/COFINS credits because they are immune, but the regime allows crediting on operational expenses tied to the activity.

How does Merchant of Record work in Brazil?

The concept of a Merchant of Record does not formally exist in Brazilian legislation. What exists is the figure of the importer or reseller that assumes the transaction's tax liability. For a Brazilian company that wants to sell software globally, the MoR operates as the de facto exporter: the contract with the MoR is an export of services, and taxation follows the applicable export rules.

For the inverse operation, a Brazilian company purchasing international software, the Nexforce Marketplace operates as a distribution platform that handles import. The customer buys the software in BRL, via boleto or PIX, with the exchange rate locked at the time of the transaction. Nexforce issues a Brazilian nota fiscal, calculates and remits import taxes automatically, and delivers the amount to the international vendor. For companies on the non-cumulative Lucro Real regime, Nexforce's nota fiscal enables recovery of the 9.25% PIS/COFINS credit; in direct import, that same credit depends on precise tax classification and correct withholding to be properly accounted for. Nexforce's domestic NF simplifies accounting and eliminates the risk of credit loss from classification errors. For companies on the Lucro Presumido regime, which do not take PIS/COFINS credits, the 9.25% PIS/COFINS embedded in the domestic NF is a non-recoverable cost. The benefit for Lucro Presumido is exclusively operational: exchange rate lock, billing in BRL, and consolidation of payment and import into a single process, without the administrative cost of direct import.

Note on Brazil's Tax Reform: PIS and COFINS will be phased out in 2027, replaced by the CBS (Contribuição sobre Bens e Serviços), established by Complementary Law 214/2025. CBS maintains the non-cumulative and credit logic but operates with a unified rate and a different calculation regime. References to PIS/COFINS in this article reflect the current regime; companies on the Lucro Real regime should monitor the transition to CBS and adjust their credit policy under the new framework.

This architecture solves what global MoRs do not address: tax compliance on the Brazilian side of the transaction, with documentation valid for the Receita Federal and tax credits usable by companies operating under the non-cumulative regime.

Global MoR or local distribution platform: how to choose?

The decision depends on three factors: direction of the sale, tax regime, and the need for a Brazilian nota fiscal.

For companies operating in both directions, selling SaaS internationally and purchasing software internationally, the two architectures coexist. The global MoR processes outgoing sales. The local distribution platform processes incoming purchases. Accounting treats each flow with its specific documentation.

MoR or self-processing: where is the inflection point?

The decision between contracting a MoR and maintaining self-processing is not binary. It intersects transaction volume, geographic dispersion of customers, and tax risk tolerance.

A MoR makes sense when the company sells into five or more countries, or when international revenue exceeds USD 500,000 per year. Below that threshold, the cost of self-compliance (maintaining tax registrations, manually calculating and remitting VAT/GST, responding to audits) is manageable, though it consumes the finance team's time. Above it, the cost of self-compliance scales faster than revenue, and the MoR becomes the lower total cost option.

For Brazilian companies, the calculation includes an additional variable: the cost of maintaining an international account with competitive foreign exchange spreads. Global MoRs settle in USD, EUR, or GBP. Conversion to BRL is handled by the provider, who bears the FX spread, IOF/Exchange tax of 0.38% on incoming foreign currency (Decree 6.306/2007), and the settlement timeline. (Import operations, in the opposite direction, are subject to IOF/Exchange of 3.5% on outbound remittances.) The exchange rate lock, offered by platforms like Nexforce Marketplace, eliminates that exposure.

Companies processing fewer than 50 transactions per month and selling into one or two countries outside Brazil can operate with a PSP (Stripe, Adyen) and manual compliance. Companies selling at global scale or requiring tax compliance in Brazil benefit from combining a global MoR for sales and a local distribution platform for purchases.

Frequently asked questions about Merchant of Record

Does a Merchant of Record replace the need for a CNPJ in Brazil?

No. The Brazilian company still needs a CNPJ (Brazil's corporate tax ID), regardless of whether it uses a MoR. The difference is that the MoR assumes tax liability in the jurisdictions of sale. In Brazil, the company maintains its obligations: issuing the export NFS-e, paying IRPJ/CSLL, and maintaining proper accounting.

Does a global MoR issue a Brazilian nota fiscal?

No. MoRs such as Paddle, FastSpring, and Stripe Managed Payments issue commercial invoices in formats accepted in each country, but they do not issue Brazilian electronic invoices (NF-e). The NF-e is the Brazilian company's responsibility when applicable to the transaction.

How much does a Merchant of Record cost?

Commission ranges from 4% to 6% per transaction, plus a fixed fee per transaction (USD 0.50). For a company with an average ticket of USD 100, the per-transaction cost is USD 4.50 to 6.50. For a USD 1,000 ticket, the cost rises to USD 40.50 to 60.50 per transaction. B2B companies with high average tickets typically negotiate reduced rates.

Can Brazilian companies use Paddle or FastSpring?

Yes, provided they have a CNPJ and meet each platform's compliance requirements. Both accept Brazilian companies. The limitation is not access; it is scope: they process the sale, but they do not issue a Brazilian nota fiscal, nor do they resolve tax compliance in Brazil.

Which MoR supports PIX?

No global MoR offers PIX as a native payment method. PIX is a Brazilian payment system, and global MoRs operate with international payment infrastructure (cards, PayPal, Apple Pay, wire transfer). For companies selling into Brazil and needing to offer PIX, a local distribution platform like the Nexforce Marketplace is the alternative with native support for the method.

From operator choice to payment architecture

The Merchant of Record solves a real problem for Brazilian SaaS companies selling globally: it transfers tax liability across multiple jurisdictions to a specialized operator, eliminates the need for local entities, and simplifies international payment management. What it does not solve is tax compliance on the Brazilian side of the operation: the nota fiscal, taxes on incoming revenue, and PIS/COFINS credit for companies operating under the Lucro Real regime.

The most efficient architecture for a Brazilian SaaS company depends on the direction of the financial flow. For international sales, a global MoR such as Paddle or FastSpring covers the payment and sales tax layer. For international software purchases, a local distribution platform like the Nexforce Marketplace delivers the Brazilian nota fiscal, exchange rate lock, and tax credit. The two layers are complementary, not competing.

The decision of which operator to use and which payment structure to adopt precedes technical integration. It is a tax architecture decision. Payment orchestration provides the infrastructure layer; the MoR provides the legal layer. Companies that treat the two as independent decisions lose efficiency. Companies that unify them within the same financial architecture capture margin competitors don't see.

References and Further Reading

• Paddle: What is a Merchant of Record?
• Brazilian Law 10.637/2002 - PIS/PASEP
• Brazilian Law 10.833/2003 - COFINS
• Brazilian Decree 6.306/2007 - IOF/Exchange