In app purchase with first transaction

Question

Created Jun ’20

Replies 1

Boosts 0

Participants 2

Hi team,
I building a charge coin feature in my app (In-app purchase). Everything seems OK but I have 1 issue with the first transaction.

My case is:
1. User A doesn't fill payment information (VISA card) on the apple store.

2. User A opens my app and executes the Charge coin feature.

3. My app shows a popup payment of Apple store.

4. Apple store detects user A doesn't have payment information and goes to the payment information screen.

5. User A fill all payment information success. Apple store auto-execute pending transaction and show transaction success on Apple store.
6. User A goes to back my app, then Swiftystorekit shows transaction error.

7. On my server (Nodejs server) can't hear that transaction success to verify that transaction and add coins to Wallet of User A.

8. On my app can't receive any receipt to send to my server for verifying that transaction and add coins to Wallet of User A.

And I want that transaction can be verified by my server but I don't have any solution for that. I have 2 questions:

1. How to my app can receive a receipt of a transaction that is executed on apple store?

2. How to my server can hear transaction is executed on apple store?
Please help me find a solution for that case, this is an urgent issue with me?
Thank you so much!

Boost

Answer 1

PBK OP

Jun ’20

TMI.

In the scenario you describe StoreKit will send your updatedTransactions method two transactions, one immediately after the other. The first will have a state of 'failed' because the user's credit card information needed to be updated. The second will have the state 'purchased' because the user decided to go ahead with the purchase after updating their credit card information. Your code needs to handle both.

A common problem is code that removes the transaction observer and the class that handles the IAP immediately after getting the failed transaction. One solution is to leave the observer and class in memory permanently (Apple recommends this solution!). Another solution is to delay removing them for a few seconds after a failed transaction.

Usually the code allows the user to 'restore' their purchases. That will 'fix' this problem should it occur in a production app.

0