Automatic Pix FAQ
1. What happens if my customer pays the authorization before the due date?
If the payment is completed up to the day before the due date, the instruction related to that cycle will be automatically canceled to avoid duplicate debits. This does not terminate Automatic Pix: the recurrence remains active and the next charge will be generated normally on the scheduled date of the next cycle.
2. Is the payer responsible for processing the charge every month or does Asaas do it automatically?
After the first payment and the Automatic Pix authorization, the payer no longer needs to take any action monthly. However, Asaas does not create the charges automatically either. You need to create the payment instruction via API for each cycle (monthly, for example). Once the instruction is created, the debit occurs automatically, provided there is sufficient balance.
3. Can I use split payments together with Automatic Pix?
Yes and no. During the authorization creation process, split payments are not supported. However, when creating new charges within the same authorization, you may apply split normally using our charge API.
4. What happens if the customer does not have enough balance on the Automatic Pix due date?
The instruction will expire and the charge related to that authorization will change its status to OVERDUE, with the webhook event PAYMENT_OVERDUE being generated normally.
5. How do retry flows work when the payer does not have sufficient balance?
The first Pix payment attempt occurs at 7 AM. If there is no available balance, the bank will continue attempting throughout the day using the intraday retry flow (as defined in the official Pix documentation provided by the Central Bank of Brazil). Subsequent attempts will occur at 10 AM, 1 PM, 4 PM, 6 PM, 7 PM and 8 PM. If all attempts fail, at 8 PM the schedule is definitively refused, with no additional attempts after that time or on subsequent days.
6. Can I change the value of payment instructions?
It is possible to change the value of payment instructions depending on how the authorization was created. The value field is not mandatory during creation. When it is sent with a fixed value, that value becomes locked in the authorization and cannot be changed in subsequent monthly instructions. This scenario is suitable for fixed-value charges, such as a gym membership, for example.
On the other hand, when the authorization is created without sending the value, the amount can be freely defined for each monthly instruction. This is ideal for scenarios where the amount may vary, such as consumption-based charges or utility bills.
If the authorization was created with a fixed amount and later it becomes necessary to change it, this modification cannot be performed on the same authorization. In this case, the current authorization must be canceled and a new one must be created with the desired amount.
7. What is required to be eligible to use Automatic Pix with Asaas?
The prerequisites for using Automatic Pix are:
- The account must belong to a legal entity (individual accounts are not eligible)
- The account must be approved
- The account must not have pending registration issues
- The company's CNPJ must be active with the Brazilian Federal Revenue Service
- The CNPJ must have been active for at least 6 months
- The account must not have fraud-related flags associated with Pix
8. What happens if an account was eligible and becomes ineligible?
When an account becomes ineligible, the event PIX_AUTOMATIC_RECURRING_ELIGIBILITY_UPDATED is sent, with eligibility.status equal to INELIGIBLE. As a result, all active authorizations are canceled and all payment instructions are canceled. Therefore, upon receiving this event, you must adjust the related charges to avoid any losses.