Skip to main content
Boleto is a voucher payment method in Brazil. Customers get a Boleto with a barcode and a numeric code for their purchase. They pay it in cash at a bank, a lottery outlet, or an ATM, or through their online banking. It gives customers without a card a way to pay online. Payrails processes Boleto through dLocal as the payment service provider (PSP).

​
How a Boleto payment works

Boleto is a redirect payment method that ends with an offline or online bank payment:
  1. The customer selects Boleto at checkout.
  2. Payrails returns a redirect URL from dLocal, and the customer goes to the dLocal payment page.
  3. The page shows the Boleto barcode and numeric code.
  4. The customer pays the Boleto at a bank, a lottery outlet, or an ATM, or through online banking.
  5. Payrails receives the final result from dLocal and updates the payment.
The payment stays pending until the customer pays the Boleto. Each payment is single-use: every purchase gets its own Boleto. Payrails captures Boleto payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

Boleto supports BRL (Brazilian real) as its only presentment currency.

​
Integrate Boleto

Choose the PSP that processes Boleto for you. The guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

Boleto via dLocal

​
Check PSPs

​
Ways to integrate Boleto

  • Payrails SDK: the Web SDK shows Boleto when your workflow returns it as a payment option, and redirects the customer to the dLocal payment page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with boleto as the paymentMethodCode. The PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. The payment stays pending until the customer pays the Boleto, so don’t fulfill the order on the authorize response or the customer’s return to your site.
Last modified on October 5, 2026