Payment Gateways in Brazil (2026): A Comparison for Businesses

Choosing a payment gateway in Brazil is about more than just “accepting cards.” In practice, it determines which payment methods you offer, how seamless the checkout process is, how funds are settled, and how automated the accounting reconciliation can be.

In this technical guide, we review how online payments are structured in Brazil, the most commonly used methods, and what to look for when selecting a provider. For a regional overview, see payment gateways in Latin America. If your business involves cross-border transactions, see international payments.

In Brazil, it is often necessary to design the checkout process by payment method: Pix, credit cards, and payment slips each have different processing times, fees, and reconciliation procedures.

The goal for businesses is to maximize conversion rates without compromising control over payments, adjustments, and returns.

If you're involved in cross-border transactions, make sure to check compatibility with local payment methods and clarify FX terms before making your choice.

How online payments work in Brazil

In a typical e-commerce workflow, your website or app captures the payment intent, sends the transaction to the provider, and the provider handles the authorization (card or bank transfer), confirmation, and subsequent settlement. The difference between providers lies not only in “whether they approve” the transaction, but also in how they expose events, references, and reports to facilitate operations in Brazil.

For businesses, the most critical issues are typically: issuer approval, fraud and chargeback management, settlement times, availability of reports, and consistency of identifiers for reconciliation.

Most Common Payment Methods in Brazil

In Pix, traceability relies on identifiers and references. Make sure you can link the order → payment → statement.

In the ticket, configure expiration, cancellation, and inventory settings. Deferred payments enhance the customer experience.

The mix of methods varies by industry, average order value, and sales channel. In general, it is advisable to prioritize methods that maximize conversion without compromising operational control: traceability, reconciliation, and returns management.

• Credit Cards: The foundation of e-commerce, with specific terms regarding fees and issuer authorization.
• Pix: An instant payment method with widespread adoption: it improves cost efficiency and reduces chargebacks, but requires reconciliation by identifier.
• Ticket: Useful for certain segments and tickets: affects confirmation times and cancellations.
• Wallets: They complement mobile conversions; it’s advisable to measure their impact by channel.

A best practice is to set up tracking for the checkout process to measure conversion rates by payment method, rejection rates by issuer, and confirmation times. This allows you to choose a provider based on data, not just on the published rate.

The leading payment gateways in Brazil

Since there isn't a single winner, prioritize operational fit: data, webhooks, reports, and support. That's what determines scalability.

This list is for informational purposes only and is not a ranking. The exact availability of payment methods, terms and conditions, and technical support varies depending on the specific case and volume.

• PagSeguro: A Brazilian provider of online payment processing services with local options.
• Mercado Pago: Checkout for merchants using credit cards and local payment methods, depending on the configuration.
• Pagar.me: A payment platform and gateway focused on integrations for businesses in Brazil.
• Stone: Payment solutions for merchants with e-commerce and POS capabilities.
• Cielo: A provider of solutions for retail and e-commerce.
• EBANX: Specialist in local payment methods in Latin America (including Brazil) for global merchants.
• Rebill: A platform for accepting payments in Brazil using local payment methods, with a focus on reconciliation, fund settlement, and operational control.
• Stripe: APIs for credit card processing; availability by country and use case.
• Adyen: An enterprise platform with orchestration capabilities and local methods.
• dLocal: Access to local payment methods for international transactions or platforms.
• Getnet: Payment acceptance solutions for merchants.

Before making a decision, I requested API documentation, payment event notifications (webhooks), sample settlement reports, and a clear breakdown of the fees charged (transaction fees, fixed fees per transaction, chargebacks, anti-fraud fees, refunds, and FX fees, if applicable).

How to Choose a Payment Gateway in Brazil

For businesses, the selection process should be based on operational and risk requirements. A practical checklist:

• Required methods: cover the actual payment mix (credit card, bank transfer, cash, digital wallet) without increasing the number of reconciliations.
• Conversion: latency, friction, retries, and authentication policies.
• Settlement: schedule, currency, fee netting, and availability of transaction details.
• Reconciliation: Consistent, exportable IDs, reliable webhooks, and reports detailing net amounts, fees, and settlements.
• Risk: 3DS support, anti-fraud tools, chargeback management, and rules based on BIN/country.
• Scalability: limits, API stability, SLAs, and support for high demand.

In Brazil, Pix and fees mean that the “total cost” is more than just the credit card interest rate.

Payment gateway fees in Brazil

There is no such thing as a “single fee.” The total cost typically consists of: a variable rate (percentage), a fixed fee per transaction, chargeback costs, refund costs, anti-fraud costs, and, for international transactions, FX and bank fees.

To compare providers, request a breakdown of the net amount settled per transaction (settlement example) and simulate different payment method combinations. A payment gateway with a slightly higher fee may be more efficient if it improves approval rates and reduces chargebacks.

Operations and reconciliation: what data you need in Brazil

Beyond the checkout process, issues often arise in the back office: reconciliation, refunds, adjustments, and reporting. A minimum set of data per transaction includes: merchant ID, order ID, payment method, gross amount, fee, taxes, net amount, currency, authorization date, settlement date, and final status.

If the provider doesn’t offer a consistent model for events (webhooks) and reports, the team ends up having to make up for it with spreadsheets. That’s why, for businesses, “integration” doesn’t end with an approved payment: it ends when you can close out the month without any discrepancies.

Implementation: Technical Checklist for Businesses

If you work with ERP or BI systems, make sure to verify the format of export files (fields, delimiters, time zone) and how changes are versioned from day one. A change to a column can break pipelines.

I defined the returns process: who initiates the refund, how the customer is notified, how it appears on the statement, and how it is recorded in the accounting system (reversal of revenue vs. credit memo).

Work with support to define the incident response process: which logs to share, response times, and how to verify resolution. When it comes to payments, time is of the essence because it affects conversion rates and reputation.

If you plan to use more than one provider, design the “workflow” and governance from the start: when to use each method, how to compare metrics, and how to avoid duplicate reconciliations.

Before integrating the system, define the data model you want to maintain: internal order, customer, method, status, net amount, fees, and dates. The finance department will use this model to close the books each month.

Determine early on how you will handle idempotence (retry mechanisms that prevent duplicate charges), how you will store tokens, and what retry strategy you will use in the event of authorization failures.

In QA, test "unfavorable" scenarios: chargebacks, partial refunds, disputed charges, pending payments, and expired payments. The key is to ensure that each scenario is consistently tracked in reports and events.

At the operational level, set up alerts for: webhook failures, rejection rates by issuer, fraud spikes, discrepancies between settled net and expected net, and settlement delays.

Red flags to watch for when evaluating a gateway

These signs often foreshadow operational and reconciliation issues, even if the provider “charges fairly” or promises high conversion rates.

• The reports do not show the net amount per transaction or use different IDs across the dashboard, API, and exportable data.
• There are no reliable webhooks, or there is no way to reprocess events.
• The settlement statement is provided in aggregate form without sufficient detail for reconciliation.
• Refunds get "lost" in adjustments, and there is no way to track why a certain amount was deducted.
• The payment terms are unclear depending on the method (credit card vs. bank transfer vs. cash).

Common mistakes when implementing payment gateways

These errors occur when the focus is solely on launching the checkout process and the related operations—such as reconciliation, returns, and adjustments—are overlooked.

• Failure to define a unique and persistent order ID throughout the entire workflow (checkout, webhooks, reports).
• Reconcile using bank totals without reconstructing the net amount per transaction.
• Do not test statuses that are not "Happy" (pending, expired, partial refunds, chargebacks).

Practical example: Pix confirms quickly, but reconciliation depends on IDs. If the bank statement doesn't include a reference you can map, you end up reconciling manually on a volume basis.

Frequently Asked Questions About Payment Gateways in Brazil

Which payment method should be prioritized for e-commerce in Brazil?

It depends on your audience and payment amount. Generally, credit cards are the standard; adding bank transfers or local payment methods can improve coverage. Track conversion rates by payment method.

How does the reconciliation statement affect accounting reconciliation?

Define which identifiers and reports you receive. Ensure that each transaction has unique IDs and that the reports detail the net amount, fees, and settlements.

What should you look for in the clearance sale?

Calendar, currency, commission breakdown, and transaction details. Also, whether there are any withholdings or adjustments listed on the statement.

What do I need to process international payments to Brazil?

In addition to the payment method, you need to clarify the foreign exchange rate, credit times, and reconciliation between the supplier, the bank, and the accounting department. See the guide to international payments.

When is it advisable to use more than one supplier?

When you need redundancy, better rates per method, or coverage for methods that a single provider cannot offer. The trade-off is greater operational and reconciliation complexity.