Sell one live event without building a storefront
Launch a paid live event with one controlled playback surface, simple pricing, and viewer access tied directly to the session you want to monetize.
Monetization
Pay-per-view streaming and controlled access
Sell tickets to a live event, offer the replay on demand, or protect a video collection behind one branded viewing experience. Set pricing and access rules, publish the player on your site, and keep control of the audience relationship and revenue model.
Sell one live event without building a storefront
Launch a paid live event with one controlled playback surface, simple pricing, and viewer access tied directly to the session you want to monetize.
Workflow
- Sell one live event without building a storefront
Launch a paid live event with one controlled playback surface, simple pricing, and viewer access tied directly to the session you want to monetize.
- Reuse the same paywall for VOD
Use the same playback and access model for live events, follow-up replays, or catalog assets that need controlled viewing after the event ends.
Brand the player and choose password-only, email-and-password, or generated and imported unique credentials instead of outsourcing the full customer-facing access experience.
MonetizationMonetization
- Deliver paid playback globally
Make viewer access the business problem, not buffering. Keep the playback layer usable for paid audiences across geographies and connection conditions.
- Schedule launches, free passes, and follow-up access
Prepare paid events ahead of time, grant selected viewers access, and keep the same controlled surface available for replay or later sales.
CONTRIBUTION TO ACCESS
From an SRT contribution feed to a paid player
Keep contribution, playback, and payment as separate checkpoints. The SRT feed brings the event into Callaba, the player creates the viewer experience, and the payment configuration decides who may open it.
- Public endpoint
Assign a stable IP or hostname and allow only the required ports.
- TLS
Issue and test the certificate for the viewer-facing domain.
- SRT input
Create the contribution endpoint and prove decoded video and audio.
- Payment
Add the supported PayPal client configuration and event price.
- Player
Set branding, access behaviour, and the shareable viewer URL.
Run two tests before publishing the event link
- Open the player as an operator and confirm video, audio, and reconnect behaviour from the real SRT source.
- Complete a low-value purchase in a clean browser session, verify successful access, then repeat a failed or cancelled payment.
A healthy SRT transport cannot fix an incomplete buyer path. Keep the payment account, TLS expiry, source status, player URL, and refund or support process in the same event preflight.
Monetization
Control the player experience
Brand the player and choose password-only, email-and-password, or generated and imported unique credentials instead of outsourcing the full customer-facing access experience.
Reuse the same paywall for VOD
Use the same playback and access model for live events, follow-up replays, or catalog assets that need controlled viewing after the event ends.
Control the player experience
Brand the player and choose password-only, email-and-password, or generated and imported unique credentials instead of outsourcing the full customer-facing access experience.
Workflow
Keep your revenue model predictable
Set the price, keep the commercial logic clear, and avoid rebuilding access flows every time a new event or paid asset goes live.
Keep your revenue model predictable
Set the price, keep the commercial logic clear, and avoid rebuilding access flows every time a new event or paid asset goes live.
Deliver paid playback globally
Make viewer access the business problem, not buffering. Keep the playback layer usable for paid audiences across geographies and connection conditions.
Schedule launches, free passes, and follow-up access
Prepare paid events ahead of time, grant selected viewers access, and keep the same controlled surface available for replay or later sales.
Technical specification
What the product supports, and what to verify
Supported behavior sits beside a practical acceptance check. The installed Callaba interface and the real source, destination, and infrastructure profile remain authoritative.
| Capability | Supported behavior | Acceptance check |
|---|---|---|
| Sell one live event without building a storefront | Launch a paid live event with one controlled playback surface, simple pricing, and viewer access tied directly to the session you want to monetize. | No. The goal is to keep access centered on your paid playback surface, not to force viewers through a separate platform onboarding flow. |
| Reuse the same paywall for VOD | Use the same playback and access model for live events, follow-up replays, or catalog assets that need controlled viewing after the event ends. | Yes. A common pattern is to use the same player and access surface for the live event first and then keep it available for replay or on-demand sales. |
| Keep your revenue model predictable | Set the price, keep the commercial logic clear, and avoid rebuilding access flows every time a new event or paid asset goes live. | No, Callaba doesn't take any fees from your sales. You receive the full 100% of your earnings directly into your designated payout account. |
| Deliver paid playback globally | Make viewer access the business problem, not buffering. Keep the playback layer usable for paid audiences across geographies and connection conditions. | Yes. The paywall belongs with the playback surface, so embed-ready players and grouped player pages are the natural place to expose it. |
| Control the player experience | Brand the player and choose password-only, email-and-password, or generated and imported unique credentials instead of outsourcing the full customer-facing access experience. | In practice the workflow is split: player surfaces handle viewing and branding, grouped pages handle payment and access scenarios, credential lists control invited viewers, and File Manager provides the underlying assets when VOD is involved. |
| Schedule launches, free passes, and follow-up access | Prepare paid events ahead of time, grant selected viewers access, and keep the same controlled surface available for replay or later sales. | Yes. Use scheduled availability, selected viewers, or generated and imported credential lists when access should be granted outside the normal payment path. |
Continue in the product
Set it up in Callaba. Then check the full path.
You have seen what the product does. These three guides take you into the exact controls, show what to connect next, and give you a practical check before the workflow goes live.
Workflow
Ingest, route, secure, and deliver live and VOD — via UI or API. Cloud on AWS or on-prem.
Sell tickets to a live event, offer the replay on demand, or protect a video collection behind one branded viewing experience. Set pricing and access rules, publish the player on your site, and keep control of the audience relationship and revenue model.
Cloud pay per view streaming pricing
The pay-as-you-go cloud tariff is ideal for those who need all the advantages of the cloud, such as instant deployment of Callaba, low latency due to the global network of data centers, server reliability, data backup, scalability, managed services, and much more.
Self-hosted unlimited pay per view streaming pricing
The unlimited tariff is a good fit for actively growing broadcasting organizations of medium and large size that would like to have no limitations like those in the bundled tariff, while also maintaining full control over their data.
Search intent map
Choose the page that matches your decision
Use this page to evaluate and launch the Callaba product. Use the two guides for concepts and implementation planning.
Configure paid playback in Callaba
Stay here when you need the product capabilities, deployment choices, access controls, and next launch step.
Understand pay-per-view streaming
Read the overview for definitions, business models, and the role of a video paywall.
Plan a paid live event and VOD replay
Use the practical guide for event preparation, paid access, replay, and operating checkpoints.
Pay per view API
Pay per view REST APIAutomate paywalled playback with API modules
A paywalled video product is more than one payment form. In practice, teams manage player surfaces, grouped access pages, files, and viewer access rules as separate workflow pieces. Use the API when the paywall should behave like part of your own product, event stack, or customer portal.
Frequently Asked Questions
Do viewers need a Callaba account before they can pay and watch?
No. The goal is to keep access centered on your paid playback surface, not to force viewers through a separate platform onboarding flow.
Can I sell both live events and VOD with the same stack?
Yes. A common pattern is to use the same player and access surface for the live event first and then keep it available for replay or on-demand sales.
Can I control free passes or invited viewers?
Yes. Use scheduled availability, selected viewers, or generated and imported credential lists when access should be granted outside the normal payment path.
Does the paywall work with embed or player pages?
Yes. The paywall belongs with the playback surface, so embed-ready players and grouped player pages are the natural place to expose it.
Where does the revenue and access logic live?
In practice the workflow is split: player surfaces handle viewing and branding, grouped pages handle payment and access scenarios, credential lists control invited viewers, and File Manager provides the underlying assets when VOD is involved.
Where should I start in the docs?
Start with Web player groups for paywalled viewing pages, continue with Web players, and use Files if your paid workflow includes on-demand assets.
Do you charge any commission on my sales?
No, Callaba doesn't take any fees from your sales. You receive the full 100% of your earnings directly into your designated payout account.
Monetization
Schedule launches, free passes, and follow-up access
Prepare paid events ahead of time, grant selected viewers access, and keep the same controlled surface available for replay or later sales.