Pix changed: what does it actually require of your app?
Short answer: you probably don't need to rewrite anything, but you do need to check how your app handles pending, declined, and refunded payments. That's where the new rules hit.
Since October 1, 2026, the specific R$ 500 cap on contactless Pix (Pix por aproximação) is gone. On September 18, the Central Bank published BCB Resolution 587, which changes fraud rules, creates what's called hybrid billing (cobrança híbrida), and extends Pix Automático to salary accounts.
Each of these changes touches a different part of the system. It helps to separate what belongs to the customer's bank, what belongs to your payment provider, and what belongs to your code.
The end of the R$ 500 cap on contactless Pix: does it change anything for your app?
Almost nothing, and it's best not to overstate it. Contactless Pix usually happens in the customer's wallet or banking app, not yours. The one who gained flexibility is the payer, who adjusts the limit through their own institution's digital channels.
The thing to watch for is any fixed text or rule in your app that mentions the old amount. Plenty of apps have had a notice like 'payments above R$ 500 are not accepted' written right on the screen, with nobody remembering to review it later.
The second precaution is the reverse: the customer's limit may be lower than the purchase amount, and that still applies. If the payment doesn't go through because of the limit, your app will only notice that the Pix didn't happen. Offer a clear way out on the same screen, such as another payment method or a new QR Code, instead of leaving the user staring at a countdown timer.
BCB Resolution 587: fraud flagging and rejected transactions
The most sensitive part of the resolution is the one that allows flagging CPFs and CNPJs with well-founded suspicion of fraud, for up to five years, and rejecting transactions tied to that flag. This has been in effect since publication. Notifying the customer about the flag, according to coverage of the topic, only kicks in in February 2027.
For app owners, the consequence is simple: a rejected transaction stops being a rare case and becomes a normal state in the flow. The most common mistake is treating everything that isn't 'paid' as a technical failure and telling the user to try again, over and over, with no explanation.
What to do: in your code, distinguish between a decline caused by the payer, an expired charge, and an error on your side. Show a different message for each case and keep a support channel close at hand. A customer who pays and doesn't see the order confirmed just wants to know who to talk to.
Confirmation and refunds: never trust the user's click
Since February 2026, MED 2.0 has been mandatory for financial institutions, and it can track the path of the money across several accounts in a row when there's a scam. On the receiving end, this means a confirmed Pix can, in fraud cases, be refunded later.
If your app releases a product, credit, or access the moment the user taps 'I already paid,' you're exposed. Confirmation needs to come from the payment provider, usually through a webhook, and your system needs to keep the history of each charge: created, paid, expired, refunded.
In practice, this calls for two business decisions before the technical one. How long do you wait before releasing something high-value, such as a physical product being shipped or an expensive service? And what happens to the customer's access when the payment is refunded? Put that in writing, then ask the team to implement it.
Hybrid billing and Pix Automático: what to expect in 2027
Hybrid billing combines boleto and Pix in a single charge with a due date: the customer chooses how to pay. Once the boleto is paid, the matching Pix is canceled, and if a Pix arrives afterward, it is rejected or returned to the payer. Offering it is optional for the institution, which must also be the boleto issuer.
As for dates, sources disagree. Most coverage points to February 1, 2027 for hybrid billing, but some say the official summary doesn't give a specific date. Confirm with your bank or provider before planning anything.
Pix Automático on salary accounts, on the other hand, is scheduled for July 1, 2027. This widens where the debit can come from, but it doesn't remove the customer's prior authorization. If your business charges a monthly fee, the authorization and cancellation flow remains the core of the project.
My recommendation: don't build anything on top of hybrid billing until your bank or provider says it offers it. But do design the system now with a single status per charge, queried by any payment channel. That avoids rework when the new feature arrives.
An afternoon checklist to review your app's payments
You don't need a big project for this. Sitting down with whoever built the app and going through these points already takes care of most of the risk.
If your app is still on paper and payment is a central piece, the best time to test these decline, pending, and refund screens is before writing any code. At SKAD, the R$ 99 clickable prototype is made for exactly that: seeing these flows in action and deciding what needs to exist in the first version.
- Look in the app for fixed texts or rules that cite the old R$ 500 limit.
- Check that there's a clear screen for expired, declined, and pending Pix, each with its own message.
- Verify that order release depends on the provider's confirmation (webhook), not on the user's click.
- See whether the system keeps the history of each charge, including refunds.
- Define in writing what happens to access or the order when a payment is refunded.
- If you charge on a recurring basis, review the Pix Automático authorization and cancellation flow.
- Ask your bank or provider when and whether they will offer hybrid billing.
Frequently asked questions
Is the R$ 500 limit on contactless Pix really gone?
Yes. Since October 1, 2026, the specific R$ 500 cap for this type of payment no longer exists, and customers now adjust the limit through their financial institution's digital channels.
Do I need to change my app's code because of BCB Resolution 587?
It depends on how payment was built. If your app confirms payments by webhook, handles declines and refunds, and keeps the charge history, the change tends to be small. If it releases everything on the user's click, it's worth reviewing.
What is hybrid billing in Pix?
It's a charge with a due date that can be paid by either Pix or boleto. When one of the two is paid, the other is canceled to prevent duplicate payment.
Will Pix Automático work with salary accounts?
It's scheduled for July 1, 2027. The customer will still need to authorize the recurring charge beforehand.
Conclusion
Before thinking about any new feature, set aside an afternoon to simulate three situations in your own app: a Pix that expires, a Pix that is declined, and a payment refunded after being confirmed. If any of them leaves the user without an answer or releases something it shouldn't, start there. Hybrid billing and Pix Automático on salary accounts can wait until your bank or provider confirms the dates.