Pix Automático for businesses enables recurring payments after a one-time customer authorization. It can broaden payment options and remove manual billing steps, but it does not eliminate failures, cancellations, or payment defaults. The decision to adopt it should consider customer profiles, total cost, reconciliation, and the process used when a debit fails.
This matters for subscription software companies, schools, gyms, communities, agencies, and subscription businesses. Changing the payment method without redesigning operations may simply replace one known problem with another. Card payments may fail because of credit limits or expiry. Pix Automático may fail because of insufficient funds, transaction limits, or canceled authorization.
How does Pix Automático work for businesses?
With Pix Automático, a business registered as a legal entity sends periodic charges, and the customer’s bank makes the payments under a prior authorization. The customer confirms that authorization in their bank’s own environment and may set conditions such as a maximum amount per charge.
According to Central Bank of Brazil, the basic flow has five stages: the business offers the payment option, the customer authorizes it, the business sends each charge, the bank schedules it and notifies the customer, and on the scheduled date it attempts payment.
- The business contracts a provider that offers payment collection through Pix Automático.
- The customer receives an offer, scans a QR Code, or is directed to the banking app.
- The customer confirms the authorization and its terms with the bank.
- The company sends the charges within the authorized recurrence.
- The bank informs the schedule and tries to settle the payment on the scheduled date.
A charge may have a fixed or variable amount and a weekly, monthly, quarterly, or annual frequency. This accommodates both a stable subscription and a bill that varies with usage. The commercial contract still defines what is owed. Pix Automático makes the payment under the authorization, but does not replace the contract, billing, or customer service.
How does it differ from Pix Agendado and recurring card payments?
The central difference is who initiates each payment. With Pix Agendado Recorrente, the payer schedules future transfers. With Pix Automático, the customer authorizes the business to send periodic charges under the agreed terms.
A Official Pix FAQ clarifies that the company can set values and dates after authorization. The client, in turn, can consult authorizations, check scheduled debits, set a ceiling and cancel a specific charge without necessarily ending all recurrence.
Recurring card payments use different infrastructure and may offer different features depending on the acquirer and issuer. Under some contracts, the business can also receive advances on receivables. With Pix Automático, funds depend on each charge being settled. Comparing only the transaction fee therefore gives an incomplete picture.
- Pix Agendado Recorrente (recurring scheduled Pix): the client sets values and dates in the bank.
- Pix Automático: the company sends charges within a client-controlled authorization.
- Recurring card payments: the collection goes through the card infrastructure and the rules of the contracted provider.
Does Pix Automático reduce payment defaults?
Pix Automático can reduce delays caused by forgetfulness, but does not guarantee payment. Charges remain subject to available funds, the limit set by the customer, the bank’s transaction limit, and the validity of the authorization.
When there is no balance or limit on the scheduled day, the bank shall notify the customer and make a new attempt on the same day. The regulation also allows the recipient to plan further attempts, provided that this is provided for in the authorisation.
A BCB No. 513 Normative Instruction provides that these retries may occur for up to seven calendar days and on no more than three different dates. The period must not extend into the next cycle or beyond the end of the recurrence.
This creates an operational opportunity: treat a failure as a recoverable event before suspending the service. It also creates a risk. If billing, product access and communication do not share the same state, the customer may receive undue reminders, lose access before the last attempt or remain active after a definitive failure.
When is it worth adopting?
Pix Automático tends to make more sense when a business has recurring revenue, customers who use Pix but do not want to register a card, and operations able to track authorization, settlement, failure, and cancellation. It can be introduced as an additional option before becoming the main payment method.
Four questions help test the decision:
- Is there a clear payment problem? Measure how many customers drop out because an appropriate option is missing and how many manual charges become overdue through forgetfulness.
- What's the total cost? Include provider tariff, integration, reconciliation, support, fault communication and eventual loss of card-related benefits.
- Can the base authorize it without friction? Consider the banks used by customers, the familiarity with the flow and context in which the authorization will be requested.
- Can the operation handle exceptions? Define what happens after each attempt, when access is suspended and how a cancelled authorization is differentiated from a closed contract.
This development is not exclusive to Brazil. In the United Kingdom, recurring account-to-account payments use authorizations with limits and revocation mechanisms. The documentation from British Open Banking describes a similar logic of control by the payer. The useful lesson for the Brazilian company is operational: visible consent and simple cancellation are part of the billing product.
How can we roll this out without risking all our revenue?
Start with a small subset of the customer base and keep another payment method available. The pilot aims to find out whether the benefit appears in real operations, rather than just confirming that the technical integration works.
- Choose a segment with simple charging, as new customers from a single monthly plan.
- Register the current method to compare conversion, failure, recovery and cancellation.
- Design the authorization journey with an amount, frequency, and rules that are easy to check.
- Integrate billing states with customer access and support.
- Test lack of balance, insufficient limit, cancellation of a debit and closure of the authorization.
- Review the results by one or more full billing windows before extending the offer.
The Central Bank does not require the service to be free for recipients. Its official page says receiving businesses may be charged and should consult their provider. Request a written proposal and confirm what is included: API, reconciliation, notifications, support, retries, and refunds.
What metrics show if the change worked?
Adoption should be assessed by the effect on receipt and experience, not by the isolated number of authorizations. An active authorisation does not mean that the collection was sent, liquidated or maintained by the client.
- Conversion of authorisation: customers who completed the flow divided by those who started it.
- Settlement on the first attempt: charges paid on the scheduled date without later recovery.
- Recovery: failures that were settled in new attempts within the allowed period.
- Final failure: collections that remained open after the attempts were closed.
- Cancellation of authorisation: authorisations closed, separated from actual cancellations of the product.
- Cost per payment collected: tariffs and operating costs divided by payments actually settled.
- Reconciliation time: necessary effort to connect each payment to the correct customer and invoice.
Compare these metrics with card payments, boleto (a Brazilian payment slip), or manual Pix for the same customer profile. Mixing different plans, prices, and audiences may attribute to the payment method an effect caused by another change.
The decision is financial and operational
Adopting Pix Automático makes sense when it improves access to recurring payments and the business can manage the full billing cycle. The infrastructure handles authorization and money movement. The business still needs to manage contracts, billing, reconciliation, customer service, and recovery.
Before expanding the payment option, gather the pilot data and answer: did the cost per payment collected fall, did recovery improve, and did the customer encounter less friction? This analysis depends on consistent context across the payment provider, financial system, and customer base—the same problem addressed in the framework for context engineering for business.
SOCEO can help organize these sources, show where the numbers diverge, and turn monitoring into a verifiable decision. The tool does not choose the payment method for you. It helps you see what supports the choice and what still needs to be measured.