Pix tap-to-pay on iPhone in Brazil still has no launch date as Apple and CADE remain at odds

Brazil’s plan to bring Pix tap-to-pay to the iPhone is still stuck in regulatory and technical negotiations, with no launch date set. For PSPs, acquirers, and banks watching high-risk payments, the point is simple: Apple’s control over NFC on iPhone is still the gatekeeper issue.

1. The implementation of Pix tap-to-pay on iPhone in Brazil is facing regulatory obstacles and has no defined date. The dispute centers on differences between Apple and CADE, Brazil’s antitrust regulator, in a case that started in April 2025 over alleged anticompetitive practices.
2. In California, Apple executives reportedly acknowledge ongoing conversations with Brazilian authorities, but say there is still “much work” to be done. The company remains unwilling to open its platform to third parties while it sees regulatory and technical questions as unresolved.
3. Apple told CADE in February that it wants the right to charge third parties for licensing the technology needed to support Pix tap-to-pay. At the center of the fight is access to the NFC chip, which is necessary to complete the transaction.
4. On Android, Google allows apps free access to the NFC chip. On iPhone, third-party use by banks and fintechs has to go through Apple Pay, the NFC chip, and the SE Element chip, and the article says each Pix transaction generates micropayments for Apple.
5. Apple says it does not want to give up that fee structure and accuses rivals such as Nubank, Zetta, Mercado Pago, PicPay, and PayPal of trying to cut their own costs. The company also raises security and privacy concerns, saying NFC opening could expose user data and create new vulnerabilities, especially when payments are involved.

For high-risk payment operators, the commercial detail matters as much as the regulatory one: Pix moved R$ 35,36 trilhões in 2025, so any delay in iPhone access is not a side issue, it is a distribution problem with fees, control of the checkout flow, and platform dependency all baked in.