Pay-per-view
Pay-per-view (PPV) sells access to a single live event or title for a one-time payment, instead of an ongoing subscription. Technically, a purchase creates an entitlement, a record that this buyer may watch this event. At playback, your backend turns that entitlement into a short-lived signed token, and the video platform plays the stream only when the token is valid. High-value events add DRM, and a replay window is enforced by when tokens and licenses expire.
How does pay-per-view streaming work?
The flow has four steps. Checkout records the payment and writes an entitlement for the buyer and the event. When the buyer opens the player, the app asks your backend for a playback token. The backend checks the entitlement and signs a token, usually a JWT, a signed JSON object that names the stream and an expiry time. The player sends that token when it requests the manifest, the playlist that lists the stream's segments, and the platform or CDN verifies the signature before serving anything.
For a long event, the token expiry is set a little longer than the broadcast, or the app refreshes the token in the background so nobody is cut off in the final round. If the event carries DRM, the same entitlement also decides whether the license server issues a license. After the event, access to the replay is simply another entitlement with its own end date.
How do you stop pay-per-view link sharing?
A pay-per-view link gets pasted into group chats within minutes of the start, so protection has to live in the stream, not on the web page. Signed tokens with short expiry stop an old link working later. Binding the token to one event stops a ticket for one fight playing another. Your entitlement service can also count active sessions per account and refuse new tokens past a limit, which slows password sharing.
Those controls stop link sharing but not stream ripping, where a tool records the decrypted segments. DRM closes that gap, because the key never leaves the device's secure module. Screen recording and camera capture remain, which is why large events add a visible watermark, often showing an account or order ID, so a leaked restream can be traced. Each layer has a cost, so match it to the event's value.
How do you scale a pay-per-view live stream?
Pay-per-view traffic is a flash crowd. Most buyers press play in the few minutes before the main event, so every part of the path sees its peak at the same moment. For a large event the token service may have to sign thousands of tokens a second, and if it slows down, viewers who paid see a spinner even though the video is fine.
On the delivery side, the CDN absorbs the load only if segments are cacheable. Tokens are checked at the edge, so the same cached segment serves every valid viewer. Live manifests refresh every few seconds, which makes manifest requests the hottest path. Multi-CDN routing spreads that load and gives a fallback if one network degrades in a region.
At the source, a single encoder is a single point of failure. A backup ingest and a rehearsal stream on the same setup are standard before any ticketed event.
Pay-per-view vs. subscription access: what changes technically?
The delivery stack is the same; the entitlement model is not. A subscription entitlement covers a whole catalogue for as long as billing stays active, so a token can be issued for any title and DRM licenses can renew while the subscription lasts. A pay-per-view entitlement covers one event or title, so tokens must name that specific stream and expire on the event's terms.
Time matters more in PPV. Access often has a start, so the stream should refuse early tokens or show a holding slate. It often has an end, such as a replay window, so token and license expiry must match it. Live sports services frequently run both models at once, with a season pass entitlement and a separate PPV entitlement for a single fight night, checked by the same token service against different rules.
How does FastPix handle pay-per-view?
FastPix handles the video side of a pay-per-view event; checkout, pricing and entitlement stay in your stack. Ingest accepts RTMP, RTMPS or SRT from OBS, vMix, Wirecast, FFmpeg or hardware encoders, with authenticated stream keys and backup ingest for redundancy. Real-time bitrate and dropped-frame health, plus webhooks on connect, disconnect and error, show the feed's state before doors open.
The stream is delivered as LL-HLS at 4 to 7 seconds glass-to-glass across a multi-CDN network of 300+ points of presence, with edge routing chosen per viewer. Concurrency scales with your plan, so there is nothing to provision before the event or tear down after it. AAO NXT runs premiere events on it.
Access is enforced at playback. After checkout, your backend signs a JWT for the buyer with your FastPix signing keys and an expiry you set, and the playback ID plays only with a valid token. Widevine, FairPlay and PlayReady DRM can be added for high-value events, billed as a monthly platform fee plus a small fee per license. DVR lets late buyers rewind and return to the live edge, and auto_archive turns the broadcast into an on-demand replay with the same playback ID and policy. Video Data alerts on error rate or QoE can be routed to Slack, PagerDuty or Opsgenie for the night.
Live encoding costs $0.0324 a minute at any resolution up to 1080p, and viewing is billed per minute watched. Rehearse the event, including an expired-token test, with the free plan's 30 live minutes, no card needed.
By the numbers
- Mayweather vs. Pacquiao in 2015 set a pay-per-view record with 4.4 million buys and upward of $400 million in residential revenue, according to Showtime and HBO. ('MayPac' KOs PPV buy, revenue records (Sports Video Group))
