Developer Console
Sign In
Sign In
Developer Console

Quick Subscribe FAQ

The following are frequently asked questions (FAQ) about Quick Subscribe.

General Quick Subscribe FAQ

Q: If I integrate with Quick Subscribe, do I need to add support for account information sharing?
Yes, to help you with account creation and sign-in, Amazon passes the customer details (email, first name, last name, and zip code) to you.
Q: What happens if a customer purchases a subscription through Quick Subscribe and wants to download the app on a second device?
The subscription is added to the customer's account after they subscribe through Quick Subscribe. Customers can use the "app only" option to download the app on additional devices. Customers can then access their subscription on those devices.
Q: Can I perform A/B testing for Quick Subscribe?
Yes, Quick Subscribe supports A/B testing. You can contact your Amazon representative to set up the test experiment.
Q: Why are all receipts returned when I call getPurchaseUpdates() with false in Live App Testing (LAT)?
If you have enabled accelerated subscriptions, all receipts are returned. If you turn off accelerated subscriptions, you will no longer have all receipts returned when you call getPurchaseUpdates() with false.
Q: What version of Amazon Appstore supports Quick Subscribe?
To properly test Quick Subscribe, you must use Appstore version release-8.5026 or later. If you are seeing intermittent sync issues with getPurchaseUpdates(), verify you are using a supported version of Amazon Appstore.
Q: What marketplaces are Quick Subscribe available in?
Quick Subscribe is available in all marketplaces except India (IN).

One-click account information sharing FAQ

Q: What is the difference in the customer experience between Quick Subscribe with one-click account information sharing and Quick Subscribe without the feature?
Quick Subscribe with one-click account information sharing enables the customer to share their Amazon account information with your app in a one-click process. In Quick Subscribe without this feature, the customer has to manually sign up for an account to use your service.
Q: When I update my app to support Quick Subscribe with one-click account information sharing, what happens if a customer is using an older version of my app without the feature?
Customers who can't update the app to your latest version can use your previous implementation of Quick Subscribe that doesn't support one-click account information sharing.
Q: What is the difference between the Acknowledge Receipt API and the notifyFulfillment() method? Do I need to integrate with both?
The notifyFulfillment() method is included in the Appstore SDK on the client-side, and confirms fulfillment of an item by sending a fulfillment result to Amazon. The Acknowledge Receipt API achieves the same objective but through a server-to-server call using the acknowledgeReceipt operation.

You must use at least one of these methods in your app to communicate the fulfillment result to Amazon. If you've already integrated with the Acknowledge Receipt API, you can continue to use it, however using notifyFulfillment() is the preferred method. You can also choose to use both the Acknowledge Receipt API and notifyFulfillment() in your app.

Q: What if I need information in addition to email, name, and zip code to create an account?
If you need additional information, your app must request the required information from customer.
Q: Do legacy SDKs support one-click account information sharing?
No. You must integrate with the Appstore SDK to use one-click account information sharing. If your app uses Quick Subscribe with IAP SDK v2.0, you must upgrade to the Appstore SDK. One-click account information sharing is supported in the Appstore SDK v3.0.5 and higher.
Q: Can I test one-click account information sharing with Live App Testing (LAT)? Can I reset consent of LAT testers to restart testing?
Yes, you can test one-click account information sharing with LAT. To reset consent, the LAT tester must go to Manage Login with Amazon and click Remove in the Manage Connection column. There isn't an option to revoke consent status in bulk.
Q: Can I test one-click account information sharing using App Tester?
You can use App Tester to mock the consent status attribute of the getUserData() method. To test your integration, set the response for consent status to CONSENTED or UNAVAILABLE. If the returned status is CONSENTED, your app should call requestUserProfileAccess() to fetch the authorization code. Then, make calls to the Appstore SDK REST APIs to get the customer data and automatically sign them in. If the returned status is UNAVAILABLE, your app should fall back to the default sign-in experience.

Integration with other IAP features FAQ

Q: Can I offer Quick Subscribe if I also offer a free trial?
Yes, you can offer both Quick Subscribe and a free trial on the same subscription product. However, Quick Subscribe doesn't support 60-day free trials.
Q: What if my customer used a free trial previously?
Quick Subscribe can detect a free trial created previously on the Amazon Appstore and does not allow the customer to enter into an additional trial period. However, if the customer started a trial outside of Amazon, Quick Subscribe cannot detect this information and the customer may enter into an additional free trial.
Q: Can I offer Quick Subscribe if I also offer promotional pricing?
Yes, you can offer both Quick Subscribe and promotional pricing on the same subscription product. However, Quick Subscribe doesn't support promotional pricing at weekly or biweekly intervals.
Q: How do I implement the Modify Subscription API?
To implement the Modify Subscription API, see Modify Subscription API in the tiered subscriptions documentation. At this time, tiered subscriptions is available to select partners only. Contact your Amazon representative for instructions to enable tiered subscriptions for your app.

Last updated: Apr 07, 2025