Stripe's Pix Automático Reaches 93% of Brazilian Adults. A Business Based in Brazil Still Can't Turn It On.
Stripe's Pix Automático only works for businesses domiciled outside Brazil — and its fixed-amount mandate cap breaks upgrades, proration, and overages.
Pix is not a niche rail you can get away with ignoring if you sell into Brazil. It's the default way the country pays, full stop — ahead of cash, cards, and bank transfers combined. So when Stripe shipped mandate-based recurring billing for Pix this year, the obvious assumption was that every SaaS business billing Brazilian customers had just gained a serious new subscription rail. Read the actual eligibility rules and a stranger picture shows up: the feature works great for a company in Austin or Berlin billing a customer in São Paulo, and it's switched off entirely for a company that's actually based in São Paulo itself.
That 93% figure — 142 million people — is the Central Bank's own count of adults who touched Pix at all in a single month. Add the volume: more than 36 billion Pix transactions in the first five months of 2026 alone, close to 3,000 a second. There's no serious argument left that Pix is optional infrastructure for anyone selling into Brazil. The argument is entirely about which version of it you can actually use, and that depends on where your business is incorporated, not on anything about your product.
One rail, two completely different eligibility rules
Stripe's documentation splits Pix into two products that share a name and little else. One-time Pix — scan a QR code, money moves in seconds, done — works for Brazil-domiciled Stripe accounts and foreign ones alike. Pix Automático, the recurring product built specifically for subscriptions, memberships, and anything else that bills on a cycle, carves Brazil-domiciled accounts out entirely. The documentation states it without qualification: Pix Automático isn't available to businesses domiciled in Brazil. A Brazilian SaaS company serving Brazilian customers can take a one-time Pix payment from them today and cannot put them on a recurring Pix mandate at all through Stripe, regardless of plan, volume, or how long they've been a customer.
A foreign company — a US, UK, or EU-domiciled Stripe account, among the eligible list — faces the opposite situation: it can set up Pix Automático mandates with Brazilian customers that a domestic competitor literally cannot offer. If you're a cross-border SaaS business already serving Latin America out of a US or European entity, that's a genuine opening most of your Brazil-based competitors don't have access to on this specific rail. If you're a Brazilian company building for the Brazilian market, it's a gap with no workaround inside Stripe's current product — you're stuck offering one-time Pix and asking customers to manually pay again every cycle, or routing them onto a card instead.
| Recurring billing option in Brazil | Who can offer it | Variable amounts? |
|---|---|---|
| Card on file | Any Stripe account, Brazil-domiciled or not | Yes, within normal card-network limits |
| Boleto, reissued manually each cycle | Any Stripe account | Yes, but no standing mandate — the customer must act on each new slip |
| Pix Automático mandate | Only Stripe accounts domiciled outside Brazil | No — capped at the amount authorized at mandate creation |
Compiled from Stripe's Pix payments documentation (2026).
The mandate cap: the catch that hits even the businesses who can use it
Eligibility is only the first filter. Even a foreign-domiciled business that's allowed to run Pix Automático runs into a second restriction that changes how you have to design billing for it. The customer authorizes an exact amount and a billing cycle when they set up the mandate in their banking app. Every future charge against that mandate has to stay inside the terms they agreed to — and if you try to charge more than what was authorized, the payment doesn't get adjusted or flagged for review. It fails outright, the same category of hard stop as an expired card, except there's no "update your payment method" prompt that fixes it, because nothing about the payment method itself is broken.
Think through what that actually breaks in a normal SaaS billing cycle. A customer upgrades from a $29 plan to a $79 plan mid-month — the prorated charge for the difference exceeds what their Pix Automático mandate authorized, and it fails. A usage-based product bills an overage on top of a base fee — the overage pushes the total past the mandate ceiling, and it fails. You run an annual price increase and need to collect a slightly higher renewal amount — same failure, same reason. None of this is a decline you can smart-retry your way through, the way Stripe's Smart Retries work on a card that failed because of a temporary insufficient-funds issue. The mandate amount is a hard ceiling set once, by the customer, and the only fix is getting them to actively re-authorize a new mandate at the new amount — which means pulling them back on-session, the exact friction recurring billing exists to avoid in the first place.
Sources: Banco Central do Brasil (April 2026); figure cited in CancelFlow's cross-border payments research; Stripe Pix documentation (IOF rate).
Every Pix Automático charge is, by definition, a cross-border one
Because only foreign-domiciled businesses can run the recurring product at all, every single Pix Automático subscription is structurally a cross-border transaction — and Brazil taxes cross-border currency conversion through IOF, a tax applied whenever a Brazilian customer pays a business domiciled outside the country. Stripe's current rate is 3.5% of the transaction value, charged on top of whatever you're billing. You get to choose who absorbs it: the default, amount_includes_iof: never, passes the full 3.5% markup to the customer inside their banking app at authorization time; setting it to always means you eat the tax out of your own settlement instead. Either way, a Brazilian subscriber paying a foreign SaaS company via Pix Automático is paying a tax that a Brazilian subscriber paying a domestic competitor via card or boleto never sees — one more reason the mandate amount matters: if your prices already sit close to a round, psychologically clean number, deciding who swallows that 3.5% changes what the customer actually sees on their statement.
The confirmation delay changes what "paid" means for a few days
Pix's reputation is built on being instant — a one-time Pix payment clears in seconds. Pix Automático trades that away for the recurring use case, and the delay is built into the regulatory design, not a Stripe limitation. Once a mandate is live, each scheduled charge triggers a mandatory pre-debit notice to the customer's bank, a required 3-day wait, and then the actual debit attempt — with the whole cycle, including retries, able to stretch to 7 days before the charge reaches a final state. During that window, the PaymentIntent sits in processing, not succeeded and not failed. A renewal that would clear instantly on a card can leave an account in payment limbo for most of a week on Pix Automático, and any access-gating logic built around "charge succeeded, so grant access" or "charge failed, so restrict access" needs a third state in between, or you'll either lock out a customer who's going to pay in two days or grant free access to someone whose mandate ultimately fails at the end of the window.
What shows up on the statement isn't your name
We've written before about how a mismatched statement descriptor turns a legitimate renewal into a dispute because the customer doesn't recognize the charge on sight. Pix Automático makes that risk structural rather than a configuration mistake you can fix. Stripe doesn't support customized statement descriptors for Pix at all — the value you set in your account settings is ignored. Stripe's local processing partner, Ebanx, appears as the payment recipient on the customer's bank statement; your business name shows up only in a secondary identifier field that most banking apps don't surface prominently next to the amount. A subscriber who doesn't immediately connect "Ebanx" with the SaaS tool they signed up for three renewals ago is exactly the customer who files a dispute instead of checking first.
That matters more on Pix than it would on a card, because the downside of a Pix dispute is worse. We've covered how Stripe quietly added an API to appeal a lost card dispute in September 2026. Pix gets no equivalent. Stripe's documentation says plainly that you can't contest a Pix dispute or submit evidence against it — the partner's decision is final, full stop, and Pix doesn't support partial disputes either, so a successful dispute reverses the entire charge. A card dispute at least gives you an evidence window and, now, an appeal path if you lose it. A Pix dispute gives you neither, which makes the Ebanx-branded statement line a materially bigger risk than a confusing card descriptor ever was.
| What happens | Card | Pix Automático |
|---|---|---|
| Charge exceeds what the customer pre-authorized | Often succeeds up to network/issuer limits | Fails outright — hard mandate ceiling |
| Customer disputes a recognized-but-forgotten charge | Evidence window, partial wins possible | Full reversal only, no partial disputes |
| You lose the dispute | Can now appeal via Stripe's Sept 2026 API | No appeal — partner decision is final |
| Charge settles | Typically same day | Up to 7 days with mandatory pre-debit wait |
Cancellation runs through the customer's bank, not your product
A Pix Automático mandate isn't something your cancellation flow can touch directly. Detaching the saved payment method on your end revokes it, but a customer can just as easily kill the mandate from their own banking app at any time, with no visit to your product and no interaction with your cancel page at all. Stripe surfaces this as a mandate.updated event, and once it fires, the mandate is gone — there's no grace period, no retry, and no path back except asking the customer to go through full mandate authorization again, on-session, from scratch. It's a different shape of involuntary churn than the one most dunning playbooks assume, closer to the mandate-revocation problem we've covered with UPI Autopay in India than to a simple card decline, and it's one more reason a Brazilian subscriber who cancels through their bank instead of through you never shows up as a clean, attributable cancellation in your churn reporting — it just looks like a payment that stopped working.
What this actually means if you sell into Brazil
If you're a Brazilian company, Pix Automático isn't a decision you get to make yet — it's simply off the table through Stripe, and your recurring billing options are a card, a manually-reissued boleto, or working through a different local processor that may offer broader domestic eligibility. If you're a foreign-domiciled SaaS business weighing whether to turn Pix Automático on for Brazilian subscribers, the honest framing is that you're trading card-level flexibility for access to a rail 93% of the country already uses: keep pricing simple enough that upgrades and overages rarely need to exceed what a customer authorized up front, decide deliberately who eats the 3.5% IOF rather than defaulting into it, and build your access logic to tolerate a multi-day processing state instead of assuming a binary paid-or-failed signal. None of that is a reason to skip Pix Automático for a market this large — treating it like a card with a few extra settings is the mistake, not using it at all.
Where this connects back to the rest of your churn stack: a mandate that silently dies in a customer's banking app, or a prorated charge that fails because it crossed an authorization ceiling nobody flagged at the time, both produce the same thing on your end — a subscriber who disappears without ever telling you why. Running your Pix Automático segment through our churn calculator separately from your card-based churn is the fastest way to see whether that gap is costing you enough to justify the extra billing logic. And for the Brazilian subscribers who do mean to leave on purpose rather than lose access to a failed mandate, CancelFlow's reason capture is what tells you which one actually happened, instead of leaving both to get miscounted as the same generic "payment failed" churn.
Frequently asked questions
What is Pix Automático and how is it different from regular Pix?+
Regular Pix is a one-time, real-time transfer — a customer scans a QR code or pastes a Pix key and the payment clears in seconds, with no standing authorization for a future charge. Pix Automático is the Central Bank of Brazil's separate recurring-payment rail: a customer authorizes a mandate once, inside their own banking app, specifying an amount and billing cycle, and the merchant can then collect against that mandate on a repeating schedule without asking again each time. They share a rail and a brand, but one is a single transfer and the other is closer to a card-on-file token with a hard ceiling baked in.
Can a business based in Brazil use Stripe to accept Pix Automático?+
No. Stripe's own documentation states plainly that Pix Automático isn't available to businesses domiciled in Brazil, even though Brazil-based Stripe accounts can accept one-time Pix payments. Only Stripe accounts based outside Brazil — in dozens of eligible countries across the Americas, Europe, and Asia-Pacific — can collect recurring Pix Automático payments from Brazilian customers. A domestic Brazilian SaaS company selling to domestic Brazilian customers is explicitly locked out of the one Pix feature built for subscriptions.
Why would a Pix Automático payment fail even though the customer has enough money?+
Because the mandate itself caps the amount, independent of the customer's balance. The customer authorizes a specific amount and cycle when they set up the mandate, and any attempt to charge more than that authorized amount simply fails — Stripe's documentation is explicit that exceeding the mandate amount is a payment failure, not something Smart Retries or a dunning sequence can work around. A price increase, a plan upgrade, a usage overage, or a prorated mid-cycle charge can all trigger this exact failure on a customer who has plenty of money in the account the mandate is tied to.
Can you dispute or appeal a Pix chargeback on Stripe the way you can with a card?+
No, and this is a sharper restriction than cards get. Stripe added an API in September 2026 letting merchants appeal a lost card dispute. Pix disputes don't get that option at all: Stripe's documentation says you can't contest a Pix dispute or submit evidence to challenge it, and the partner's decision is final with no appeal path. Pix also doesn't support partial disputes — it's a full reversal or nothing — which raises the stakes of avoiding the dispute in the first place, since there's no partial-win outcome to fall back on.
Stop losing subscribers today
One script tag. One function call. A live cancellation flow in under 10 minutes.
Start free trial →