Razorpay integration for OTT platform

The admin stores your Razorpay key ID and key secret and lets you switch the gateway on for viewers. When a viewer chooses to pay through Razorpay, the checkout is rendered by Razorpay, so the UPI handle or the card number is entered into Razorpay's form. The platform holds the keys on the server and never exposes the secret to the browser.

When the viewer confirms a recurring plan, the platform creates a Razorpay subscription for that plan's price and interval and hands the viewer to Razorpay checkout to authorize the first charge and the mandate. Razorpay owns the mandate from that point and debits renewals on the interval. The platform stores the subscription identifier against the viewer's account and records the plan as active.

The platform does not keep its own renewal clock for Razorpay. When it needs to know whether a subscription is still live, it fetches the subscription from Razorpay and reads the status Razorpay returns, such as active, pending, halted or canceled. That status decides whether the viewer keeps access. If Razorpay reports the mandate stopped, the operator sees that on the subscriber's record.

A viewer who moves from a monthly plan to an annual plan is not given a second subscription. Flicknexs calls Razorpay's update on the existing subscription so the new plan takes over, and the admin reflects the new plan on the subscriber. This keeps one mandate per viewer, which matters because each mandate is something the viewer authorized and can see in their bank or UPI app.

When a viewer cancels from their account page or an operator cancels from the admin, the platform calls Razorpay to cancel the subscription. Razorpay stops future debits and the platform marks the plan as ended. Access can be kept until the end of the paid period or stopped at once, depending on how the operator handles the cancellation on the subscriber's record.

For a film rental, a purchased title or a paid live event, the platform creates a Razorpay order for the amount set on the title in the admin, and Razorpay checkout collects payment against that order. Once paid, the platform records the purchase with the rental window from the video paywall and shows it in the pay-per-view revenue report for that month.

Which methods appear at checkout, whether a given method supports recurring mandates, and what Razorpay charges per transaction are decided by Razorpay for your account and region and are documented on Razorpay's own site. Flicknexs passes the amount, the currency and the interval; it does not choose or add methods. If a method is missing, the answer is in your Razorpay account settings.

The promotion codes and the global coupon setting described on the coupons and discounts page work only on Stripe checkout. A viewer paying through Razorpay sees no coupon field. If a discount is essential for an Indian campaign, price a separate plan at the discounted amount and publish it for the campaign period instead.

The admin has no field for trial days, so a Razorpay subscription created by Flicknexs charges from the first authorization. To let viewers sample content before they commit, set free-preview minutes on titles and episodes on the video paywall; that needs no mandate and no Razorpay call at all.

The platform learns that a mandate halted or a renewal failed by fetching the subscription from Razorpay, not by receiving a push from Razorpay. An operator who wants to act quickly on failed renewals should watch the Razorpay dashboard, where the failure appears first, and then adjust the subscriber's record in the admin if access should end.

Razorpay is a web checkout. Purchases made 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 Razorpay on the website is signed in on the apps with the same account and keeps that access.