What does the Google Play notification SUBSCRIPTION_PENDING_PURCHASE_CANCELED mean?
The Google Play notification SUBSCRIPTION_PENDING_PURCHASE_CANCELED means a purchase that was still pending was cancelled before it went through.
Quick facts#
| Notification | subscriptionNotification.notificationType 20, SUBSCRIPTION_PENDING_PURCHASE_CANCELED |
| Where | Google Play real-time developer notifications (Pub/Sub, DeveloperNotification) |
| Sent by | Google Play, as a Cloud Pub/Sub push to your endpoint |
| What Google says | A pending transaction of a subscription has been canceled. |
What triggers it#
- The customer started a purchase with a slow payment method, and it was cancelled before completing.
- The subscription never became active, so no access was ever due.
- Pending purchases are shown by Google as
SUBSCRIPTION_STATE_PENDINGuntil they finish.
What your server should do#
- Do not trust the message for the state. Google says a notification only tells you the purchase state changed; call the Google Play Developer API (
purchases.subscriptionsv2.get) with the purchase token to get the full state. - Remove any pending marker you kept for this purchase token.
- Do not grant access and do not acknowledge the purchase.
- Let the customer try again.
- Answer 2xx once you have handled the message, and skip a
messageIdyou have seen: Google recommends checking the uniqueness of message IDs so a redelivery does not make a second API call.
Example#
// A Pub/Sub push body: the notification is base64 JSON in message.data.
const body = { message: { messageId: "136969346945", data: Buffer.from(JSON.stringify({"version":"1.0","packageName":"com.example.app","eventTimeMillis":"1790800914000","subscriptionNotification":{"version":"1.0","notificationType":20,"purchaseToken":"PURCHASE_TOKEN"}})).toString("base64") } };
function decide(body) {
const n = JSON.parse(Buffer.from(body.message.data, "base64").toString("utf8"));
if (!(n.subscriptionNotification?.notificationType === 20)) return "ignore";
return "drop the pending purchase, grant nothing";
}
console.log(decide(body));Run-checked: npm run check:snippets runs this snippet with Node and compares its output with grant nothing (checked 2026-10-03).
How RevenueDot handles it#
RevenueDot answers every handled message with 2xx and every temporary failure with 5xx so Pub/Sub redelivers it. For subscription types it re-reads the subscription from Google with purchases.subscriptionsv2.get and applies that state, and it acknowledges a new purchase if the app has not. A purchase RevenueDot has not seen is applied only when the app's Track new purchases from server-to-server notifications setting is on. RevenueDot ignores it: the message is stored, answered 2xx with status ignored, and no purchase or event is created. Pending subscription states are ignored the same way.
Related#
- What does the Google Play notification SUBSCRIPTION_PURCHASED mean?
- What does the Google Play notification ONE_TIME_PRODUCT_CANCELED mean?
- What does the Google Play notification SUBSCRIPTION_EXPIRED mean?
- Which webhook events does RevenueDot send?
- Set up Google Play notifications in RevenueDot
Source#
- Google: Real-time developer notifications reference guide
- Google: Subscription lifecycle
- RevenueDot server: stores/google/notifications.ts (how the message is received)
- RevenueDot server: stores/google/notifications.ts (how the message is received)
- RevenueDot server: stores/google/sync.ts (how the purchase is re-read and applied)
Checked: 2026-10-03