Paddle + RevenueCat
Zellify supports external subscription management via RevenueCat. If your app uses Paddle for payments and you use RevenueCat to centralize your subscription data, this guide explains how to make it w
Overview
Zellify supports Paddle, and RevenueCat offers a native integration with Paddle (Classic or Billing). This makes it possible to manage your subscriptions in RevenueCat while still using Zellify for web onboarding and conversions.
How It Works
User purchases via Zellify funnel (Paddle checkout)
Zellify triggers a Paddle payment via your linked account.
Zellify sends a webhook to your backend with the user's email and transaction info.
Paddle notifies RevenueCat of the subscription
You configure RevenueCat to receive webhook events from Paddle.
RevenueCat updates the subscription state automatically.
App creates user record
Your backend receives the Zellify webhook and creates the user.
The same email can be used in RevenueCat to match users and subscriptions.
Requirements
RevenueCat must be connected to the same Paddle account Zellify uses.
Developer must configure Paddle to send webhook events to RevenueCat.
Notes
RevenueCat handles both Paddle Classic and Paddle Billing, but Billing has limited SDK support.
For best results, sync RevenueCat’s App User ID with Zellify funnel metadata or email.
Summary
Supported by Zellify?
✅ Yes
Supported by RevenueCat?
✅ Yes
Developer must set up?
Paddle 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