Webhook setup
Google Play Real-time Developer Notifications
Google Play RTDN delivers subscription events through a Pub/Sub topic. You create the topic, add a push subscription pointed at stubkit, and grant stubkit's service account OpenID Connect verification.
Endpoint to paste
https://api.stubkit.com/v1/webhooks/google/your-appReplace your-app with the slug of the tenant you are configuring.
Dashboard steps
- In Google Cloud Console, create a new project or reuse an existing one.
- Enable the Google Play Android Developer API.
- Create a service account with role Pub/Sub Subscriber. Download the JSON credentials file.
- Create a Pub/Sub topic and add a push subscription with the endpoint set to the stubkit URL above.
- On the subscription, enable Authentication and select your stubkit service account. This makes Pub/Sub sign every push with an OpenID Connect JWT we verify.
- In Play Console → All apps → your app → Monetization setup → Real- time developer notifications, set the topic path.
- Paste the service account JSON and the package name into dash.stubkit.com → Apps → your app → Settings → Providers.
What we verify
- The Authorization header is a Bearer JWT signed by Google's OpenID Connect authority.
- The audience matches the exact push URL configured in Pub/Sub.
- The service account email in the token matches what you uploaded.
What we store
The Pub/Sub envelope is archived under google/<tenant>/yyyy/mm/dd/<messageId>.json. The base64-decoded RTDN notification is normalized into an internal message keyed by purchase token and notification type — safe to re-deliver.