Cross-Platform Subscriptions Across iOS, Android, and Web
Supporting subscriptions on iOS, Android, and the web means working with StoreKit, Google Play Billing Library, and Stripe or another web provider. Each system evolved separately, so data fields, lifecycle meanings, and edge cases do not line up. The work grows faster than the number of platforms because every difference must be found, tested, and maintained.
Different platforms, no common standards
Apple's StoreKit traces to legacy iTunes-era architecture and can omit data developers expect from a modern processor. Google Play Billing arrived later but still has data gaps and API quota limits to respect. Stripe is developer-friendly, yet web billing leaves VAT and sales-tax handling to you. Refunds illustrate the split: Google and Stripe allow them, Apple does not. Apple provides full transaction history, while Google provides active subscription status and cannot retrieve subscriptions expired more than 90 days via its APIs. Apple automates upgrades, downgrades, and crossgrades; Google and Stripe leave that logic to developers. Family Sharing exists on Apple but not on Google or Stripe. Even shared terms lack a standard meaning: a lapsed subscription that later pays, or a trial that moves from monthly to annual, may or may not count as a trial conversion depending on the platform.
Sample receipt data: what to compare
Compare the same trial purchase across platforms using protected modules code0001 for Apple, code0002 for Google Play, and code0003 for Stripe. The field names, nesting, and coverage differ completely. Apple does not provide transaction price in the sample, and Google does not provide purchase date in an easily digestible format. Use these samples as a checklist when designing a unified internal model: capture what each platform reliably provides, mark gaps explicitly, and never assume a field exists because another platform has it.
Pain point 1: Identity validation
A subscription must stay tied to the right person across phone, laptop, and TV. Store systems know Apple or Google accounts, web payments may know only an email and card, and none know your internal user IDs. A receipt token can act as a proxy for the store account, but alternate paths break the simple one-user, one-subscription picture: subscribing on one device then opening another without signing in, or sharing a login so two receipts land on one account. Cross-platform use multiplies the permutations. Decide in advance which receipt wins, whether a second device is blocked, and how much sharing is allowed, similar to a streaming service that permits some sharing within limits. A unified identity layer below your account system can return one clean subscriber view regardless of device or sharing path, using an App User ID you supply or generate from a system such as Auth0 or Firebase.
Pain point 2: Managing entitlements
Knowing who a subscriber is is only half the task; you also need what they can access. Entitlements cover subscriptions, content, and bundles, including items that may no longer be valid. They are not simple booleans: states such as expired, renewing, or billing trouble carry different names and meanings per platform. Complexity rises as offerings change. Replacing a lifetime option with an annual plan, then adding individually purchased pro features, creates multiple paths to the same feature. A user who buys two pro features, upgrades to lifetime, then cancels must retain the original features. Model each entitlement with its state and source, merge across platforms, and check access through a single entitlement identifier. Protected module code0005 shows the pattern of checking whether a named entitlement is active for a purchaser.
Pain point 3: Data integrations with third-party tools
Subscription data becomes useful only when it reaches analytics, lifecycle, and messaging tools. Historical analysis can reveal when people cancel and what precedes cancellation; real-time events such as turning off auto-renew can trigger winback messages. With one platform, wiring data into tools is manageable. With several, each tool would otherwise need separate pipelines for Apple, Google, and Stripe formats, and switching providers means rebuilding them. Normalize receipt data into one consistent event format at ingestion, then send it to analytics, a data warehouse, or a mobile measurement partner. Streaming events support immediate campaigns, and webhooks cover unsupported tools or custom workflows.
Pain point 4: Future-proofing for platform updates
Platform release calendars collide: Apple announces features in June and ships in September, while Google and Stripe move incrementally. New receipt fields can break existing parsing, and open-source helpers may lag behind platform changes, forcing forks. Keep a release calendar per platform, isolate receipt parsing behind adapters, and test new fields before launch. The source example notes offer-code support added two days after Apple's release, illustrating the value of a team or vendor whose job is to track these changes. Testing deserves its own plan too, because some in-app purchase behavior is hard to test and techniques vary widely by platform.
Summary and launch checklist
Use this launch checklist: 1) Inventory each platform's receipt fields and gaps. 2) Define one internal event and entitlement model. 3) Map store accounts and receipt tokens to internal user IDs, including shared-login rules. 4) Preserve separately purchased features across upgrades and cancellations. 5) Normalize events once, then fan out to analytics and messaging. 6) Track each platform's release calendar and test new fields in isolation. A unified layer that handles identity, entitlements, normalized data, and platform updates lets the app team focus on the product instead of reconciling three billing systems.
| Area | Apple | Google Play | Stripe / web |
|---|---|---|---|
| Refunds | Not offered by Apple | Supported | Supported |
| Transaction history | Full history provided | Active status only; expired over 90 days not retrievable via API | Full history provided |
| Plan changes | Upgrades, downgrades, crossgrades automated | Developer handles logic | Developer handles logic |
| Family sharing | Supported | Not supported | Not supported |
| Tax handling | Platform handled | Platform handled | Developer handles VAT and sales tax |
Differences summarized from source; verify current platform behavior before implementation.
Frequently asked questions
Why do receipt formats differ so much between Apple, Google, and Stripe?
Apple may not expose transaction price, Google may not expose purchase date in an easily digestible format, and each platform structures receipt JSON differently. Plan a normalization layer that fills gaps before reporting or entitlement decisions.
What should happen when one account has two store receipts?
Map a receipt token or store account to your internal user ID, handle sign-in on a second device, and decide precedence when two receipts attach to one account. Shared logins need an explicit sharing policy rather than an accidental first-receipt rule.
Why is a simple active-or-not check insufficient for entitlements?
Treat entitlements as states, not booleans. A user can be expired, renewing, or in billing trouble, and those labels differ by platform. Also preserve separately purchased features when a later subscription is cancelled.
{
"environment": "Production",
"latest_receipt": "receipt_token",
"latest_receipt_info": [
{
"expires_date": "2021-04-10 18:05:37 Etc\/GMT",
"expires_date_ms": "1618077937000",
"expires_date_pst": "2021-04-10 11:05:37 America\/Los_Angeles",
"in_app_ownership_type": "PURCHASED",
"is_in_intro_offer_period": "false",
"is_trial_period": "true",
"original_purchase_date": "2021-04-07 18:05:37 Etc\/GMT",
"original_purchase_date_ms": "1617818737000",
"original_purchase_date_pst": "2021-04-07 11:05:37 America\/Los_Angeles",
"original_transaction_id": "0000000000",
"product_id": "product_id",
"purchase_date": "2021-04-07 18:05:37 Etc\/GMT",
"purchase_date_ms": "1617818737000",
"purchase_date_pst": "2021-04-07 11:05:37 America\/Los_Angeles",
"quantity": "1",
"subscription_group_identifier": "00000000",
"transaction_id": "0000000000000",
"web_order_line_item_id": "0000000000000",
}
],
"pending_renewal_info": [
{
"auto_renew_product_id": "product_id",
"auto_renew_status": "1",
"original_transaction_id": "000000000000",
"product_id": "product_id",
}
],
"receipt": {
"adam_id": 0,
"app_item_id": 0,
"application_version": "1.0",
"bundle_id": "com.sample.app",
"download_id": 1234567890,
"in_app": [
{
"expires_date": "2021-04-10 18:05:37 Etc\/GMT",
"expires_date_ms": "1618077937000",
"expires_date_pst": "2021-04-10 11:05:37 America\/Los_Angeles",
"in_app_ownership_type": "PURCHASED",
"is_in_intro_offer_period": "false",
"is_trial_period": "true",
"original_purchase_date": "2021-04-07 18:05:37 Etc\/GMT",
"original_purchase_date_ms": "1617818737000",
"original_purchase_date_pst": "2021-04-07 11:05:37 America\/Los_Angeles",
"original_transaction_id": "000000000",
"product_id": "product_id",
"purchase_date": "2021-04-07 18:05:37 Etc\/GMT",
"purchase_date_ms": "1617818737000",
"purchase_date_pst": "2021-04-07 11:05:37 America\/Los_Angeles",
"quantity": "1",
"transaction_id": "000000000",
"web_order_line_item_id": "000000000",
}
],
"original_application_version": "1.0",
"original_purchase_date": "2021-04-07 18:04:36 Etc\/GMT",
"original_purchase_date_ms": "1617818676000",
"original_purchase_date_pst": "2021-04-07 11:04:36 America\/Los_Angeles",
"receipt_creation_date": "2021-04-07 18:05:38 Etc\/GMT",
"receipt_creation_date_ms": "1617818738000",
"receipt_creation_date_pst": "2021-04-07 11:05:38 America\/Los_Angeles",
"receipt_type": "Production",
"request_date": "2021-04-07 18:05:58 Etc\/GMT",
"request_date_ms": "1617818758965",
"request_date_pst": "2021-04-07 11:05:58 America\/Los_Angeles",
"version_external_identifier": 839248731,
},
"status": 0,
}{
"receipt_data": {
"acknowledgementState": 1,
"autoRenewing": true,
"countryCode": "CA",
"developerPayload": "",
"expiryTimeMillis": "1618085008677",
"kind": "androidpublisher#subscriptionPurchase",
"orderId": "GPA.3314-0849-3356-76418",
"paymentState": 2,
"priceAmountMicros": "27990000",
"priceCurrencyCode": "CAD",
"startTimeMillis": "1617818646564",
}
}
{
"application_fee_percent": null,
"billing": "charge_automatically",
"billing_cycle_anchor": 1622160021,
"billing_thresholds": null,
"cancel_at": null,
"cancel_at_period_end": false,
"canceled_at": null,
"collection_method": "charge_automatically",
"created": 1619568021,
"current_period_end": 1622160021,
"current_period_start": 1619568021,
"customer": "cus_**",
"days_until_due": null,
"default_payment_method": null,
"default_source": null,
"default_tax_rates": [],
"discount": null,
"ended_at": null,
"id": "sub_**",
"invoice_customer_balance_settings": {
"consume_applied_balance_on_void": true,
},
"items": {
"data": [
{
"billing_thresholds": null,
"created": 1619568022,
"id": "si_**",
"metadata": {},
"object": "subscription_item",
"plan": {
"active": true,
"aggregate_usage": null,
"amount": 1990,
"amount_decimal": "1990",
"billing_scheme": "per_unit",
"created": 1507048460,
"currency": "eur",
"id": "**",
"interval": "month",
"interval_count": 1,
"livemode": true,
"metadata": {},
"nickname": null,
"object": "plan",
"product": "prod_**",
"tiers": null,
"tiers_mode": null,
"transform_usage": null,
"trial_period_days": null,
"usage_type": "licensed",
},
"price": {
"active": true,
"billing_scheme": "per_unit",
"created": 1507048460,
"currency": "eur",
"id": "**",
"livemode": true,
"lookup_key": null,
"metadata": {},
"nickname": null,
"object": "price",
"product": "prod_**",
"recurring": {
"aggregate_usage": null,
"interval": "month",
"interval_count": 1,
"trial_period_days": null,
"usage_type": "licensed",
},
"tiers_mode": null,
"transform_quantity": null,
"type": "recurring",
"unit_amount": 1990,
"unit_amount_decimal": "1990",
},
"quantity": 1,
"subscription": "sub_**",
"tax_rates": [],
}
],
"has_more": false,
"object": "list",
"total_count": 1,
"url": "\/v1\/subscription_items?subscription=sub_**"
},
"latest_invoice": {... \/\/ a lot of additional data in here
},
"quantity": 1,
"schedule": null,
"start": 1619568021,
"start_date": 1619568021,
"status": "trialing",
"tax_percent": null,
"transfer_data": null,
"trial_end": 1622160021,
"trial_start": 1619568021,
}curl --request GET \
--url https:\/\/api.revenuecat.com\/v1\/subscribers\/app_user_id\
--header 'Authorization: Bearer REVENUECAT_API_KEY' \
--header 'Content-Type: application\/json' \
--header 'X-Platform: ios'