In-app purchases and subscriptions
Verify Apple and Google purchases in the backend. Manage entitlements without trusting a single client-provided premium flag.
How to design the workflow
Handle renewals, cancellations, refunds, grace periods and account changes. Store notifications may repeat or arrive late; deduplicate by event ID and verify ordering.
Cost and service boundaries
Backend plans do not include store commissions or third-party subscription management fees. Receipt verification and payment providers are not connected; this page explains the integration architecture.
Pre-launch checklist
Validate these steps in your app and with the providers you choose. Measure concurrent load alongside CPU, memory and storage before selecting a plan.
- Test sandbox purchases and restore flows.
- Verify access revocation after refunds.
- Keep store secrets only in the backend.
Common questions
Is this service available today?
This page describes a service plan and architecture. Managed customer services are not enabled; publication does not activate resources or integrations.
Which plan should I consider?
Consider the resource scope of Developer. This is not a capacity guarantee; validate it against application load and external provider fees.