Recurring billing on a card is authorized once per cycle. Pix Automático (Automatic Pix) is authorized once per mandate, and every later debit runs against a bank account on a schedule. Moving a subscription book to the instant rail changes what fails, when it fails, and who has to act when it does.
A subscription business collecting in Brazil picks between two authorization models, and the pick is usually made by whoever integrated the checkout first. A card on file carries a per-cycle authorization. Pix Automático carries a standing mandate against an account. Retries, dunning, reconciliation and the share of cancellations nobody chose all follow from which of the two the charge runs on.
Two authorization models sit under the word subscription
In 2026, a company billing recurring revenue in Brazil can charge a card on file or debit an account through Pix Automático. On the card, every renewal is a fresh authorization request: the instrument has to still exist, the limit has to be there, and the issuer's risk engine has to agree, every cycle. On the instant rail, the payer approves a recurring debit once, and after that the schedule executes against an account. An account has no expiry date and no reissue after a fraud alert.
A definition, for anyone reading this section on its own: Pix Automático is the recurring debit model of Brazil's instant payment rail, in which a payer approves a standing mandate once, inside their own bank, and the biller then submits scheduled debits against that payer's account, settling in seconds like any other instant transfer.
What does a Pix Automático mandate actually authorize?
A specific biller, a specific payer account, and a schedule with a ceiling, approved by the payer in their own banking app. The mandate is the object the entire model turns on, and it lives on the payer's side. That placement has two consequences that surprise teams arriving from cards.
- The payer can revoke it without contacting you. Cancellation stops being an event you receive in your own funnel and becomes an event you learn from the rail.
- The mandate has a shape. It is bound to the biller it belongs to, the account it debits, the value ceiling and the periodicity it was approved for. A charge outside that shape is rejected as unauthorized rather than retried as a failure.
So the first thing a billing system needs is a mandate registry: which payers hold an active mandate, under which ceiling, since when, and which ones revoked. Teams that store the mandate as a token and move on rediscover this on the first plan upgrade that crosses the approved ceiling.
Failure modes change shape on the instant rail
On cards, most failures are instrument failures, and they are recoverable by talking to the customer: expired card, reissued number, limit reached, issuer decline. The customer is still a customer, and the work is getting a valid instrument on file.
On the instant rail, failures split into balance failures and mandate failures. Insufficient balance on the scheduled date is the common one, and it is recovered by retrying at a different moment rather than by asking the customer for anything. Revocation is the other one, and it is not recoverable: it is a cancellation that already happened, arriving as a payment event.
That difference reshapes the metric. A card book has a recovery rate that depends on customer contact. A mandate book has a smaller recoverable slice, arriving earlier, plus a hard cancellation signal that no dunning sequence reverses. Reporting both under one failed-payments number hides which of the two a finance team is looking at.
Where does dunning go when the card is gone?
Most of it goes away, and the part that stays changes its job. The email asking for a new card has nothing to ask for when the debit runs against an account. What replaces it is narrower: a retry window built around balance timing, a mandate health check before the charge date, and a re-consent flow for the payer who revoked or whose new plan outgrew the approved ceiling.
Re-consent is the flow teams forget to build. Raising a price or changing a billing period can require the payer to approve a new mandate, which means a pricing decision and a payments integration stop being separate projects. The calendar for a price change on the rail includes the time it takes for payers to re-approve, and some of them will not.
The card still carries credit and reach
Enough of both that cards against the rail is the wrong frame for a subscription book of any size. The card pays when the account behind it is empty, which is precisely the case where an account debit fails. It reaches the international payer whose bank sits outside Brazil's instant rail. It carries installments, a purchase habit the local market is organized around. And it carries chargeback rights, which a support team may prefer as the resolution path for a disputed renewal.
The rail's advantage is the standing authorization and settlement in seconds. The card's advantage is credit and reach. A subscription book offering only one of the two is choosing which customers it loses.
How do you run both rails without doubling the billing stack?
By keeping the payment method separate from the subscription. The subscription owns the plan, the price, the period and the state of the customer. The payment method owns the authorization and the movement of money. Where those are the same object in the data model, adding the rail means rebuilding billing; where they are separate, it means adding a method and a mandate registry beside the card vault.
That separation is the shape ATTRUS supports on the collection side. Pix and Pix Automático are available in the Brazilian Pay-In, alongside other payment methods through one API, with real-time confirmation and automatic currency conversion at execution. That conversion leg carries its own paper trail in Brazil, which we walk through in how a Brazilian exchange contract works as an audit trail.
Renewals on either method reconcile on the same ledger as the rest of the operation, with statements, typed webhooks and audit trails on every state change, and no local entity required in the country being billed. What a platform can embed on a partner's license and what it has to hold itself is the subject of what you can embed in Latin America, and what needs a license. For SaaS platforms selling into Brazil from outside the country, that is the distance between adding a rail and running a second billing operation.
Five questions before moving a subscription book
These five are about the rail. The ones about the provider carrying it are in seven questions to ask before choosing cross-border infrastructure, and the two lists answer different halves of the same decision.
- Can the billing system hold a mandate as a first-class object, with ceiling, periodicity and status? If mandates end up in a column beside the card token, the migration comes before the launch.
- What happens on an upgrade that exceeds the approved ceiling? The answer is a re-consent flow, and it needs a screen someone has to design.
- How does a revocation reach the dunning logic? It arrives from the rail rather than from the cancellation page, and it should stop retries on arrival.
- Which customers stay on cards, and why? International payers, installment buyers, and anyone whose renewal depends on credit rather than on balance.
- Does reporting separate a balance failure from a revocation? They are different events, and one number covers both.
The rail is a billing strategy, with its own consent object, its own failure modes and its own reporting. Treated as a fallback for declined cards, it delivers the fallback and none of the advantage.
What is Pix Automático?
Pix Automático (Automatic Pix) is the recurring debit model of Brazil's instant payment rail. A payer approves a standing mandate once, inside their own bank, defining the biller, the account, the periodicity and a value ceiling. The biller then submits scheduled debits against that account, and each one settles in seconds like any other instant transfer.
Does Pix Automático replace cards for subscriptions in Brazil?
For most subscription books it runs beside them. The rail debits an account, so it fails when the balance is not there, while a card pays on credit in exactly that case. Cards also reach international payers whose banks are outside the Brazilian rail, and they carry installments and chargeback rights. Offering both is how a book keeps the customers each method reaches.
Can a foreign company collect recurring payments in Brazil without a local entity?
Yes, through a licensed local partner. ATTRUS operates in Brazil under its own payment-institution authorization, so a company outside the country can collect in Brazilian reais through Pix, Pix Automático and other local methods on one API, and hold or convert the proceeds without incorporating locally.
What happens when a payer revokes a Pix Automático mandate?
Scheduled debits stop being authorized, and further attempts are rejected rather than retried. The revocation is a cancellation that reaches the biller as a payment event, so the billing system needs to read it, halt retries and treat it as churn on arrival. Winning the payer back requires a new mandate, approved again on the payer's side.