Strong Customer Authentication (SCA) and In-App Purchases: A Practical Guide
Strong Customer Authentication (SCA) adds a bank or payment-provider verification step to certain in-app purchases in the European Economic Area. The requirement is designed to reduce online payment fraud, but it also changes the purchase journey: a customer may leave your app to authenticate, and the transaction may complete later in the background. This guide explains the scope of SCA, the customer experience, and the practical steps for keeping your app's subscription state accurate.
When SCA applies to in-app purchases
SCA requirements apply to certain in-app purchases in the European Economic Area. The bank or payment service provider must authenticate the transaction before it can be completed. The following conditions shape whether a purchase is likely to require SCA:
- For auto-renewable subscriptions, SCA is required only for the first transaction.
- Purchases under €30 may not require SCA.
- Purchases made with Apple Pay, which already meets SCA requirements, will not require additional authentication.
- A purchase settled through mobile phone billing, another payment service, or an Apple ID balance topped up by gift card or Apple Wallet skips the extra authentication step.
These are the conditions described in Apple's guidance at the time. The €30 threshold is a qualification, not a guarantee: a purchase under €30 may still be subject to authentication depending on the payment method and provider. Treat the threshold as a screening rule, not a promise that every small purchase will skip SCA.
For the full regulatory context, see Apple's SCA support page.
What the SCA customer experience looks like
Apple's guidance describes a general flow rather than a fully testable one. At the time the guidance was published, the behavior could not be tested in sandbox, so the exact customer experience was not known in advance. The described flow is:
- The purchase flow inside your app pauses, and the customer is routed to their bank or payment service provider's website or app to authenticate.
- Once the purchase is confirmed outside your app, the customer returns to your app and sees an Apple message confirming the purchase was completed.
The difficulty for developers is that the customer leaves your app to complete the transaction. You are left with several unknowns: whether the user will return, whether they will return without completing the transaction, and whether the transaction will complete later that day or next week.
A typical purchase implementation shows an error alert when the purchase attempt returns an error. With SCA, that error may appear while the customer is being redirected away from the app to complete the transaction. If the transaction later completes successfully outside the app, the purchase-completed handler has already fired with an error. The transaction is still recorded in the background, but the customer may have to close the paywall manually and possibly refresh the page to pick up the latest subscription status. The app may still work, but the experience can feel clunky.
Failed, deferred, and pending: a useful distinction
SCA introduces a state that looks like a failure but is not the same as a declined purchase. Apple's guidance compares the interrupted transaction to Ask to Buy purchases that need approval from a family approver, or to the case where a user must agree to updated App Store terms and conditions before completing a purchase. In those situations, the payment queue can update with a state of "failed" or "deferred" as the user exits the app.
This distinction matters for your UI and your subscription logic:
- A failed purchase is a terminal outcome for that attempt. The customer should see an error and can try again.
- A deferred or pending purchase is an open transaction. The customer may complete it outside the app, and your app should be ready to refresh subscription status when the transaction resolves.
- A purchase that completes in the background is a success even if the original attempt returned an error. Your app should not treat the earlier error as the final word.
On Android, Google had not released guidance on handling SCA in the Play Store at the time. The hope was that SCA would be handled automatically in the native in-app purchase flow. If it is not, the behavior may resemble Google pending transactions, which are already supported.
Implementation checklist for SCA-ready purchases
The goal is to keep the app's subscription state accurate when a purchase completes outside the normal purchase flow. A practical checklist:
- Set up a notification that fires when the purchaser info changes. On iOS, this can be done in the AppDelegate by setting the Purchases delegate after configuring Purchases and posting a notification from the didReceiveUpdatedPurchaserInfo delegate.
- Add an observer for that notification on the paywall so the paywall can dismiss when the purchase completes.
- Add an observer on the main view controller so the main view refreshes to show the premium state if the customer dismisses the paywall before the notification fires.
- In the observer's update function, fetch the latest purchaser info and update the view based on the subscription status.
- Remove the observer when the view is deallocated.
The same concepts apply to iOS and Android. Your app's structure determines how much of this applies: some apps need every step, others only a subset, and apps with several view controllers may need the same observer pattern in more than one place. Handling specific errors around pending payments differently, or showing a dismissible banner indicating a pending payment was initialized, is optional. The extra development and testing may not be worth it if the small changes already made provide a large improvement.
Worked example: a purchase that completes after the app shows an error
Consider a customer who taps a subscribe button on the paywall. The purchase attempt returns an error, and the app shows an alert. The customer is redirected to their bank's app to authenticate. They complete authentication and return to your app, where Apple shows a message confirming the purchase.
In the meantime, the original purchase attempt has already returned an error. If the app relies only on the purchase-completed handler, it may not update the paywall or the main view. The customer sees a completed purchase message from Apple but the app still shows the non-premium state.
With the notification-based approach, the purchaser info change fires the didReceiveUpdatedPurchaserInfo delegate. The AppDelegate posts the kPurchaserInfoUpdated notification. The paywall observer dismisses the paywall, and the main view observer fetches the latest purchaser info and updates the premium state. The customer sees a consistent result even though the original attempt returned an error.
This example uses the source's own captured scenario. The exact timing and behavior of SCA transactions may vary by bank, payment method, and platform.
What SCA may mean for conversion
With many unknowns about when and how SCA triggers an authentication flow, the impact on conversion rates is difficult to predict. It seems likely that SCA will decrease conversion rates somewhat. How much, and whether the impact will be significant, probably will not be clear for many months.
The practical response is to remove as much friction as possible. A great product that people want to buy will still find buyers, but a clunky purchase experience can lose customers who would otherwise have completed the transaction. The notification-based approach described above is one way to reduce that friction.
Frequently asked questions
Does SCA apply to every subscription renewal?
No. For auto-renewable subscriptions, SCA is required only for the first transaction. Renewals do not require a new authentication step under the described guidance.
Are all purchases under €30 exempt from SCA?
Purchases under €30 may not require SCA. This is a qualification rather than a guarantee, so a purchase under €30 can still be subject to authentication depending on the payment method and provider.
Does Apple Pay require an additional SCA step?
No. Apple Pay already meets SCA requirements, so purchases made with Apple Pay will not require additional authentication.
How should Android apps handle SCA?
At the time of the guidance, Google had not released information on handling SCA in the Play Store. The hope was that SCA would be handled automatically in the native in-app purchase flow. If it is not, the behavior may resemble Google pending transactions, which are already supported.
Can SCA behavior be tested in sandbox?
At the time the guidance was published, there was no way to test the SCA behavior in sandbox. The exact customer experience was not known in advance, and Apple provided only general information about the flow.
If a purchase returns an error during SCA, does that mean the purchase failed?
Not necessarily. The payment queue can update with a state of "failed" or "deferred" as the user exits the app. A deferred or pending transaction may still complete outside the app, so the app should refresh subscription status when the transaction resolves rather than treating the earlier error as final.