Vega Quick Subscribe Overview

Quick Subscribe reduces the number of clicks needed to purchase subscriptions on Fire devices and on your app’s retail web page. With Quick Subscribe, your customers enjoy a streamlined experience with app download, subscription purchase, and one-click account information sharing. In a typical account creation process on a Fire TV, a customer must type their account information using the remote. With Quick Subscribe, it takes only one click for a customer to share their first name, last name, zip code, and email address with your app, which reduces customer friction for creating an account and signing in.

​

Subscription requirements

To use Quick Subscribe, your app must follow these requirements.

• After Appstore presents an offer to a customer and they purchase and confirm the transaction, you must honor the terms of the offer, regardless if the customer is actually eligible for the offer.
• Any subscriptions presented in Quick Subscribe must be available through the app.
• After a customer purchases a subscription, they should not be allowed to purchase it again in the app.

​

User flow comparison

The following image shows a typical customer experience when signing up for a subscription on a Fire TV without Quick Subscribe. With Quick Subscribe, customers can subscribe in the first step, directly from the app detail page. The following image shows the flow when signing up for a subscription on Fire TV with Quick Subscribe. With one-click account information sharing, Appstore shows the customer a consent screen that allows them to agree to share their details with your app. If a customer provides their consent, after the app downloads and launches, the app can retrieve the customer’s details from Amazon and create an account. Your app can then automatically sign in the customer, bypassing the step for entering credentials.

​

Customer experience

The following images show the customer experience for Quick Subscribe on Fire TV, and the Amazon retail website.

​

How does Quick Subscribe work?

The following steps describe how Quick Subscribe works with Fire devices. Step 1: The customer initiates a subscription purchase from the app detail page on a Fire device. Step 2: Amazon shows a consent screen that asks the customer permission to share their name, zip code, and email with your app. Step 3: Amazon informs the customer their purchase is complete. Step 4: The app automatically downloads and opens on the customer’s device. Step 5: On launch, the app determines whether the customer has signed in to the app. If the customer hasn’t signed in, the app calls the getUserData() method from Amazon In-App Purchasing (IAP), and Amazon returns the customer’s consent status. If the consent status is CONSENTED, the app follows step 5a. If the consent status is UNAVAILABLE, the app follows step 5b Step 5a - consent status is CONSENTED:

1. The app calls the requestUserProfileAccess() method to get an authorization code for user profile access.
2. Your server uses the authorization code to fetch an access token by calling the Get Access Token REST API.
3. Your server uses the access token from the previous step to fetch the customer’s details by calling the Get User Profile REST API. Customer details include name, zip code, and email.
4. The app uses the customer’s details to create a new account or map to an existing account and then automatically signs in the customer.

Step 5b - consent status is UNAVAILABLE: The app shows the default account sign-in and account creation experience. Step 6: After the customer has signed in, your app calls the getPurchaseUpdates() method from Amazon IAP to retrieve the receipt for the purchase. Step 7: The app updates your server with the purchase data and verifies it with the Receipt Verification Service by calling the verifyReceiptId REST API. Step 8: The app calls the notifyFulfillment() method from IAP to acknowledge the receipt for the purchase and to confirm that the customer has access to the content*. * If you have previously integrated with the Acknowledge Receipt API and not notifyFulfillment(), the app calls the acknowledgeReceipt REST API to confirm the customer has accessed the content in this step. Step 9: The app allows the customer access to the content. Step 10: The app uses Real-Time Notifications (RTN) to receive notifications about the status of the user’s in-app purchase.

​

Related topics

---