In-App Purchase Programming Guide - Apple Developer

More documents

Recommendations

Info

Working with Subscriptions Cancellation Note: Increasing the price of a subscription doesn’t disable automatic renewal for all customers, only for those customers whose subscription expires in the next ten days. If this change is a mistake, changing it back to the original price means no additional users are affected. If this change is intentional, keeping the new higher price causes automatic renewal to be disabled for the rest of your users in turn as they enter the ten-day renewal window. During the 24-hour period before the subscription expires, the App Store starts trying to automatically renew it. The App Store makes several attempts to automatically renew the subscription over a period of time but eventually stops if there are too many failed attempts. The App Store renews the subscription slightly before it expires, to prevent any lapse in the subscription. However, lapses are still possible. For example, if the user’s payment information is no longer valid, the first renewal attempt would fail. If the user doesn’t update this information until after the subscription expires, there would be a short lapse in the subscription between the expiration date and the date that a subsequent automatic renewal succeeds. The user can also disable automatic renewal and intentionally let the subscription expire, then renew it at a later date, creating a longer lapse in the subscription. Make sure your app’s subscription logic can handle lapses of various durations correctly. After a subscription is successfully renewed, Store Kit adds a transaction for the renewal to the transaction queue. Your app checks the transaction queue on launch and handles the renewal the same way as any other transaction. Note that if your app is already running when the subscription renews, the transaction observer is not called; your app finds out about the renewal the next time it’s launched. Cancellation A subscription is paid for in full when it’s purchased and can be refunded only by contacting Apple customer service. For example, if the user accidentally buys the wrong product, customer support can cancel the subscription and issue a refund. It’s not possible for customers to change their mind in the middle of a subscription period and decide they don’t want to pay for the rest of the subscription. To check whether a purchase has been canceled, look for the Cancellation Date field in the receipt. If the field has a date in it, regardless of the subscription’s expiration date, the purchase has been canceled—treat a canceled receipt the same as if no purchase had ever been made. Depending on the type of product, you may be able to check only the currently active subscription, or you may need to check all past subscriptions. For example, a magazine app would need to check all past subscriptions to determine which issues the user had access to. 2013-10-22 | Copyright © 2013 Apple Inc. All Rights Reserved. 36
Working with Subscriptions Cross-Platform Considerations Cross-Platform Considerations Product identifiers are associated with a single app. Apps that have both an iOS and OS X version have separate products with separate product identifiers on each platform. You could let users who have a subscription in an iOS app access the content from an OS X app (or vice versa), but implementing that functionality is your responsibility. You would need some system for identifying users and keeping track of what content they’ve subscribed to, similar to what you would implement for an app that uses non-renewable subscriptions. The Test Environment For the sake of testing, there are some differences in behavior between auto-renewable subscriptions in the production environment and in the test environment. Renewal happens at an accelerated rate, and auto-renewable subscriptions renew a maximum of six times per day. This lets you test how your app handles a subscription renewal, a subscription lapse, and a subscription history that includes gaps. Because of the accelerated expiration and renewal rate, the subscription can expire before the system starts trying to renew the subscription, leaving a small lapse in the subscription period. Such lapses are also possible in production for a variety of reasons—make sure your app handles them correctly. 2013-10-22 | Copyright © 2013 Apple Inc. All Rights Reserved. 37
Page 1 and 2: In-App Purchase Programming Guide
Page 3 and 4: Contents Persisting the Purchase 25
Page 5 and 6: About In-App Purchase In-App Purcha
Page 7 and 8: About In-App Purchase See Also Rele
Page 9 and 10: Designing Your App’s Products Cre
Page 11 and 12: Designing Your App’s Products Dif
Page 13 and 14: Retrieving Product Information Gett
Page 15 and 16: Retrieving Product Information Retr
Page 17 and 18: Retrieving Product Information Sugg
Page 19 and 20: Retrieving Product Information Sugg
Page 21 and 22: Requesting Payment Detecting Irregu
Page 23 and 24: Delivering Products In the final pa
Page 25 and 26: Delivering Products Persisting the
Page 27 and 28: Delivering Products Persisting the
Page 29 and 30: Delivering Products Delivering Asso
Page 31 and 32: Delivering Products Finishing the T
Page 33 and 34: Delivering Products Suggested Testi
Page 35: Working with Subscriptions Expirati
Page 39 and 40: Restoring Purchased Products Refres
Page 41 and 42: Preparing for App Review After you
Page 43 and 44: Preparing for App Review Implementa
Page 45 and 46: Document Revision History Date 2011

In-App Purchase Programming Guide - Apple Developer

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?