Monetization
For anyone selling through Zellify funnels. You'll have a clear split between what Zellify handles and what your code handles. You need a payment provider connected.
How Zellify handles money#
Zellify never touches your money: Zellify does not hold funds. Every payment flows directly to your connected Stripe, Paddle, or Solidgate account. Zellify configures checkout, attaches metadata, and routes the user to the success page. Zellify never performs manual charges — all transactions run through your provider's hosted checkout.
Zellify does not grant access after payment: Zellify does not automatically grant user access or entitlements after payment. The platform registers webhooks for attribution and analytics only — it never updates your application's entitlement state. You must implement your own webhook handler in Stripe, Paddle, or Solidgate to grant users access to paid features. See Payment events and the Payments integration guides.
Collect email before the paywall: Every payment provider requires an email to create a checkout session. A funnel without a registration step before the paywall will fail at checkout. See Paywalls for the registration setup.
What you need before selling#
- A payment provider connected.
- At least one product.
- A funnel with a paywall attached to the product, preceded by a registration step that captures email.
Products, upsells, downsells#
How entitlements work#
Zellify does not manage entitlements. After payment, your code is responsible for granting access. That happens via your payment provider's webhooks (see Payment events) or via RevenueCat (see RevenueCat). The integration guides cover the common patterns.
The webhooks Zellify registers in your provider are read-only — they fire Zellify's analytics and attribution pipelines. They do not write back to your application database or grant entitlements. That handler is yours to implement.