Code redemptions and bank verification errors

Is the comment more about what should an app do when a customer has an "interrupted transaction"? These interruptions are things like invalid/stale/declined/missing payment info, accepted updated Terms and conditions, PSD2 in EU, Ask to Buy, etc.

In terms of what to do for interruptions, just be sure you are following best practices and ensure your app is always "listening" for transactions immediately on app launch. Meaning not just when customer initiated a buy or restore, but on every app launch on fresh app install or not. Always initialize TransactionObserver with Original StoreKit or transaction.updates with StoreKit2.

Note for those seeing this thread, that redemption URL is only for Promo codes and will not work for Subscription Offer Codes.

Hi and thanks for the reply!

Normal subscription activations, resumes and similar; works just fine and the App manages these without any issues. Errors and Finished transactions.

For some reason the flow that our users follow here seems to break the session, or fail to handle or forward any issues to the App Store /redeem page. The "only" difference is that they initiate the transaction of setting up as sub, from the /redeem page and not a "normal" subscription request.

As for this being "interrupted transactions", we are pretty sure this is not the case as the users claim other purchases and PSD2 verifications work fine.

There are no errors coming from the bank and the users seem to be redirected back to the App Store just as expected after a successful verification with BankID. The issue we are facing is that they just end up on the same page (/redeem) as when the first left our app. No error messages, and they are welcome to just redeem the code again, sadly with the exact same result.

I could visualise the flow like this..

This is what we would expect to happen:

• redeem-page (user confirms offer)
• PSD2 popup displays
• banks page opens
• redirect to BankID App or using external BankID
• redirect back to bank on successful auth
• redirect back to App store to confirm purchase
• redirect back to our App which handles the updated transaction

This is what happens now:

• redeem-page (user confirms offer)
• PSD2 popup displays
• banks page opens
• redirect to BankID App or using external BankID
• redirect back to bank on successful auth
• redirect back to redeem-page where the offer is displayed again.

Sounds like you are reporting a bug that is related to code redemptions that occur in the App Store and not within your application. Can you clarify what types of codes these are? The only codes that come to mind that you can use that redeem url for is "Promo codes". Can you confirm? Also please submit a feedback assistant ticket with as much info as you can. Such as steps to reproduce, example urls's, codes, your app ID, Apple ID's of accounts that ran into this issue, screenshots/recordings, sysdiagnose, etc.http://feedbackassistant.apple.com

Right! Will do an outreach to the affected users to see if they are willing to send us their IDs.

Should we keep this thread and update going forwards, or close it and move it to the feedback issue?

/K

Use feedback assistant to provide details and specifics, especially anything you don’t want public. Share the FB# here once filed and we can update this thread further with our findings so this can be useful for others on the forums.

Hi @kwickell and Apple Engineer! We have the exact same problem as you describe above. Very curious to understand if you managed to find a solution? This information would be very helpful to us.