Home / Resource center / Guides
Guide 01 · Choosing a method
The question is not which option is “better”, but which party sends the money. This guide compares the three collection methods against your actual transaction scenario, and explains the opening conditions and limits of each.
Direct answer
A Brazilian buyer places an order on a marketplace and the platform pays you → use Brazilian marketplace collection (a same-name local account receives the platform settlement).
You agree a deal with the buyer directly, and the buyer pays a link you send → use Trade and payment link collection (a fixed-amount BRL collection link).
You want to embed Brazilian local collection inside your own website, app or platform → use PIX API (Direct API for instant collection / PIX Automático for recurring collection).
The three do not conflict: many merchants use two of them at once. For example, a platform store settles into a same-name account while payment links pick up one-off orders from trade shows and social media.
Once you have chosen, the whole application is completed online in the Merchant Dashboard: enter the portal, fill in and submit the details following the on-screen steps, and the system reviews them automatically.
The most reliable way to separate them is who initiates the payment and when. Everything else — amount, technical integration, whether you need a Brazilian local entity — changes with the shape of your business. The table below sets out each case.
| Point of comparison | Marketplace collection | Trade and payment link | PIX API |
|---|---|---|---|
| Who initiates the payment | The marketplace pays out under its own settlement rules | The buyer pays you directly | The buyer pays inside your checkout flow |
| What you provide | A same-name local account under a CNPJ / CPF | A fixed-amount BRL collection link | An API integration, callbacks and order lookup |
| Typical scenario | Day-to-day sales from a Brazilian local store | Trade shows, private channels, social media, direct sales from your own site | SaaS subscriptions, online stores, platform top-ups, usage-based billing |
| Does it need a Brazilian tax ID holder | Yes: a CNPJ (company operator) or CPF (individual operator), and the relationship with the store must pass review | No Brazilian tax ID needed; the non-Brazilian entity contracts directly | No Brazilian tax ID needed; the non-Brazilian entity contracts directly |
| Does it need technical integration | No | No | Yes |
| How the money arrives | PIX or TED credited to the same-name account | The buyer pays by PIX QR Code / PIX Key / TED | PIX / PIX Automático credited into the BRL balance |
A same-name local account is reviewed and opened independently by the applicable partner bank or payment institution; NexaPay does not make the approval decision on their behalf. Whether an account is approved depends on whether the entity, the documents and the partnership meet the applicable rules.
The application itself is completed online in the Merchant Dashboard: enter the Merchant Dashboard → fill in and submit the details following the on-screen steps → the system reviews them automatically → once approved, continue to open and use the product following the on-screen steps. If anything needs to be added or corrected, the system explains it by email and in the application receipt — follow the receipt back to the relevant application.
Cross-border sellers and brands with a local store on a Brazilian e-commerce platform. You have a Brazilian sales entity (a CNPJ company or a CPF individual operator), and the platform pays your sales proceeds into your account under its own rules.
Some platforms are not yet within NexaPay’s confirmed supported scope, and the supported scope changes. Before submitting an account application, check whether your platform is currently supported. If it is not, use the contact option on the page to ask about applicability, so that you do not prepare documents that cannot be used.
Merchants that contract directly as an overseas entity, have real buyers in Brazil and can close deals independently: trade, trade shows, own websites, social media, private channels. This route does not require the merchant to hold a Brazilian CNPJ or CPF.
Once business verification is complete in the Merchant Dashboard following the on-screen steps, you can create payment links in the portal. Documents are submitted in the portal and reviewed automatically by the system; anything that needs to be added is communicated by email and in the application receipt.
This route does not provide card acquiring. If your buyers must pay by credit card, that falls within an acquiring institution’s scope and has to be assessed separately.
Businesses registered in mainland China, Hong Kong, Singapore or elsewhere outside Brazil, selling to Brazilian customers on an ongoing basis, with their own website, app, online store or trading platform. A PIX API integration does not require the merchant to hold a Brazilian CNPJ or CPF.
| Point of comparison | PIX QR Code Direct API | PIX Automático API |
|---|---|---|
| Collection rhythm | Per transaction, the customer confirms instantly | One authorisation, recurring charges |
| Typical business | Online orders, account top-ups, digital goods, instant checkout | Subscriptions, memberships, software services, recurring billing, fixed repayments, usage-based billing |
| Amount | The order amount each time | A fixed or variable amount |
| API action | Create an order, return a QR code or a checkout URL | Create an authorisation and trigger recurring charges |
| Common capabilities | Query, signed callbacks, refunds; PIX Automático additionally supports status callbacks and authorisation cancellation | |
After completing business verification in the Merchant Dashboard, submit the integration details following the steps on the portal’s API page. Documents are submitted online and reviewed automatically by the system; anything to add or correct is fed back by email and in the application receipt.
A Brazilian company cannot onboard directly as the entity for Brazilian cross-border collection business; the onboarding entity has to be a non-Brazilian company. The relationship between the CNPJ / CPF holder, the overseas entity and the store must also pass review.
The two routes solve different problems. Payment links cover “the buyer pays voluntarily”; a same-name account covers “the platform pays out”. To receive platform sales proceeds you still need a same-name account.
The credit method is decided by the payer’s (the platform’s) settlement rules, not by the merchant. The account accepts both PIX and TED credits.
It does not. The account is reviewed, opened and maintained independently by the applicable partner bank or payment institution under its own rules. NexaPay submits the documents online and provides operational support; it does not make the approval decision on the institution’s behalf.
Local payments support PIX Key and PIX QR Code; initiating TED or Boleto payments is not supported at present. The account accepts TED credits — that is a different thing.
Products and services are subject to merchant eligibility review, partner institution approval, account capabilities, platform rules and applicable law. This website does not promise account approval, credit timing or rates.
Sign in to the Merchant Dashboard and submit your application following the on-screen steps. Complete it online in three steps:
Check the system email and the application receipt and follow the instructions back to the relevant application. If you hit something the system cannot handle, use the contact option on the page and the support team will follow it up with you.
Sources
This guide is compiled from NexaPay’s published product pages and compliance disclosures; the publication and last-updated dates are shown in the metadata above.
Apply online
Once you have chosen a method, enter the Merchant Dashboard, fill in and submit the details following the on-screen steps, and the system reviews them automatically. If anything needs to be added or corrected, check the system email and the application receipt and follow the instructions back to the relevant application.