Docs / Monetization

Manage access and revenue without separating it from publishing.

This public guide covers subscriptions, PPV, codes, referrals, and supported payment providers.

Playback & Entitlement Flow

Monetization is enforced before playback. The same title can use free, AVOD, SVOD, or PPV access while the backend decides whether to issue a signed playback URL or send the viewer to an upgrade path.

Playback and entitlement

Server-side access checks before every secure stream.

Needs accessAllowedUser opens titleDetail page or deep linkProfile and sessionAccount, device, planAccess checkFree, AVOD, SVOD, PPVPaywall or upgradeSubscribe, rent, purchaseSigned playback URLTTL, provider token, HLSStream deliveryCDN, player, subtitlesWatch progress savedResume across screens
Entitlements are enforced server-side
Subscriptions and PPV share one access model
Signed streams reduce playback leakage
Progress follows users across devices

Plans

Create subscription plans with price, currency, duration, trial period, max devices, max profiles, quality limits, app-store product identifiers, and provider availability.

Plan settings are product controls

Plans can define commercial price, app-store identifiers, profile limits, device limits, quality rules, and visibility behavior. Existing subscribers keep access until their subscription state changes.

PPV

Configure rental and purchase models for selected titles. Use PPV management to review purchases and keep title-level pricing close to the content record.

Codes

Activation codes support offline or partner-driven subscriptions. Discount codes support targeted campaigns for supported billing providers and plans.

Providers

Supported commercial flows include Stripe, Paddle, Apple, Google Play, and RevenueCat integrations, with webhooks and admin-side settings for operational control.

Stripe Checkout and webhooks
Paddle checkout path
Apple in-app purchase IDs
Google Play Billing offer tokens
RevenueCat entitlement events