RevenueCat

RevenueCat sits between the app and the stores: its SDK runs the store purchase sheet and posts every purchase token to the RevenueCat backend for verification before the app sees confirmation, and the backend computes which access the customer owns. Most outcomes come down to keeping two reads apart: Offerings say what to sell, CustomerInfo says what the user owns, and access is gated on one thing, an active entitlement. Most failures are configuration mismatches (wrong key for the platform, a bundle ID or package name that doesn't match, a current offering with no packages, store products still in draft), not code bugs. These files cover Flutter (purchases_flutter), React Native and Expo (react-native-purchases) and the Web SDK; some sources are chapters of RevenueCat's Android SDK handbook, and names from it are tagged [Kotlin]. For card payments and subscriptions on the web through Stripe itself, see stripe SKILL.md.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]