Last updated: August 9, 2026
SubTru documentation
These docs cover subscription handling in web and mobile apps across Stripe, Apple App Store, and Google Play. A subscription handler receives provider subscription events to determine the subscription status of a user. Topics in these docs include subscription event testing, verification, idempotency, ordering, user mapping, and access checks.
These docs apply whether you build subscription handling yourself or use SubTru instead.
Guides
- How SubTru handles subscriptions
What works with Stripe, Apple App Store, and Google Play, plus what is not supported yet.
- How subscription access works in your app
How subscription status, billing events, and access checks fit together. This is the foundation for the rest of these docs.
- How to test subscriptions across Stripe, Apple App Store, and Google Play
Test provider subscription events.
- How to handle Stripe subscription webhooks
Stripe signature verification, raw body handling, retries, idempotency, event ordering, and metadata mapping.
- How to handle Apple subscription webhooks
App Store Server Notifications V2, signedPayload verification, retries, idempotency, and appAccountToken mapping.
- How Apple certificate chain verification works
Apple's x5c chain, leaf certificates, intermediates, trusted roots, and JWS signature checks.
- How to handle Google Play subscription webhooks and RTDN
Cloud Pub/Sub push authentication, Real-time Developer Notification (RTDN) parsing, subscriptionsv2.get fetches, message acknowledgment, linked purchase tokens, and unbound purchase remediation.
Not sure where to start? How subscription access works in your app is the foundation everything else builds on.