← Back

Country payment guide

Accept payments in Brazil

Brazil is a high-priority market for local checkout because many buyers expect Pix, local cards, instalments, boleto-style alternatives, and wallet or marketplace routes instead of a simple international card form. For a small cross-border merchant, the practical question is usually whether to use a local PSP, a global PSP with Brazil coverage, or a regional aggregator that can handle Pix, local settlement questions, refunds, reconciliation, and merchant support.

Which PSPs and payment routes can you explore in Brazil?

Existing research for Brazil includes Asaas, Pagar.me / PagBank, Cielo E-commerce, Rede E-commerce, PicPay Empresas, Mercado Pago. Explore their products and local payment methods, then use your business and company location to narrow the enquiries.

No local company, or no clear contact route?

These are research leads, not approval or industry-support guarantees. Tell us the market and your company location so we can help you explore further.

12Channel recordsPublic directory entries
Latin AmericaRegionBR
Usually requires a local entity, Medium, verify entity and documentsOnboardingFrom structured fields
T+1, Real-time / T+0SettlementVerify on detail pages

Curated market guide

Brazil PSP routes to verify first

Which PSPs or acquiring routes should an online merchant ask first for Pix, boleto, cards, and local wallets in Brazil?

4
local_psp_or_aggregator · curated

Brazilian PSP / aggregator shortlist

AsaasPagar.me / PagBankPagBrasilPagsmile Brazil

Use when you need one commercial conversation for Pix, boleto, cards, and localized checkout instead of separate bank/wallet integrations.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
acquirer_or_bank · curated

Card acquirer or bank merchant-services route

Cielo E-commerceRede E-commerceGetnet (Brazil)Adiq

Use when card acquiring control, local bank relationship, or direct acquirer contracting matters.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
direct_scheme_or_wallet · curated

Direct Pix, boleto, and wallet route

PicPay EmpresasMercado PagoWoovi

Use when a local team can manage method-specific onboarding and wants to verify direct wallet or QR/payment-link options.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
international_psp · curated

Cross-border or international PSP discovery route

Bexs (Ebury Brazil)Bexs PayPagSeguro International

Use when the merchant is not incorporated in Brazil and needs to verify whether a cross-border pay-in or merchant-of-record style path is available.

Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.

  • Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
  • Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
  • Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
KYB prep

Documents to prepare

  • Company registration documents
  • CNPJ or explanation of foreign-entity onboarding request
  • Beneficial-owner and signatory ID
  • Brazilian tax and invoice readiness notes
  • Website/app URL and refund policy
Due diligence

Questions to ask

  • Can my current merchant entity onboard for this market, or is a local company required?
  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Contact route fallback

If the official contact route is unclear

If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.

  • Which local payment methods are actually enabled for my merchant category and transaction model?
  • Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
  • Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
  • Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?

Merchant questions before choosing a provider

Use these questions to separate customer payment fit from PSP onboarding, settlement, pricing, support, refunds, disputes, and compliance details.

How customers may pay locally

Plan for Pix as a core payment expectation, then check domestic credit and debit cards, instalments, boleto or cash-voucher alternatives, wallets, and marketplace checkout routes. A card-only setup can miss buyers who prefer instant bank payment or local instalment behaviour.

Local entity and settlement checks

Ask each provider whether a local company, local tax registration, local bank account, or local contracting entity is required. Settlement currency, FX handling, reserves, and payout timing should be confirmed in writing before integration.

PSP selection notes

Compare global PSPs, LATAM PSPs, local acquiring partners, marketplace routes, and aggregators that can enable Pix and local methods. The right route depends on whether the merchant has a Brazil entity, whether settlement must stay local or cross-border, and how much operational support is needed.

Documents and KYB checks

Prepare company registration documents, beneficial owner information, website and product descriptions, refund policy, chargeback process, expected volume, average ticket size, and industry category. Some providers may ask for extra documents for cross-border or higher-risk sectors.

Integration checklist

Confirm these items before committing engineering time or signing provider terms.

Merchant checklist before integration

Use these questions before committing engineering time or signing a provider contract.

  • Confirm whether Pix is available directly or only through a PSP or local partner.
  • Ask whether a Brazil entity, local bank account, or local tax setup is required.
  • Confirm settlement currency, FX conversion, reserves, and payout timing.
  • Check refund, cancellation, dispute, and reconciliation workflows for Pix and cards.
  • Verify sandbox, webhooks, payment links, hosted checkout, and API support.
  • Ask for official pricing or a written quote before treating costs as final.

How customers actually pay here

Brazil moved from cards to account-to-account faster than most large markets. Pix, operated by the central bank, is widely used for account-to-account payments and has spread from person-to-person transfers into online checkout and in-store QR codes; merchants should still confirm provider confirmation, payout, refund, and reconciliation rules. Cards have not disappeared, because Brazilian shoppers expect parcelamento, splitting a purchase across several monthly instalments, and merchants usually decide whether they or the buyer absorbs the cost. Boleto Bancário remains the fallback for people who prefer cash or have no card: the buyer copies a code and settles it through a bank app, lottery outlet or ATM. Wallets such as Mercado Pago and PicPay sit on top of the same rails. Cash-on-delivery is small but not zero.

  • Pix is often a core local checkout rail, but merchants should confirm payment confirmation, settlement, payout timing, refund handling, and reconciliation with the provider before launch.
  • Instalments are a habit rather than a promotion, and mid-ticket orders often depend on them.
  • Boleto reaches buyers without cards, but the money only arrives once the buyer pays the slip.
  • Wallets like Mercado Pago and PicPay bundle Pix, stored balance and card-on-file in one app.
  • Cash still matters at the margin, especially for first-time online buyers.

Next actions

Next actions for Brazil

Use these internal paths to move from market research to provider outreach without assuming eligibility, pricing, settlement, or local-entity access.

Questions merchants ask

Is Pix usually important for Brazil checkout?

Yes. Pix is often a core local payment expectation, so merchants should check whether their PSP route supports Pix alongside cards and any instalment or voucher methods needed by their buyers.

Can a foreign merchant accept local payments in Brazil without a local company?

It depends on the provider route. Some global or regional PSPs may support cross-border onboarding, while local acquiring routes may require a Brazil entity, tax details, or local settlement setup.

Should Brazil merchants choose a local PSP or a global PSP?

Use a local PSP when local method depth and support matter most; use a global PSP when cross-border contracting, multi-market operations, and unified reporting are more important.

What should be confirmed before integrating Pix?

Confirm buyer flow, payment confirmation timing, refunds, reconciliation, webhook events, expiry rules, settlement currency, and how failed or expired payments are handled.

Are published Brazil payment prices final?

Published pricing is suitable for first-pass screening only; final terms vary by country, sector, volume, settlement currency, integration route, and contract.

Do I need a Brazilian company to accept payments in Brazil?

It depends on the provider route, merchant entity, product category, risk review, payout currency, and contract model. Some cross-border PSP routes may support foreign entities, while domestic acquiring or local settlement routes may require Brazil-specific registration, tax details, or banking arrangements. Confirm the requirement in writing before integration.

Which payment method should I add first in Brazil?

Evaluate Pix early because many Brazil checkout plans need a local account-to-account route, then compare cards, instalments, boleto, wallets, and marketplace checkout based on your buyers. Confirm provider support, entity eligibility, refunds, disputes, reconciliation, and payout handling before treating any method as the launch default.

How long does settlement take for Brazilian payments?

Do not rely on rail-level speed as your payout calendar. Ask the provider to confirm payment confirmation timing, payout schedule, settlement currency, failed-payout handling, refund timing, boleto status handling, card settlement, and reconciliation files in writing.

Public sources