Policy dimension
Published
Ecosystem and commercial policy rows aggregated across every feature — ad
networks, payment SDKs, and app-store/distribution channels. The Sponsored
flag is always visible; editorial status is independent of sponsorship.
- Legend
- Yes
- Partial
- Flag
- No
- Unknown
| Feature | Entity | Type | Context | Status | Sponsored | Notes |
|---|---|---|---|---|---|---|
| Payment Request API | Apple Pay | payment_sdk | Safari / iOS | Yes | No | Works in Safari via Payment Request; merchant-domain verification required. |
| Payment Request API | Stripe | payment_sdk | Cross-browser | Yes | No | Stripe wraps Payment Request as the Payment Request Button / Payment Element. |
| Payment Request API | Google Play billing | store_policy | Google Play TWA | No | No | TWAs distributing digital goods must use Play Billing, not Payment Request, per Play policy. |
| Web App Manifest: scope | Google Play (TWA) | distribution_channel | Google Play TWA | Yes | No | assetlinks.json origin must match the manifest scope origin, or the TWA degrades to a Custom Tab with browser chrome. |
| Web App Manifest: scope | Microsoft Store (PWA) | distribution_channel | Microsoft Store | Yes | No | Scope defines the in-app boundary store reviewers preview at submission. |
| Web App Manifest: screenshots | Google Play (TWA) | store_policy | Google Play TWA | Yes | No | Store listing screenshots are managed in Play Console, separate from the manifest member. |
| Web Push | Apple Push (APNs) | delivery_policy | iOS | Partial | No | iOS Web Push requires the user to add the app to the Home Screen first. |
← Back to the Compatibility overview.