Create a great in-app purchase experience for your iPhone, iPad, Mac, and Apple Watch apps. Discover how to handle refunds, integrate new App Store server notifications, and find out how to use receipts and server notifications to manage subscriber status. We'll also walk you through the latest updates in StoreKit, including in-app purchases on Apple Watch, Family Sharing, SKOverlay, SKAdNetwork, and more.
with in-app purchases. And we have a lot to cover today. This session will be divided into two sections. I'll focus on covering what's So let's get started with our server updates. On the server side, my mind, if I have an issue with the content and call Apple to request a refund, First a customer purchases some content in an app like 100 Gems. However the purchase was an accident so they call Apple for support. After considering purchases is important for many reasons. Most importantly it gives you control to take action as you see fit. Such as messaging the customer or economy, making game play more fair for all players as there will be repercussions for your other content types with little additional work on your end.
has also been implemented in a privacy friendly way as we're not giving you any information about the customer only information you'd already have about the purchase. The refund notification is live today so if you're already receiving App Store server notifications make sure you're looking for the original_transaction_id to tell you which transaction we've refunded. fields can be found in the unified_receipt object in the App Store server this field to know which app you've received a refund for. Next look in different situation. In this situation the customer still buys 100 gems but then consumes the gems and still asks Apple for support with their purchase. take proactive action such as providing an in-app message in your app. A message In the case of consumables there are additional actions you can take like This solution is also more scalable as you require more subscribers.
payload first look for the auto_renew_product_id to see exactly which product the notification applies to and the product we plan to auto-renew next.
for this customer. Finally look at the pending_renewal_info array to find the upcoming renewal info for each subscription the customer uses billing of the subscription in the billing retry period or grace period.
bringing you an App Store server notification for every successful auto-renew. This is a new notification type which we're calling DID_RENEW. Coming later this year, we'll send you this notification after every single successful auto-renew, every time. Like all the other notifications it contains the the addition of the did renew notification completes our events, bringing you offer before we renew the subscription with that offer. That's why we've added the promotional offer id to the pending renewal info section.
Second schedule a call to verify receipt for your subscription shortly after its to offer a full feature unlock. Customers will choose which in-app purchases that are already set up. Because the use of family is so widely adopted, apps page and select 'Turn On' in the Family Sharing section. Note that once app they will have a transaction available in the transaction queue for for these to be available to all family members. So let's get an idea of only do we put a transaction in the transaction queue for their devices their family, for all of their devices. So when their family members open from their purchase history. For existing purchasers for a shareable subscription to be shared with their family they must opt in from the managed subscriptions
Looking for something specific? Enter a topic above and jump straight to the good stuff.
An error occurred when submitting your query. Please check your Internet connection and try again.