Implementing Subscriptions in React Native (2025): iOS & Android, Cleanly

Subscriptions sound simple — until you deal with proration, grace periods, and receipt validation. Here’s a stable blueprint.

Products & SKUs

Create monthly and yearly products on both stores. Keep SKU names consistent (e.g., premium_monthly, premium_yearly). Configure intro offers and free trials at the store level.

Client Flow

1. Fetch products with react-native-iap at app start (retry on network errors).
2. Show a single source of truth pricing card; localize currency and tax.
3. On purchase:
   • iOS: finish transaction, capture transactionReceipt.
   • Android: acknowledge purchase and capture purchase token.
4. Sync to backend for server-side validation and entitlement activation.

Server Validation

• App Store: App Store Server API (transaction history + notifications).
• Play: Google Play Developer API (purchases.subscriptions).
• Store entitlement state: active | grace | on_hold | paused | expired.
• Use Server Notifications to update status on renewals/refunds; avoid polling.

Edge Cases

• Upgrade: Apply benefits immediately (stores handle proration/refunds).
• Downgrade: Defer at next renewal; show the pending plan clearly.
• Billing retry: Preserve access during grace; prompt to update payment.
• Restore purchases: Always provide a visible “Restore” on both platforms.

UX Essentials

• Clear, benefit-focused paywall with social proof and FAQ.
• Show next billing date and how to cancel.
• Accessible buttons, straightforward error states, and idempotent purchase calls.

When the contract between client and server is explicit, subscriptions become boring — the best possible state.