FAQ - Pix Automático
Questions about Recurrences
The recurrence validity is a parameter defined in the relationship between the receiver and the payer. Authorization can be granted for an indefinite period, or alternatively have pre-defined number of charges or final validity date.
Yes, as long as the minimum 2-day advance between the scheduling date and the expected settlement date is respected, which must be before the start date of the next cycle.
Questions about Authorization Journeys
The main difference lies in the user experience and the timing of recurrence authorization. Journey 2 only authorizes the future recurrence without processing payment immediately. Journey 3 allows the first immediate payment together with the recurrence authorization - the payment made is what activates the recurrence. Journey 4 works differently: the user reads a QR Code as if it were a normal PIX, and after making the payment or scheduling, the system offers the automatic pix option. Journey 4 is the only one that supports variable amount recurrences and offers more flexibility in user experience.
It's at the receiver user's discretion. They may return the settled Pix and enable a new journey 3 or may offer another authorization journey for Pix Automático with the exclusive purpose of enabling authorization for subsequent payments.
Frequently Asked Questions about Reconciliation Batches
Reconciliation batches are payment groupings that are automatically created by the system to facilitate reconciliation and control of Pix Automático payments. They serve as a way to organize and track payments by settlement date and recurrence type.
Payments are automatically grouped into batches based on criteria such as:
- Expected settlement date for the payment
- Recurrence type: fixed_amount or variable_amount
- Specific account
- Specific requester
Batches are automatically created by the system when there are payment orders that need to be processed for a specific payment date. The system groups these orders that have settlement on the same day into batches, to facilitate processing, visualization, and reconciliation.
A batch is closed always three days before the payment reference date of that batch, because payment orders need to be sent at most two days in advance relative to the payment date of that cycle. That is, when its closing date arrives.
The system automatically calculates this date based on the payment settlement date minus 3 days, ensuring that payment instructions are sent within the regulatory deadline established by the Central Bank.
Yes, you can query payments from closed batches through the batch query endpoints and listing payments from a specific batch.
Questions about Payment Orders and Attempts
Payment Order: It's the instruction created by the system to make a specific payment on a determined date.
Payment Attempt: It's each individual execution of this payment order, and there can be multiple attempts if the first one fails.
The system makes up to 4 payment attempts per payment order. If all attempts fail, the payment order is marked as rejected.
When all 4 payment attempts fail, the payment order has its status changed to "rejected" and no more attempts will be made for the payment of that cycle.
Retries are automatically executed by the system according to the retry days configured by the receiver when creating the recurrence. Each attempt that fails generates a webhook notification so you can track the status of this payment.
Questions about Cancellations
Yes, you can cancel a specific payment order through the payment order cancellation endpoint, as long as it hasn't been settled yet.
Cancel Recurrence: Cancels the entire recurrence and all future payment orders associated with it.
Cancel Payment Order: Cancels only the specific payment order for that cycle, without affecting the recurrence or other orders.
Questions about Simulation
Simulation scenarios serve to test the complete Pix Automático flow in the sandbox environment, simulating the responses and interactions of the PSP Pagador (Payment Service Provider).
Scenarios should be executed in sequence to simulate the complete flow:
- Create a recurrence
- Process payment orders
- Update execution dates (sandbox)
- Process payment attempts
- Simulate incoming PIX
- Simulate rejected attempts (if necessary)
Questions about Webhooks
The system sends webhooks for various events, including:
- Recurrence status changes
- Payment order status changes
- Payment attempt status changes
- Creation and closing of reconciliation batches
Questions about Benefits and Comparisons
Pix Automático offers a new option to receiver users for receiving and managing periodic recurring charges, using the Pix infrastructure. Among the advantages, the following stand out: increased customer base, lower operational cost for not needing to establish agreements with more than one institution, diversification of payment methods, offering Pix as an alternative to customers who use card or bank slip, in addition to reducing delinquency and more agility in managing their receivables.
Focusing on the experience of both receiver and payer users, Pix Automático presents new functionalities for managing authorizations and recurring schedules. Furthermore, any Pix participant can offer the product to their customers, expanding access for citizens and companies that today are not served by the automatic debit service, offered more restrictively only between banking institutions.