What it is
Boleto Bancário is a standardised payment slip used across Brazil for collecting money. The merchant or its provider generates a slip carrying a barcode, a numeric line and an amount, and the buyer pays it at a bank branch, an ATM, a lottery outlet, a supermarket counter or inside online banking. The slip is a collection instrument rather than a transfer: the payer authorises a payment against their account, and the money travels through the banking collection infrastructure to the beneficiary. Standards for the instrument are maintained by FEBRABAN, the Brazilian federation of banks, with the central bank supervising the wider payments system.
- A boleto is a collection slip with a barcode, a payable amount and an expiry date.
- Buyers can pay it at banks, ATMs, lottery outlets, some retailers and in online banking.
- FEBRABAN maintains the banking standards behind the instrument used across Brazil.
- The buyer needs no card, which is the whole point for a large part of the market.
Where it is used
Boleto exists only in Brazil and is denominated in Brazilian real. Its share of online payments has fallen since Pix arrived, but it has not disappeared, and it remains important in two places. The first is recurring and bill-like payments: utilities, school fees, subscriptions, insurance and anything a household already expects to settle with a slip. The second is buyers who prefer bank-slip payment or want a cash-adjacent flow. For an overseas merchant, Boleto is usually a complement to Pix rather than a replacement for it. Treat the exact role in your checkout as a segment decision, not a universal rule.
- Boleto is available only in Brazil and is settled in BRL.
- It remains common for bills, subscriptions, instalment plans and school or club fees.
- It reaches buyers who have no card or prefer a bank-slip flow.
- It is typically offered next to Pix, not instead of it.
Which businesses it suits
Boleto suits businesses where a delay between order and payment is acceptable. Subscription and membership billing, utilities-style invoicing, B2B collections and mid-value online orders can fit when reconciliation is well controlled. It suits less well when you need immediate fulfilment approval, because the merchant should wait for the provider's confirmed paid status before releasing value. It is a weak fit for low-margin businesses that cannot absorb the administrative cost of chasing unpaid slips and reconciling payments that arrive without a clean reference. Treat it as a reach tool rather than a speed tool when you plan a Brazilian checkout.
- It suits subscriptions, invoices, memberships and B2B collections in Brazil.
- It suits merchants serving buyers who prefer bank slips or cash-adjacent payment.
- It does not suit businesses that need confirmation before releasing the order.
- It does not suit merchants who cannot absorb a meaningful non-payment rate.
How merchants usually connect
Merchants do not generate boletos by hand. A provider issues them through an API, returns the barcode and payment line, and later notifies you when the slip is paid. Cross-border sellers often evaluate PSP routes that can combine Boleto with Pix and card acceptance, but eligibility and method coverage must be checked provider by provider. Brazilian merchants with a bank relationship may be able to register as a cedente and issue boletos directly through their bank or acquirer, but that route can require local documentation, bank setup and reconciliation work. Most foreign merchants should compare provider access before assuming direct issuance is available.
- A PSP such as dLocal or EBANX may generate the slip and report payment back to you.
- Direct issuance can require a Brazilian entity, documentation and a bank relationship as a registered cedente.
- Some providers bundle Boleto with Pix and cards; confirm the live methods in your contract.
- Direct issuance may change unit economics, but it adds reconciliation and banking overhead.
Cross-border merchant notes
Selling into Brazil without a local entity means your provider owns the collection relationship, and you see only what it passes back. That has practical consequences. You depend on the provider's notification timing to know when an order is paid, so build your fulfilment rules around the notification rather than the slip issue date. You also depend on it for refunds, which are slower and more manual here than on card rails. Expiry handling matters too: a slip that passes its due date needs a reissue flow, and unpaid slips need a dunning sequence that your systems should own.
- Your provider owns the collection relationship, so notification quality defines your customer experience.
- Build fulfilment rules around the paid notification rather than the date the slip was issued.
- Refunds are slower and more manual, so set customer expectations before you go live.
- Plan a reissue flow for expired slips and a reminder sequence for unpaid ones.
Fees, settlement and refunds
Treat any published rate as a first filter rather than a price. Actual pricing moves with country, industry, volume, settlement currency, integration method and contract terms, so confirm against the provider's official pricing page or a written quote before you go live. Boleto usually carries a lower per-transaction fee than cards, but the effective cost includes slips that are never paid and the staff time spent chasing them. Confirmation is not instant: the slip is paid by the customer, then cleared, and merchants typically see funds one to two business days later. Refunds are manual and slow. Chargeback exposure is low, but friendly-fraud and fake payment receipts are real risks.
- Published rates are only a starting filter, since real pricing depends on country, industry, volume, currency, integration and contract.
- Confirm final pricing on the provider's official pricing page or in a written quote.
- Confirmation follows payment and clearing, so merchants typically wait one to two business days.
- Every boleto needs an expiry date, and expired slips need a reissue path.
- Refunds are manual and slow, and chargeback exposure is low but not zero.
Alternatives and complements
Pix is the obvious complement and, for many merchants, the primary account-to-account method; still, provider confirmation, refund handling, payout timing and pricing must be verified before you rank it in checkout. Card acceptance is the other useful addition, because Brazilian shoppers may expect instalments on larger purchases and neither Boleto nor Pix provides credit. Banking transfer options can also work for B2B collections where both sides sit inside the Brazilian banking system. A sensible Brazilian checkout usually tests Pix, cards and Boleto together, then orders them by conversion, cost and operational reliability.
- Evaluate Pix when you need faster confirmation than Boleto, then verify provider notifications and pricing.
- Add card acceptance when instalments are needed to close higher-value sales.
- Keep Boleto for buyers who want a slip to pay at a bank, ATM or lottery outlet.
- Use bank transfer collection for B2B invoices where both parties bank in Brazil.
Questions to ask before you integrate
Ask how slips are issued, how quickly paid notifications arrive, and what happens when a customer pays after the due date or pays the wrong amount. Confirm the expiry rules your provider applies and whether partial or over-payments are reconciled automatically. Ask for the settlement currency, the clearing timeline and the FX margin in writing. Ask how refunds are handled, who pays the cost and how long a customer waits. Finally, ask what protection exists against forged payment receipts, because an image of a paid slip is not proof of funds. Ask whether the provider can reissue an expired slip automatically rather than forcing the customer to start again.
- Confirm how quickly a paid notification reaches your systems after the customer pays.
- Confirm what happens when a slip is paid late, partially, or for the wrong amount.
- Confirm the expiry and reissue rules the provider applies to unpaid slips.
- Confirm how refunds are processed, who pays, and how long the customer waits.
- Confirm what protection exists against forged or altered payment receipts.
Merchant usage and connection route
Boleto in the payment stack
Boleto is useful in Brazil when customers prefer a bank slip, invoice-style payment, or cash/bank-channel collection instead of cards or wallets. Merchants should assess it for order reservation windows, payment confirmation timing, expiry rules, customer instructions, refunds, and unpaid-order cleanup.
Connection route
A merchant normally enables boleto through a Brazilian bank, PSP, gateway, acquirer, billing platform, or local collection provider that generates the payment instruction and reports status changes. Confirm who owns issuance, customer notification, reconciliation files, refunds, and expired or duplicate slips.
Verification questions
- Which provider generates the boleto instruction and owns customer-facing payment details?
- What statuses are returned for issued, paid, expired, cancelled, refunded, or disputed payments?
- How long should inventory or service access remain reserved while a boleto is unpaid?
- Are taxes, invoice references, customer identity fields, and payer data captured as required?
- Can the provider reconcile boleto payments to order IDs, installments, subscriptions, or invoices?
Merchant caveats
- Boleto is not a real-time card authorization flow.
- Confirmation, expiry, and refund handling depend on the provider implementation.
- Customer instructions and payment deadlines should be tested in Portuguese checkout flows.
- Do not assume one boleto route covers every Brazilian business model or entity type.
Provider examples to verify
Related markets
Keep researching
- Boleto Bancário: Accepting Bank Slip Payments in Brazil
- Mercado Pago Payment Acceptance
- EBANX Payment Acceptance
- Pix vs Boleto in Brazil: Merchant Shortlist Review
- Boleto vs OXXO
- Submit payment requirements
This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.
Sources
Capability verification checklist
Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.
- Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
- Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
- Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.
Official links to open
Commercial terms to confirm
| Pricing model | provider quote required |
|---|---|
| Pricing basis | official public pricing or terms |
Fields still to confirm
- Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
- FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.
Integration route to confirm
No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.
Fields still to confirm
- API / checkout route: confirm with the provider, acquirer, PSP, or official documentation before launch.
- SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
- PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
- 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.
Operational features to confirm
No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.
Fields still to confirm
- Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.
Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.
Questions merchants ask
How long does a Boleto take to be paid and settled?
The customer pays the slip whenever they choose, usually within a few days of the order. After payment, banks clear it and the merchant typically sees funds one to two business days later. Your payout timing also depends on your provider's settlement schedule, so confirm both the clearing window and the payout schedule before you promise delivery dates.
Do I need a Brazilian company to issue boletos?
No. A cross-border merchant can issue boletos through a licensed provider that acts as the collection party, which is the normal route for market entry. Issuing directly through a Brazilian bank requires a local entity, registration as a cedente and a local bank relationship, which most foreign merchants only consider once volume justifies it.
What happens if a customer never pays the boleto?
The slip simply expires and the order stays unpaid, so the real cost of Boleto is partly the non-payment rate. Manage it with reminder emails before the due date, a simple reissue path for customers who miss it, and a clear order-cancellation rule. Track your paid rate as a metric, not just your fees.
Can a Boleto payment be charged back?
Boleto has no chargeback mechanism in the card sense, because the customer pushes the payment rather than the merchant pulling it. The practical risks are different: forged payment receipts, duplicate payments and disputes about whether goods were delivered. Verify payment through your provider's notification rather than any document the customer sends you.
Is Boleto still worth offering after Pix?
Yes, for segments where a bank-slip flow still fits. Boleto can matter for buyers who prefer a slip, households that already pay bills this way, and B2B or subscription cases where an invoice-driven flow fits better. Test it next to Pix and cards, then keep it where conversion and reconciliation justify the operational work.
How do refunds work on Boleto payments?
Refunds are manual. Because the original payment was pushed by the customer, there is nothing to reverse, so you collect the customer's bank details and send money back through your provider. That makes turnaround slower than a card refund and means your support team needs a documented process and realistic timelines for customers.