Stripe + RevenueCat
Zellify supports external subscription management via RevenueCat. If your app uses Stripe for payments and you use RevenueCat to centralize your subscription data, this guide explains how to make it w
Overview
If your configured payment provider on Zellify is Stripe, and you're also using RevenueCat, you can configure both to work together. RevenueCat listens to subscription events from your Stripe account, and Zellify sends funnel purchase data directly to your backend.
How It Works
User purchases via Zellify funnel (Stripe checkout)
Zellify processes the payment through your connected Stripe account.
Zellify sends a webhook to your app with the user's email and transaction details.
Stripe sends subscription events to RevenueCat
You set up a webhook between your Stripe account and RevenueCat.
RevenueCat listens for
checkout.session.completed,invoice.paid, etc.RevenueCat updates the user’s subscription status accordingly.
App creates user record
Your app backend receives Zellify’s webhook (with email) and creates the user.
RevenueCat can be configured to use the same email or an App User ID to unify the data.
Requirements
RevenueCat project must be linked to the developer’s Stripe account.
No changes required to Zellify’s integration—everything is handled via your existing webhook setup.
Optional (Recommended)
Pass RevenueCat App User ID into Zellify funnel URLs or tracking.
Sync it with your backend when handling Zellify webhook events.
Summary
Supported by Zellify?
✅ Yes
Supported by RevenueCat?
✅ Yes
Developer must set up?
Stripe webhook to RevenueCat
Best Practices
Always use consistent email or App User ID across Zellify and RevenueCat.
Use your app backend as the central point to reconcile data.
Use Zellify's webhook to create the user.
Use RevenueCat to track and manage entitlements.
For more details on webhook setup, visit Webhook Setup Guide.
Last updated