Boleto
Understand the delayed Boleto payment reminder event.
The significance of the Boleto payload in the delayed_payment.reminder
request lies in its role in facilitating the identification and reminder process for pending or expired payments made through the Boleto payment method. Specifically, the Boleto payload includes critical details such as:
documentCode
: A URL linking to the Boleto document code is essential for payment processing.document
: The numeric identifier for the Boleto, used by the shopper to complete the payment via a banking application.
These elements are crucial for reminding shoppers of outstanding payments, processing expired payments, ensuring a smooth transaction flow, and recovering potentially lost revenue.
A delayed_payment.reminder
event is triggered when a customer places an order using Boleto as their payment method but has not yet completed it. This process ensures that transactions are completed on time and informs customers of their pending payment obligations. The reminder includes essential details specific to the Boleto payment method, ensuring the customer has all the necessary information to finalize the payment.
Key components of the request:
type: Identifies the request as a reminder for a delayed payment (
delayed_payment.reminder
).boletoBancario:
documentCode: A critical URL linking to the Boleto document, facilitating payment processing.
document: The numeric identifier aiding in the completion of the payment via banking apps.
Example Payload:
This reminder is pivotal in reducing payment delays or defaults by keeping shoppers informed, aiding in a smoother transaction flow, and recovering potentially lost revenue.
Last updated