Strong Customer Authentication (SCA) with RevenueCat
Blog post from RevenueCat
Apple has introduced new Strong Customer Authentication (SCA) requirements for in-app purchases in the European Economic Area to combat fraud, necessitating bank or payment provider authentication for certain transactions. While auto-renewable subscriptions require SCA only for the initial transaction and purchases under €30 might be exempt, Apple Pay transactions already meet SCA standards and thus require no further authentication. The customer experience with SCA will involve being redirected outside the app for authentication and returning to complete the purchase, which poses challenges for developers in managing interrupted transactions. Suggestions for developers include implementing the didReceiveUpdatedPurchaserInfo delegate to ensure a seamless user experience by updating subscription statuses in real-time, despite the process potentially affecting conversion rates. Google has yet to announce how SCA will be handled on the Play Store, but developers hope it will integrate smoothly with existing purchase flows.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.