OTT payment gateway integration: 96 gateways behind one checkout
OTT payment gateway integration on Flicknexs: 96 gateways including Stripe, Razorpay and PayPal, store billing in the apps, no commission.
Flicknexs routes web subscriptions and pay-per-view charges through any of 96 gateway integrations while the mobile apps bill through Apple and Google.
Trusted by industry leaders
50+ OTT platforms powered by Flicknexs
Quick answer: OTT payment gateway integration connects a streaming service's checkout to the processors that charge viewers for subscriptions and pay-per-view. Flicknexs ships 96 gateway integrations in its payment service, with Stripe, Razorpay and PayPal covering subscriptions and one-time charges, while the iOS and Android apps bill through the stores as their policies require.
Flicknexs provides payment gateways as part of its white-label OTT platform. Flicknexs routes web subscriptions and pay-per-view charges through any of 96 gateway integrations while the mobile apps bill through Apple and Google.
Why the gateway list matters more than the gateway count
The gateway is the part of a streaming service viewers never think about until it fails. A card declined in one country, a currency the processor does not settle, a subscription that renews twice: each one is a support ticket and, often, a lost subscriber. Operators choose a platform partly on which gateways it can talk to, because the right gateway for a service in Mumbai is not the right gateway for one in Manchester. Flicknexs carries 96 gateway integrations in its payment service so that choice is yours rather than the platform's.
Counting integrations is easy; knowing what each one does is what matters. A gateway that can take a one-time payment is not the same as one that can create, update and cancel a recurring subscription, schedule a plan upgrade, or accept a promotion code. This page states what the three most used gateways in the platform code do for subscriptions and for one-time charges, how verification works when the viewer returns from checkout, and how the mobile apps bill through the stores instead. It is written from the code rather than from a brochure.
The security model follows the gateways' own. Stripe's payments documentation describes a hosted checkout in which card details are entered on a page Stripe serves, so the operator's platform never handles the card number; Razorpay and PayPal work the same way through their hosted flows. Flicknexs uses those hosted checkouts and verifies the result server-side when the viewer returns, which keeps card data out of the platform and out of your compliance scope. The gateway charges its published fee; the plan fee is flat.
What the gateway integration does on Flicknexs
Every row below is in the platform code. The three named gateways are the ones with full subscription support that most operators connect first.
96 gateway integrations
The payment service holds 96 gateway integrations; you connect the ones your regions need.
Stripe subscriptions
Recurring plans, scheduled plan upgrades, one-time pay-per-view charges and promotion codes at checkout.
Razorpay subscriptions
Subscriptions created, fetched, updated and canceled through Razorpay, plus one-time orders for pay-per-view.
PayPal billing
Billing subscriptions for plans and checkout orders with capture for one-time purchases.
Server-side verification
On return from checkout the platform re-checks the session with the gateway before granting access.
Plan currency
Each plan sets the currency charged, so it bills in the currency you set.
Store billing in apps
iOS sells through StoreKit and Android through Google Play Billing, mapped to your plans.
Revenue reports
Subscription and pay-per-view revenue reported by month across every connected route.
Source: Flicknexs platform documentation and architecture specification, 2026-09-03.
How OTT payment gateway integration works on Flicknexs
Six things to understand before you connect anything: what the count means, what each main gateway does, how payment is verified, and how the apps differ.
What 96 integrations means
Stripe: subscriptions, upgrades and one-time charges
Razorpay: recurring billing for India
PayPal: billing subscriptions and checkout orders
Verification on return, not webhooks
The store routes in the apps
How to set up a payment gateway in the Flicknexs admin
Five steps from choosing a processor to mapping store products. Use test keys until the last step.
- 1
Choose the gateway for each region
Decide which processor will serve which audience before you touch the admin. A common pattern is Stripe for card markets, Razorpay for India and PayPal where wallets dominate. Consider settlement currency, local payment methods and whether you need subscriptions or only one-time charges on that route.
- 2
Enter the credentials
Open the payment settings and add the API keys for each gateway you will use. Use test keys first. Each integration reads its own settings, so a mistyped key on one gateway does not affect another. Keep the live keys in a password manager; the admin stores them but you should hold the originals.
- 3
Create plans with the right currency
Add subscription plans with name, price and interval. The currency charged is taken from the plan, so a service billing in two currencies creates two plans rather than one plan with a conversion. Per-title pay-per-view prices are set on the title, per quality level, in the same currency as the route.
- 4
Run a purchase on every route
With test keys, buy a plan and a rental through each gateway you connected. Confirm the viewer returns to the site, the server-side re-check passes and access is granted. Then switch to live keys and buy once more with a real card, refunding it from the gateway dashboard afterwards.
- 5
Map the store products
If you ship the mobile apps, create products in App Store Connect and Google Play Console for each plan and per-title price, then map the product IDs in the admin. For Android, set up the real-time developer notifications topic so renewals and cancellations reach the platform.
Limits and what the integration does not do
These are the boundaries that surprise operators after launch. Each is stated as it stands in the platform code.
No Stripe webhooks
Coupons on Stripe only
Apple receipt validation is not implemented
Roku billing is a per-build item
No automatic gateway selection
A worked example: a regional news channel billing in two markets
Pre-launch checklist for payment gateways
- Confirm each plan’s currency matches the settlement currency of the gateway that will charge it.
- Buy a plan and a rental with test keys on every gateway you connected and confirm access is granted on return.
- Make one live purchase per gateway with a real card, then refund it from the gateway dashboard.
- Cancel a test subscription from the viewer side and confirm the gateway shows it canceled.
- Trigger a plan upgrade on Stripe and confirm it appears as a scheduled change, not a second subscription.
- Map every App Store and Google Play product ID before you submit the apps for review.
- Set up the Google Play real-time developer notifications topic and confirm a test renewal reaches the platform.
- Decide where promotion codes will run, since they apply on the Stripe checkout only.
- Note the gateway’s published fee for each route so your revenue report reconciles against payouts.
- Store live API keys in a password manager and rotate them if a team member with admin access leaves.
How the gateways work with the apps and the paywall
Which plan includes payment gateways
Standard layers
Pricing & billing
Annual savings
Conclusion: what to do next
Already on Flicknexs
Choosing a platform
Before a rights call
Frequently Asked Questions
Everything you need to know about payment gateways on Flicknexs.
The payment service contains 96 gateway integrations. That figure is taken from the platform code on the date at the top of this page, not rounded up. You connect the ones your audience uses; Stripe, Razorpay and PayPal are the ones with subscription support that most operators start with.
Yes. You can connect several gateways at the same time, and each connected gateway is a route your web checkout can offer. The usual pattern is one gateway per region, such as Razorpay for India and Stripe elsewhere, with a plan in each currency because the currency is taken from the plan.
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. The gateway's own processing charge is the gateway's published fee and is deducted before payout.
In the platform code, Stripe creates subscriptions and schedules plan upgrades, Razorpay creates, fetches, updates and cancels subscriptions, and PayPal creates billing subscriptions. Many of the other integrations handle one-time charges; check the specific gateway with the team before you plan recurring billing on it.
By re-checking the checkout session server-side when the viewer returns to the site. The platform asks Stripe whether the session is paid before it activates the plan or records the rental. It does not use Stripe webhooks, so there is no webhook endpoint or secret to manage.
The currency charged is taken from the plan. To bill in two currencies you create two plans, one per currency, and offer each to the right audience. The gateway settles in the currencies it supports, so check that before you create the plans and set the prices.
No. Promotion codes and the admin coupon setting apply on the Stripe-hosted checkout only. Razorpay, PayPal and the other integrations charge the plan at list price, and the store-billed mobile apps do not accept codes. Operators on other gateways run offers by adjusting the plan price for a period.
Through the stores, as their policies require. The iOS app sells through StoreKit and the purchase is recorded from the app. The Android app sells through Google Play Billing; real-time developer notifications are decoded server-side and purchase tokens are verified against Google. Product IDs map to plans in the admin.
No. Server-side receipt validation and App Store Server Notifications are not implemented. The iOS purchase is made through StoreKit and recorded from the app, and access is granted from that record. Android verification against Google is implemented, including renewal, cancellation and expiry notifications.
Roku Pay is not in the platform code. TV apps are available as add-ons on any plan, allowing you to expand your reach to more devices; see our pricing page for current plan and pricing details. Roku Pay integration is scoped inside that build on request, and web or mobile subscribers sign in on Roku with a code without buying again.
No. Each gateway's hosted checkout collects the card details on a page the gateway serves, and the platform receives a result to verify rather than the card number. That keeps card data out of the Flicknexs database and out of your compliance scope for card handling.
Yes, for new purchases: connect the new gateway and route new checkouts to it. Existing subscriptions stay with the gateway that created them until they are canceled or re-created, because the recurring agreement lives at that gateway. Plan the switch around renewal dates.