Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Develop
Test
Publish
Monetize
Engage users
Device specifications
Resources
Skip to main content
Real-Time Notifications (RTN) are server-to-server push notifications that provide comprehensive data about in-app purchases in real time. You can use this information to monitor purchase state changes associated with your customer’s in-app purchasable items.

Overview of Real-Time Notifications

Amazon uses receipts to notify you about a customer’s purchase state for in-app items. A receipt contains the current order state and the in-app item details you defined. Without RTN, you follow a pull model to get the latest receipt status. In the pull model, you must periodically call Receipt Verification Service (RVS) to query Amazon services for updates. However, RTN uses a push model where Amazon provides real-time server push notifications. Amazon’s RTN server sends a notification to your back-end server with information about your customer’s purchase, which you can then verify with RVS. You can use Real-Time Notifications (RTN) in addition to Receipt Verification Service (RVS). The following diagram shows how the RVS and RTN processes interact. See the description that follows. The following is a description of the process shown in the diagram. Steps 1–5: This is the regular RVS flow.
  1. User initiates an in-app purchase.
  2. App forwards the purchase receipt to your app server.
  3. App server sends a request to RVS server for validation of the receipt.
  4. RVS server confirms that the receipt is valid.
  5. Content delivered to the user.
For more details, see Receipt Verification Service Overview. Step 6: RTN sends a notification message about the customer’s in-app purchase to your app server. Step 7: The app server sends a request to the RVS server for validation of the receipt and obtains all information related to the receipt. Step 8: The RVS server confirms the receipt’s validity and returns information associated with the receipt. The RVS flow (Steps 1–5) doesn’t need to complete for the RTN flow (Steps 6–8) to start. The flows can run in parallel.

Prerequisites

Before you can use Real-Time Notifications, make sure your environment is ready to receive RTN responses. Because RTN pushes messages to you, Amazon needs a secure, publicly reachable destination to send them to. You must have a back-end server that meets the following requirements:
  • Exposes an HTTPS endpoint that receives RTN responses
  • Handles the HTTPS POST requests that Amazon sends
  • Returns a 200 response code to acknowledge each message
  • Uses valid SSL certificates from a trusted certificate provider
After your server meets these requirements, register its endpoint in the Developer Console and complete the confirmation-token flow. For the steps, see Use Real-Time Notifications.

Live App Testing for RTN

Before you release your app, use Live App Testing (LAT) to confirm that your endpoint receives and processes Real-Time Notifications correctly. LAT lets you run real in-app purchase transactions in a controlled test environment without affecting live customers. When you make an in-app purchase through LAT, the Amazon server returns an RTN payload with the attribute betaProductTransaction=true. Use this attribute to distinguish test notifications from production notifications so your server handles each appropriately.

Real-Time Notification message details

Real-Time Notifications are delivered through a JSON message to your HTTPS endpoint. Each notification contains the following JSON payload. You can find additional information in the Amazon Simple Notification Service (SNS) Developer Guide. The Message attribute of a Real-Time Notification contains an escaped JSON with the following fields.

Supported notification types

RTN messages contain information about each type of in-app purchase (subscriptions, entitlements, and consumables). Amazon might add or change notification types over time. You will be informed of new notification types as they are added. Amazon generally recommends that you ignore any notification types not applicable to you. The following table describes the currently available notification types.
Notification TypeDescription
CONSUMABLE_CANCELLEDConsumable item was voluntarily or involuntarily cancelled.
CONSUMABLE_PURCHASEDConsumable item was purchased.
ENTITLEMENT_CANCELLEDEntitlement item was voluntarily or involuntarily cancelled.
ENTITLEMENT_PURCHASEDEntitlement item was purchased.
SUBSCRIPTION_AUTO_RENEWAL_OFFAuto-renew feature for subscription was turned off.
SUBSCRIPTION_AUTO_RENEWAL_ONAuto-renew feature for subscription was turned on.
SUBSCRIPTION_CANCELLEDA subscription was voluntarily or involuntarily cancelled.
SUBSCRIPTION_CONVERTED_FREE_TRIAL_TO_PAIDAn active free trial subscription was converted to paid subscription.
SUBSCRIPTION_EXPIREDA subscription was expired.
SUBSCRIPTION_IN_GRACE_PERIODA subscription has entered grace period (if enabled).
SUBSCRIPTION_OUT_OF_GRACE_PERIODUser fixes the payment issue/failure of the subscription which was previously in grace period.
SUBSCRIPTION_MODIFIED_DEFERREDA subscription plan was modified with the “deferred” proration mode. The subscription plan is scheduled to change at the next renewal date. The current plan remains active until the renewal date.
SUBSCRIPTION_MODIFIED_IMMEDIATEA subscription plan was modified with the “immediate” proration mode. The existing plan is canceled with a prorated refund, and the new plan is activated immediately. The notification includes the canceled receipt ID.
SUBSCRIPTION_PURCHASEDA subscription was purchased.
SUBSCRIPTION_RENEWEDAn active subscription was renewed.
SUBSCRIPTION_SCHEDULED_TO_ENDA subscription is scheduled to end because the auto-renew feature was turned off. Sent 10 days before for a customer’s monthly subscription is scheduled to end. Sent 30 days before a customer semi-annual/annual subscription is scheduled to end.

Real-Time Notification FAQ

The following are frequently asked questions (FAQ) about Real-Time Notifications.
Last modified on October 8, 2026