RevenueCat IAP: products, entitlements, offerings, paywalls, and webhooks
PlannedPlanned: IAP management will follow RevenueCat's product-to-entitlement-to-offering model and will not unlock access from a client callback alone.
What this does
Will import products, map entitlements, configure offerings/packages/paywalls, generate SDK flows, and synchronize customer state.
What you need
RevenueCat, Apple, and Google products plus sandbox accounts.
What LaunchLayer automates
Planned configuration import, SDK output, purchase/restore examples, webhook deduplication, and entitlement synchronization.
What remains external
Store product approval, sandbox purchase, app integration, and pricing decisions.
Exact setup steps
Not released; use the generated IAP setup plan only.
How to verify it
Offering load, sandbox purchase, restore, entitlement return, cancellation, signature/auth check, dedupe, and environment separation must pass.
Common failures
Product ID mismatch, product not ready, missing offering, wrong public key, or duplicate webhook.
Security considerations
Preserve raw webhook body, authenticate requests, reject stale/replayed events, return quickly, and process idempotently.
Related articles
Native features; security and ownership.