Pix Automático: Solving SaaS Recurring Billing in Brazil

Pix Automático is the direct automatic debit modality via Pix launched by the Central Bank of Brazil that allows a company to debit recurring amounts from a customer's account with prior authorization, without requiring the customer to enter a password for each charge. For SaaS, it solves the biggest invisible cost of revenue operations in Brazil: involuntary churn.

What is Pix Automático?

It is a feature of the Pix ecosystem that enables recurring billing with prior payer authorization. It works like traditional direct debit, but operates on Pix rails: instant settlement, 24 hours a day, 7 days a week availability, with no card network intermediary.

The Central Bank announced the feature in June 2024. It launched on June 16, 2025 and became mandatory from October 2025 for all financial institutions. The technical mechanism is simple: the customer authorizes once, through any digital channel (banking app, SaaS interface, enrollment link), and future charges debit automatically on the defined recurrence (weekly, monthly, quarterly, annual), without the customer needing to take any additional action.

For the SaaS sector, this solves three problems simultaneously: expired cards interrupting subscriptions, boleto bills customers forget to pay, and re-authentication friction at every cycle.

Why Does Traditional Recurring Billing Break in Brazil?

The Brazilian payments market was built on two rails that were never designed for software recurrence: credit cards and boleto bancário. Both work well for one-off purchases. Both systematically fail when the operation demands continuity.

Credit cards in Brazil have a first-attempt approval rate around 70%. That means 30% of recurring charges fail on the first pass. The reasons are multiple and structural: maxed-out limits, cards blocked on fraud suspicion, card networks rejecting transactions due to issuer risk policies, disabled virtual cards. The Brazilian card market has one of the highest decline rates in Latin America, and the problem worsens in cross-border transactions, where local issuers frequently block charges from international acquirers as a default security policy.

The second card problem is the renewal cycle. Approximately 25 to 30% of active cards expire each year. When a card expires, the charge fails. The customer needs to update the data manually. A significant share simply does not update, not because they want to cancel, but because the action is not a priority in the daily workflow of the CFO or head of operations. SaaS loses revenue without the customer having made the decision to leave.

Boleto is even worse for recurrence. Brazilian market data indicates that between 40% and 50% of issued boletos are never paid. Boleto requires the customer to open the banking app, copy the barcode, and confirm payment. Every month. In a B2B operation with dozens of software subscriptions, boleto is a machine for producing delays and involuntary non-payment.

Traditional direct debit exists, but its adoption in the Brazilian SaaS market is residual. The reason is simple: integration with each bank demands a bilateral agreement, the authorization process is analog (physical form, manual validation), and settlement takes 1 to 3 business days. For an international SaaS company without a local entity, it is unworkable.

The consequence of operating with card and boleto as the only options is that Brazilian SaaS loses between 20% and 30% of its annual recurring revenue to involuntary churn: customers who wanted to keep paying but whose payment method failed.

What Is the Real Impact of Involuntary Churn on SaaS Revenue?

Involuntary churn is the revenue that disappears without the customer having canceled. It is the card that expired and nobody updated. It is the boleto that passed due and nobody paid. It is the transaction blocked by the issuer on fraud suspicion for a legitimate charge.

The cumulative impact is brutal. Consider a B2B SaaS with 500 customers and an average ticket of R$ 2,000 per month, generating R$ 1 million in monthly recurring revenue. With an involuntary churn rate of 2.5% per month, the business loses R$ 25,000 per month that it should not lose. Over 12 months, that is R$ 300,000 in revenue that walked away without a single customer deciding to leave.

Over a three-year horizon, the compounding effect is even more devastating. Voluntary churn is already hard to fight: it demands better product, better support, better pricing. Involuntary churn is different: the customer is satisfied and wants to continue, but the transaction fails due to an operational problem the SaaS does not control.

Pix Automático attacks exactly that category of loss. Prior authorization eliminates the need for customer action on every charge. No password. No card to expire. No boleto to forget. No issuer to block. The debit is direct to the account, scheduled, recurring.

SaaS companies operating in markets with mature direct debit (United States, Europe) live with involuntary churn rates below 5% per year. In Brazil, the same company operating with card and boleto loses 20% to 30%. The difference between one market and another is not in customer behavior. It is in the payment infrastructure.

How Does Pix Automático Work in Practice for Subscription Billing?

The flow of a recurring charge via Pix Automático follows four stages:

1. Enrollment. The customer authorizes the automatic debit a single time. The authorization can be done through the banking app, a link sent by the SaaS, or embedded in the subscription checkout. The customer selects the debit account, defines the maximum allowed amount, and the billing frequency. The authorization is registered in the DICT (Directory of Transactional Account Identifiers), the centralized Pix database.

2. Scheduling. The SaaS programs the recurrence: monthly, quarterly, annual. The SaaS billing system sends the debit instruction to the PSP (Payment Service Provider) or directly to the SPI (Instant Payment System) on the scheduled date.

3. Settlement. The amount is debited from the customer's account and credited to the SaaS account in real time. Settlement is instant: the money is available in seconds, not days. No card network intermediary holds the value for 30 days.

4. Confirmation. The SaaS receives debit confirmation in real time. If the customer's account lacks sufficient balance, the system can configure automatic retry rules (for example, retry 48 hours later), further reducing the failure rate.

The Pix Automático architecture solves the three failure points of traditional recurring billing:

• Expired card? Does not exist. The debit is to the current account.
• Card blocked by issuer? There is no issuer. The transaction goes directly on the Pix rail.
• Unpaid boleto? There is no boleto. The debit is automatic.

The authorization is revocable by the customer at any time, directly through the banking app. This keeps control in the payer's hands, a regulatory requirement the Central Bank made a point of preserving.

Pix Automático vs Credit Card vs Boleto: Which Is the Best Option for Recurrence?

The choice of payment method for recurring billing determines how much of your revenue you actually receive. The comparison below considers the B2B SaaS scenario in Brazil:

The table reveals what the involuntary churn numbers already indicated: for recurrence, credit card is fragile, boleto is unworkable, and Pix Automático is the first Brazilian infrastructure designed specifically for recurring billing.

No SaaS should abandon credit cards as a payment option. A good share of enterprise customers prefers to pay with corporate cards, centralize spending in a single statement, and accumulate points. The point is not to replace, but to complement. Pix Automático serves as the primary billing method to reduce churn, with card as an alternative for those who prefer it, and boleto only for exceptional cases of annual upfront billing.

How Much Does It Cost to Implement Pix Automático in a SaaS?

The implementation cost of Pix Automático is structurally lower than that of a credit-card-based solution, for two reasons: there is no interchange (the fee paid to the network and issuer, which represents 60% to 80% of the total cost of a card transaction) and instant settlement eliminates the cost of receivables anticipation.

The cost components are:

• PSP (Payment Service Provider) fee: the PSP that processes Pix Automático transactions charges a flat fee per transaction or a reduced percentage. Since Pix operates on Central Bank infrastructure, with no card network or acquirer as a mandatory intermediary, the marginal cost is significantly lower than that of a card transaction.

• Technical integration: the SaaS needs to integrate the chosen PSP's API to schedule, process, and confirm recurring debits. The development effort varies by PSP but is comparable to a traditional payment gateway integration (1 to 3 weeks of development, depending on the complexity of the billing logic).

• Authorization management: the architecture requires an enrollment flow (the customer authorizes once) and an authorization management system (revocation, limit change, account switch). Most PSPs offer ready-made tools for this management.

For an international SaaS company without a local entity in Brazil, the additional cost is the Merchant of Record (MoR) structure or local PSP acting as a fiscal representative. This cost exists regardless of the payment method (card, boleto, or Pix Automático) and is justified by the elimination of the 20-30% involuntary churn that Pix Automático solves.

The payback is direct: if the SaaS loses R$ 300,000 per year in involuntary churn and implementing Pix Automático costs R$ 50,000 (integration + first year of operation), the return on investment comes in under three months of operation.

What Are the Risks and Limits of Pix Automático That Every SaaS Operation Needs to Know?

Pix Automático solves the structural problem of involuntary churn, but it is not a silver bullet. There are operational risks and regulatory limits that deserve attention.

Insufficient balance. The automatic debit fails if the customer's account lacks balance at the time of billing. The difference versus cards is that there is no block due to fraud suspicion, no method expiration, and the retry can be programmed automatically. A well-configured SaaS defines retry rules (for example, 2 days later, then 5 days, then 10 days) and notifies the customer before each new attempt.

Value limit. The Central Bank may establish value limits per transaction or per period for Pix Automático, similar to what already exists for nighttime traditional Pix transactions. The exact limits will be defined in complementary regulation. For B2B SaaS with tickets above R$ 10,000 per month, it is prudent to verify whether the regulatory limit covers the average ticket of the base.

Unilateral revocation. The customer can revoke the authorization at any time, directly through the banking app. This is a legitimate consumer protection, but it creates the risk of the SaaS discovering the cancellation only when the next charge fails. The solution is technical: revocation notification webhooks that the PSP must offer, allowing the SaaS to act proactively (notify the customer, offer an alternative method) before the charge fails.

PSP dependency. The quality of Pix Automático implementation depends on the chosen PSP. Some PSPs will have complete webhooks for revocation notification and configurable retry. Others will have minimal implementations. The choice of payment infrastructure partner is as important as the decision to adopt Pix Automático.

Base migration. For a SaaS with hundreds or thousands of active customers, migrating the card and boleto base to Pix Automático is a payment method change operation. It demands clear communication (the customer needs to authorize the new method), a staggered enrollment campaign, and a transition period where both methods coexist. You do not migrate an entire base in one week.

How Can International SaaS Companies Use Pix Automático to Sell in Brazil?

SaaS companies headquartered outside Brazil that sell to Brazilian customers face a two-layer problem: the friction of recurring billing (cards that fail, boletos that go unpaid) and the structural barrier of not having a local entity (no CNPJ, no Brazilian bank account, no direct access to Pix).

Pix Automático solves the first layer. But to access it, the international company must solve the second: the cross-border payments guide for SaaS B2B in LatAm details each route of entry into the Brazilian market.

There are three routes:

1. Opening a local entity. Establish a CNPJ in Brazil, open a bank account, hire a local PSP, integrate Pix Automático. This is the highest-control route, but also the highest-cost and highest-complexity: the process takes 3 to 6 months, demands local accounting, nota fiscal issuance, and tax compliance structure. For a SaaS with Brazilian revenue below USD 500 thousand per year, the fixed cost of the local entity often makes the operation unviable.

2. Cross-border PSP with Pix. Some international payment providers already offer Pix as a payment method without requiring a local entity, operating as payment facilitators. However, most of these solutions do not support Pix Automático (recurrence), only traditional Pix (one-off transaction with QR code or key). For recurrence, the gap remains. For a complete overview of cross-border payment challenges in Latin America, see our cross-border payments guide for SaaS B2B.

3. Merchant of Record (MoR) with local infrastructure. An MoR established in Brazil acts as the legal seller of the transaction. It has a CNPJ, issues nota fiscal, processes payments on behalf of the international SaaS using local methods (Pix Automático included), withholds the applicable taxes, and remits the net revenue to the company abroad. The SaaS signs a contract with the MoR, integrates the API, and starts processing recurring charges as if it were a local company, without being one.

Nexforce Marketplace operates precisely on this third route. For an international SaaS selling in Brazil, the platform offers the complete local payment infrastructure: processing via Pix Automático, credit card with intelligent routing to maximize approval, and boleto, with nota fiscal issuance for the end customer and cross-border settlement in USD or EUR. The international company integrates one API and starts billing recurring subscriptions in Brazil with the same success rate as a local company.

The operational difference is measurable. A SaaS analytics product sold at USD 500 per month to 200 Brazilian customers, billing via cross-border credit card, loses about 25% of annual revenue to involuntary churn: USD 300,000 per year. With Pix Automático via MoR, the billing failure rate drops below 5%, recovering USD 240,000 per year in revenue that previously vanished without a single customer having canceled.

FAQ

Is Pix Automático already live?

Yes. Launched on June 16, 2025 and mandatory since October 13, 2025. Companies that have not yet integrated are operating at a competitive disadvantage. See the complete guide on Pix Automático for recurring payments. For every month without Pix Automático, involuntary churn continues draining 20% to 30% of recurring revenue.

What is the difference between Pix Automático and traditional direct debit?

Three key differences. See the complete guide to Pix Automático for recurring payments for an in-depth analysis. First: Pix Automático operates on Pix infrastructure (SPI), with instant settlement 24/7, while traditional direct debit operates on CIP (Interbank Payments Chamber), with settlement in D+1 to D+3 business days and only on business days. Second: Pix Automático authorization is digital and integrated into banking apps, while traditional direct debit often requires physical forms and manual validation. Third: Pix Automático is nationally standardized by the Central Bank, while traditional direct debit depends on bilateral agreements between each company and each bank.

Does Pix Automático work for international charges?

Not directly. Pix Automático operates within the Brazilian financial system, in reais (BRL). For an international company to receive the funds, an intermediary structure is needed (MoR or PSP with cross-border settlement) that processes Pix Automático locally and handles the subsequent international remittance. Nexforce Marketplace offers exactly this structure.

Can the customer cancel the Pix Automático authorization?

Yes, at any time, directly through the banking app. The Central Bank requires the payer to have full control over active authorizations. For the SaaS, this means it is essential to implement revocation notification webhooks to act before the next charge fails.

Does Pix Automático replace credit cards for SaaS?

No. Pix Automático complements credit cards as an additional recurring billing method, not as a replacement. Many enterprise customers prefer to pay with corporate cards for cash flow reasons, points accumulation, or internal purchasing policies. The correct strategy is to offer Pix Automático as the primary method (lower churn, lower cost) and card as an alternative, with intelligent routing that tries Pix Automático first and falls back to card in case of failure or customer preference.

How much does a Pix Automático transaction cost compared to a card transaction?

A credit card transaction in Brazil costs between 2% and 4% of the transacted value, of which 60% to 80% is interchange (fee paid to the card issuer). A Pix Automático transaction, operating on Central Bank infrastructure with no issuer and no card network, has a structurally lower cost. PSPs should price Pix Automático with flat per-transaction fees or reduced percentages, in the range of 0.5% to 1.5%, depending on volume. For a SaaS with an average ticket of R$ 2,000 and 500 charges per month, annual savings on payment fees can exceed R$ 100,000.

---

Pix Automático solves a problem the Brazilian SaaS market accepted as inevitable: losing 20% to 30% of revenue to billing failures that have nothing to do with the product, the price, or customer satisfaction. It is an infrastructure correction, not a strategy correction. Companies that have already implemented it are capturing the difference. Those who have not are funding their competitors' churn.

For international SaaS companies selling in Brazil, the path goes through a local infrastructure partner that operates as Merchant of Record and offers Pix Automático integrated with cross-border settlement. Nexforce Marketplace exists for this function: processing recurring payments in Brazil with the methods the Brazilian customer uses, settling in USD or EUR for the international operation, and eliminating the revenue gap that involuntary churn creates.

The question is not whether Pix Automático has already changed SaaS recurrence in Brazil. It is how much of your current revenue is disappearing while you postpone adoption.

References and Further Reading

• Banco Central do Brasil, Pix Automático FAQ
• BCB Resolution No. 401/2024
• DICT, Directory of Transactional Account Identifiers