Last updated: October 1, 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.
Open source
The SubTru API is open source and can be self-hosted.
- Self-hosting overview
Steps and requirements to run SubTru yourself.
- API reference
GitHub documentation outlining API requests and responses.
SubTru Cloud
SubTru Cloud offers a managed version of the open source API and includes a dashboard for organization management, provider setup, analytics, and more.
- How to test subscriptions
Steps on how to test subscriptions across Stripe, Apple App Store, and Google Play.
- Plans and pricing
Details on what each plan offers and how much each plan costs.
General
General guides about how SubTru handles user subscriptions. Some of the information in these guides isn't exclusive to SubTru, so it can be applied by anyone who wants to build their own subscription handling infrastructure.
- 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 SubTru handles subscriptions
What works with Stripe, Apple App Store, and Google Play, plus what is not supported yet.
- 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.