PayPal integration for video platform
PayPal integration for video platform on Flicknexs: billing subscriptions for recurring plans, checkout orders and server-side captures for pay-per-view.
Flicknexs connects the operator's PayPal business account to the plans and per-title prices defined in the admin, using billing subscriptions for recurring revenue and orders with captures for one-time purchases.
Trusted by industry leaders
50+ OTT platforms powered by Flicknexs
Quick answer: A PayPal integration for video platform lets viewers pay for a streaming service from a PayPal balance or a card held in PayPal, without typing card details on your site. Flicknexs creates PayPal billing subscriptions for recurring plans and PayPal checkout orders with server-side captures for pay-per-view, settling to the operator's own PayPal business account.
Flicknexs provides paypal integration as part of its white-label OTT platform. Flicknexs connects the operator's PayPal business account to the plans and per-title prices defined in the admin, using billing subscriptions for recurring revenue and orders with captures for one-time purchases.
Why PayPal still matters on a video platform
A share of any international audience prefers to pay through PayPal rather than type a card number into an unfamiliar site. Some hold a balance, some want a buyer-protection layer, and some are in countries where a card checkout is not the default. For an operator that share is revenue that a card-only checkout leaves behind. The question is not whether a platform shows a PayPal button but what it does with the two very different PayPal products: the recurring billing subscription and the one-time order, and how it confirms that a payment completed before opening playback.
Flicknexs treats those two products separately. A recurring plan becomes a PayPal billing subscription that PayPal renews on the plan interval, with the viewer approving it inside PayPal. A rental or purchase of a single title becomes a PayPal checkout order that the viewer approves and the platform then captures on the server. The capture is the confirmation: playback opens only after the capture returns as completed. Customer details, funding sources and disputes remain in the operator's PayPal account, which is where refunds are issued as well.
The third reason is the refund and dispute path, which is where operators lose time. PayPal runs its own resolution center and its own rules on when a buyer can claim, and those rules are described in the PayPal Subscriptions documentation and the PayPal Orders documentation together with PayPal's user agreement for your country. Flicknexs does not sit between you and that process. The operator refunds in PayPal, then ends access on the subscriber's record in the admin, and the revenue reports show what was collected by month.
What the PayPal integration does on Flicknexs
Each row is a behavior present in the Flicknexs payment service on the date checked, named the way PayPal names it.
Billing subscriptions
A recurring plan becomes a PayPal billing subscription that the viewer approves inside PayPal and PayPal renews.
Checkout orders
A pay-per-view title or paid live event becomes a PayPal order for the price set on the title.
Server-side capture
After the viewer approves an order, the platform captures it on the server and records the purchase.
Own account settlement
Client ID and secret from your PayPal business account are stored in the admin; funds settle to you.
Sandbox and live
Sandbox credentials let you test the whole flow before switching to live credentials.
Plan currency
The currency sent to PayPal is the one set on the plan or title in the admin.
Side by side with cards
Enable PayPal with Stripe, Razorpay or any other gateway on the same checkout.
Revenue reports
PayPal subscriptions and captured orders appear in the monthly subscription and pay-per-view revenue reports.
Source: Flicknexs platform documentation and architecture specification, 2026-09-03.
How PayPal subscriptions and one-time orders work on Flicknexs
PayPal offers two distinct products, and the platform uses each for the job it fits. This is what happens on each path.
Credentials and environment in the admin
The admin stores the client ID and secret from your PayPal business account and an environment switch for sandbox or live. The platform calls PayPal from the server with those credentials; the browser only ever sees PayPal's own approval pages. You can run sandbox against PayPal's test buyer accounts while the rest of the site serves real viewers, then switch when ready.
A recurring plan becomes a billing subscription
When a viewer confirms a subscription plan and chooses PayPal, the platform creates a PayPal billing subscription for the plan's price and interval and sends the viewer to PayPal to approve it. On return with the subscription identifier, the platform records the plan as active on the viewer's account. PayPal renews the subscription on the interval and holds the agreement, the funding source and the payment history.
A title becomes an order, then a capture
For pay-per-view, the platform creates a PayPal order for the price set on the title in its currency. The viewer approves the order inside PayPal and returns. The platform then captures the order on the server. Only a completed capture writes the purchase record with its rental window, expiry and view count, and only then does the player open the title.
Approval alone is not payment
An approved order that has not been captured has moved no money, and the platform treats it that way. The capture call is the confirmation step, so a viewer who returns to your site with an order identifier but whose capture fails does not get access. The failed capture is visible in the PayPal activity log, and the viewer can try again.
Cancellations and renewals live in PayPal
PayPal runs the renewal schedule and lets the viewer cancel a billing subscription from their PayPal account as well as from your site. The operator sees renewals, failed payments and cancellations in the PayPal dashboard. The platform records the plan and the subscription identifier and shows them on the subscriber record in the admin for the operator to reconcile.
Reports by month, per gateway
Every PayPal subscription and every captured order is written to the same subscription and pay-per-view revenue tables that the other gateways use, so the monthly revenue reports show PayPal income next to card income. The admin also keeps the PayPal identifiers on each record, so an operator can search PayPal by identifier when a viewer emails about a charge.
Setup for PayPal in the Flicknexs admin
Five steps in order. Use PayPal sandbox for the first four and switch to live credentials as the last step.
- 1
Create a PayPal app for your business account
In the PayPal developer dashboard, create an application under your business account to obtain a client ID and secret. PayPal issues separate sandbox and live credentials; take the sandbox pair first. Confirm that your PayPal business account is verified and able to receive payments in the currencies you intend to charge.
- 2
Enter credentials and choose the environment
In the Flicknexs admin, open payment gateways, select PayPal, paste the client ID and secret, set the environment to sandbox and enable the gateway. Save. PayPal now appears on the viewer checkout next to any other gateway you have on. The payment gateways page shows how several gateways share one checkout.
- 3
Set plan and title prices with a currency
Create your recurring plans with a price, an interval and a currency, and set per-title prices, rental windows and free-preview minutes on pay-per-view titles. The currency on each plan or title is what the platform sends to PayPal, so pick one your PayPal account can receive according to PayPal's documentation.
- 4
Run a sandbox subscription and a sandbox order
Using a PayPal sandbox buyer account, subscribe to a plan and then buy a single title as a viewer. Confirm the subscription shows as active in the admin and in the sandbox dashboard, that the order captured, that playback opened, and that both appear in the revenue report. Cancel the subscription from the viewer account and confirm PayPal reflects it.
- 5
Switch to live credentials and confirm one real capture
Replace sandbox credentials with the live client ID and secret, set the environment to live, and buy one low-priced title from a personal PayPal account. Check the capture in your PayPal activity and the purchase in the admin. Only after that real capture succeeds should marketing point viewers at the checkout.
What the PayPal integration does not do
The boundaries of the current build, so nobody discovers them during a launch weekend.
No event feed from PayPal to the platform
The platform records a subscription when the viewer returns from approval and records a purchase when it captures the order. It does not consume PayPal's background event notifications. Renewals that fail, cancellations made inside PayPal and disputes opened by a buyer are therefore read in the PayPal dashboard by the operator, who then adjusts the subscriber's record in the admin if access should end.
Coupons do not apply on PayPal checkout
The promotion codes and the global coupon setting described on the coupons and discounts page work only on Stripe checkout. A viewer paying through PayPal sees no code field. If a campaign needs a discount for PayPal buyers, publish a separate plan at the discounted price for the campaign period rather than expecting a code to apply.
No free-trial days on plans
There is no trial-days field on a plan, so a PayPal billing subscription created by Flicknexs charges from the first approval. To let viewers sample content before paying, set free-preview minutes on titles and episodes on the video paywall. That path needs no PayPal call and no approval from the viewer.
PayPal's own rules on methods, currencies and fees
Which funding sources PayPal offers a given buyer, which currencies your account can receive, how long holds last for a new account, and what PayPal charges per transaction are all decided by PayPal and documented on PayPal's own site. Flicknexs sends the amount, currency and interval; it does not change what PayPal accepts or how PayPal prices it.
Not used inside the store-billed apps
PayPal is a web checkout. Purchases begun inside the iOS app go through Apple in-app purchase and purchases inside the Android app go through Google Play Billing, each with the store's published fee. A viewer who subscribes through PayPal on the website signs in to the apps with the same account and keeps that access there.
Worked example: a film distributor renting titles through PayPal
Take an independent film distributor with a catalog of festival titles and rights in a dozen countries. Its buyers are scattered, many of them older cinephiles who trust a PayPal button more than a card form on a small site. The distributor adds PayPal in the admin alongside a card gateway, sets a rental price on each film in euros with a 72-hour window and a two-view limit, and creates a monthly all-catalog plan for the regulars. Free-preview minutes on each film give the trailer-like sample the distributor wants.
A viewer in one country rents a documentary. The platform creates a PayPal order, the viewer approves it in PayPal, and on return the platform captures the order and writes the rental with its 72-hour window. A regular viewer in another country subscribes to the catalog plan instead; that becomes a PayPal billing subscription, approved once, renewed by PayPal each month. Neither viewer typed a card number on the distributor's site, and both purchases appear in the revenue report as subscription and pay-per-view lines.
A month later a buyer opens a dispute in PayPal over a rental they say they never watched. The distributor checks the analytics section, which records the player session and its watch time, and answers the dispute in the PayPal resolution center with that information. When a different buyer asks for a refund on a mistaken purchase, the distributor refunds the capture in PayPal, then closes the rental on the viewer's record in the admin. The money and the dispute stayed in PayPal; the access decision stayed on the platform.
Checklist before you open PayPal to viewers
Run every line with sandbox credentials first, then the last line once with live credentials.
- Your PayPal business account is verified and able to receive payments in every currency you set on a plan or title.
- The client ID and secret in the admin match the environment switch, sandbox or live, and the gateway is enabled.
- A sandbox subscription shows as active in the admin and in the PayPal sandbox dashboard with the same subscription identifier.
- A sandbox order for a single title captures on return, records the rental window from the title, and opens playback.
- An order that is approved but not captured, for example when the capture is refused, does not open playback.
- Canceling a sandbox subscription from the viewer account is reflected in PayPal, and the plan ends on the subscriber record.
- Your support desk knows that coupon codes do not apply on PayPal checkout and has a discounted plan ready if a campaign needs it.
- Your team knows the refund path: refund the capture or cancel the subscription in PayPal first, then update the record in the admin.
- Live credentials are in place and one real low-value capture has landed in your PayPal activity before the launch announcement.
PayPal next to card gateways and inside the apps
PayPal is rarely the only gateway an operator runs; it is the second button next to a card checkout. On Flicknexs the two coexist on the same checkout page. The Stripe integration page describes the card path, with its subscription schedules and promotion codes, and the payment gateways page lists the 96 integrations in the payment service that can be switched on together. The viewer sees each enabled option and picks one. Because promotion codes apply only on the Stripe path, an operator running a coupon campaign will steer that campaign to the card button and price a separate plan for PayPal buyers if needed.
A PayPal subscription or rental is attached to the viewer's account, not to the browser, so the viewer signs in to the Android app, the iOS app, the Android TV app and the Fire TV app and finds the same content open. Purchases started inside the iOS or Android app go through Apple in-app purchase or Google Play Billing, described on their own pages, and carry the store's published fee. The web checkout with PayPal is the path most operators promote when they want to keep the store fee out of a sale.
Every gateway shares one pricing model. Recurring plans, per-title pay-per-view with rental windows, free-preview minutes and paid live events are defined on the video paywall once. PayPal supplies the billing subscription or the captured order; the platform decides what that payment opens by reading the plan or the title the viewer chose.
Which plan includes PayPal
Standard layers
The PayPal integration is part of every plan, including the web-only plan, because the payment service ships with the platform rather than as an add-on. Flicknexs adds no per-transaction charge on PayPal income. Plans are flat fees and Flicknexs takes no commission on your revenue; payment-gateway fees are between you and your gateway. See our pricing page for current plan and pricing details. PayPal's own per-transaction charge is set by PayPal and published on PayPal's pricing pages for your country.
Pricing & billing
F1 Standard is the web-only plan, with 300 GB of storage and 20 TB of bandwidth yearly; see our pricing page for current plan and pricing details. F1 Standard includes 300 GB of storage and 20 TB of bandwidth yearly for website streaming; see our pricing page for current plan and pricing details. Both include PayPal billing subscriptions and checkout orders on the website.
Annual savings
F2 Super includes 300 GB of storage and 20 TB of bandwidth yearly, and adds native Android and iOS mobile apps; see our pricing page for current plan and pricing details. Yearly billing on F1 to F4 costs less per month than monthly billing; see our pricing page for current plan and pricing details. On F2 and above, web purchases go through PayPal or another web gateway, while purchases inside the Android and iOS apps use the store's billing at the store's published fee.
Conclusion: what to do next
Already on Flicknexs
If you are already a Flicknexs customer, open payment gateway settings, confirm whether your PayPal credentials are sandbox or live, and run the checklist above. Give the approved-but-not-captured test real attention, because that is the case where a viewer writes in saying they paid; the PayPal activity log will show whether a capture ever completed.
Choosing a platform
If you are choosing a platform, ask each vendor which PayPal products it uses and how it confirms payment. The precise answer names billing subscriptions for recurring plans and orders with a server-side capture for one-time purchases, and it says that access opens only after the capture completes. Vendors that answer with a button screenshot have not answered the question.
Before a rights call
Read the companion pages next. The payment gateways page shows how PayPal sits among the other integrations on one checkout. The Stripe integration page covers the card path and is the only place coupon codes apply. The video paywall page explains the rental windows, free-preview minutes and paid live events that a PayPal capture opens.
Frequently Asked Questions
Everything you need to know about PayPal on Flicknexs.
Yes. PayPal is part of every plan, from the web-only plan upward, and Flicknexs adds no per-transaction charge. Plans are flat fees and Flicknexs takes no commission on your revenue; payment-gateway fees are between you and your gateway. See our pricing page for current plan and pricing details. PayPal's own charge is published on PayPal's pricing pages for your country.
Yes. A recurring plan becomes a PayPal billing subscription that the viewer approves inside PayPal and PayPal renews on the plan interval. The platform records the subscription identifier on the viewer's account and shows the plan as active in the admin.
Yes. Enable both in payment gateway settings and the viewer sees both on the same checkout page and picks one. Promotion codes apply only on the Stripe path, so route discount campaigns there and price a separate plan for PayPal buyers if needed.
For a one-time purchase, the platform captures the approved order on the server and opens playback only after the capture completes. For a subscription, the platform records the plan when the viewer returns from PayPal approval with the subscription identifier.
In your own PayPal business account. Flicknexs stores the subscription or order identifiers and the resulting access record. Refunds are issued in PayPal and disputes are handled in PayPal's resolution center; then the operator updates the subscriber's record in the admin.
No. The current build records subscriptions on return from approval and purchases on capture; it does not consume a background event feed. Failed renewals, cancellations made inside PayPal and disputes are read in the PayPal dashboard by the operator.
Yes. A pay-per-view title or a paid live event becomes a PayPal order for the price set on the title. Once the order is captured, the platform records the rental with the window, expiry and view count defined on the video paywall.
No. Promotion codes and the global coupon setting apply only on Stripe checkout. For a discount aimed at PayPal buyers, publish a separate plan at the discounted price for the campaign period instead of expecting a code field to appear.
The currency set on the plan or title in the admin is what the platform sends to PayPal. Which currencies your PayPal business account can receive, and any conversion PayPal applies, are decided by PayPal and described in PayPal's documentation for your country.
Yes. Enter sandbox credentials, set the environment to sandbox, and run a subscription and a single-title order with a PayPal sandbox buyer account. When the admin, the revenue report and the sandbox dashboard agree, switch to live credentials.
Yes. The subscription is attached to the viewer's account, so signing in to the Android, iOS, Android TV or Fire TV app opens the same content. Purchases begun inside the iOS or Android app go through the store's own billing instead.
Refund the capture, or cancel the billing subscription, in the PayPal dashboard where the money lives. Then open the viewer's record in the Flicknexs admin and end the rental or plan so access stops when you intend it to.