RevenueCat

RevenueCat handles native in-app purchases and subscriptions for you - the kind users buy through the App Store and Google Play, not card payments. It manages the paywall, the entitlement that unlocks paid features, and the cross-platform receipt checks that Apple and Google would otherwise make painful. This is distinct from Stripe card payments: use RevenueCat for app-store subscriptions and one-off purchases, Stripe for cards on the web.

What you get by connecting it

Once RevenueCat is connected, the agent can build:

• A paywall screen that shows your offerings and prices.
• The purchase flow, using the correct platform key on each device (iOS or Android).
• Entitlement checks that gate paid features, so the right content unlocks the moment a purchase clears.
• A restore-purchases flow, which Apple requires for any app selling subscriptions.

The agent uses the iOS public key on iPhones and the Android public key on Android devices automatically. You describe the paid features you want; the agent does the wiring.

Connecting it

RevenueCat gives you a separate public key for each platform:

• An iOS public key that starts with appl_.
• An Android public key that starts with goog_.
• Optionally, a secret REST API key for server-side reads (for example, checking a subscriber's status from your own backend).

Find them in the RevenueCat dashboard under Project settings then API keys. Paste them into Dashboard then Connectors then RevenueCat. Connect once and every project in your account can use it. Connecting requires a paid plan.

Saved secrets show as dots - the browser only ever sees that a key exists, never its value. The connector page has a Test connection control to re-check the saved keys against the live service, and a Disconnect control to remove them.

Keys and security

RevenueCat is a just connect connector. The two platform public keys (appl_ and goog_) are public by design and safe to embed in the app, so the agent puts them straight into the generated code where the purchase SDK needs them. There is no relay for these keys.

The optional secret REST key is different: like any secret, it must never be bundled into an app people download. If your app needs server-side subscriber reads, the agent routes them through a small server-side relay that holds the secret key, rather than the app calling RevenueCat's REST API directly.

Stored credentials are encrypted at rest with AES-256-GCM. The AI never sees a decrypted secret, and it will never ask you for a key in chat - keys belong on the connector page.

Useful links

• RevenueCat docs: https://www.revenuecat.com/docs
• Appsanic guide: Payments

Next

Read Payments for the full picture of charging money in your app, including when to reach for RevenueCat versus Stripe.