Timely registration will help you avoid missing any transaction states. The email arrives stating confirmation of the purchase and invites you to check the attached PDF document for details. An email phishing campaign has been seen doing the rounds, which is targeting Apple users by pretending to be a receipt for a purchased item on the app store. To ensure this data stream, you need to register a transaction observer as soon as possible after you launch your app. Apple ID Phishing Campaign Tricks Users with Fake App Store Receipts. This information is received from the updatedTransactions callback.

We need to use the StoreKit framework which is a part of iOS SDK to get all information on transactions (including status, id, and any errors that may occur). So choose this type of validation if you need a purchase to be available in one iOS platform app only. But purchases validated on a device won’t be available on your site or in your Android app, for instance. On-device purchase validation is suitable if all purchases are processed locally on one iOS device. In this article, we’ll describe both options for validating purchases and help you choose the most appropriate one depending on your needs and your app infrastructure. You don’t need any paid resources to implement each of both solutions. You can alternatively use on-device validation to unlock in-app features and content with no need to connect to your server. However, is server-to-server purchase validation really the only way to go? No. Why? Because your app will recognize and trust your own server, allowing you to control all transactions between your server and user devices.

Using your own server to communicate with the App Store is generally the best option for validating purchases in your application. But all in-app purchases need to be validated. As we know, Apple lets users purchase goods and services in apps using their Apple IDs.

Fake app store receipt