Guides
API Reference

Journey 4

QR Code for Payment with Due Date and Recurrence Option

Suggest Edits

The receiver can create a QR code with a due date or a static QR code, both containing recurrence data. After the payment, the payer has the option to accept or reject the associated recurrence.

  • How it works: The receiver can generate a QR code with a due date or a static QR code, both with recurrence data, and the payer scans the QR code and makes the payment. After the transaction, a recurrence offer is presented, which can be confirmed or rejected.

  • API Integration: GeneratePixQrCodeDueDate (to generate the recurrence and a payment with a due date) or GenerateStaticPixQRCode (to generate the recurrence and a static payment), PixOut (endpoint when the first payment is made), and NotifySuccess (endpoint when the recurrence is approved) or NotifyFailure (endpoint when the recurrence is rejected).

More details:

GenerateStaticPixQRCode: Generates a static QR code. Only if recurrence data is provided, an Automatic PIX will be created with the first payment configured as static.

GeneratePixQRCodeDueDate: Generates a QR code with a due date. Only if recurrence data is provided, an Automatic PIX will be created with the first payment subject to a due date.

NotifySucess: This webhook notifies that the recurrence has been approved.

NotifyFailure: This webhook notifies that the recurrence has been rejected.

Updated about 4 hours ago