Feature
RTDN webhooks
Google Play real-time developer notifications — auto-processed. Tierux runs the Pub/Sub delivery pipeline, validates JWTs, and keeps entitlement state updated so your backend just reads the API.
| Capability | With Tierux | Without Tierux |
|---|---|---|
| Pub/Sub setup | None needed — RTDN delivery runs on Tierux's shared Pub/Sub topic. You still point Play Console at that topic yourself. | Manual Google Cloud Console setup, IAM roles |
| Notification validation | JWT signature + audience checked automatically | Custom JWT verification, key rotation handling |
| Renewal processing | Auto-updates entitlement expiry | Custom state machine per subscription |
| Cancellation handling | Grace period tracked, expiry date set | Manual parsing + DB updates |
| Apple Server Notifications v2 | JWS-signed notification processing included | Separate implementation, certificate management |
| Entitlement state sync | Always current via REST API | Batch jobs or stale snapshots |
Tierux is pre-launch. RTDN and App Store notification processing ship as part of the verification pipeline — your entitlement state stays current without you building notification infrastructure.
Related features
Purchase verification
Verify a purchase once, then let RTDNs keep entitlement state current.
Server-side entitlements
Gate features from your backend — RTDNs keep the state accurate.
Docs: RTDN setup
Step-by-step guide for Google Play real-time developer notification configuration.
Frequently asked questions
What are Google Play real-time developer notifications (RTDN)?
RTDNs are Pub/Sub messages that Google Play sends to your backend when a subscription event occurs — renewal, cancellation, expiry, grace period entry, account hold, etc. Without a service like Tierux, you must set up a Google Cloud Pub/Sub topic and subscription, handle authentication, and parse the notification payloads yourself.
How does Tierux handle RTDNs?
Tierux operates one shared Pub/Sub topic and push subscription for every customer app — there's no Pub/Sub topic or subscription for you to create. You still point your app's Play Console at Tierux's topic yourself — that stays manual. Incoming notifications are automatically validated (JWT signature + audience check), parsed, and applied to the user's entitlement state — your backend queries the REST API and always sees current data, not a stale snapshot.
Does Tierux process Apple App Store notifications too?
Yes. Tierux handles App Store Server Notifications v2 (JWS-signed) for subscription lifecycle events — renewal, expiry, billing retry, refund, etc. — and applies them to entitlement state using the same mapping as Google Play RTDNs, though the App Store notification path is implemented with limitations and has received less production hardening than RTDN (see the platform support matrix).
Let RTDNs update your entitlements automatically
Free tier — unlimited apps, 1 paywall. No credit card, no revenue share.
Start free