Recurring Payment

What is Subscription Hub?

Subscription Hub is Jio Payment Solutions Limited's recurring payments platform that lets businesses collect fixed or variable amounts from their customer at regular intervals, without asking the customer to pay manually on every cycle.

At its core, Subscription Hub automates the two things every recurring-billing business needs:

• A one-time customer consent — the customer authorizes a merchant to debit their bank account or card, up to a specified amount, at a specified frequency. This is called mandate creation.
• Ongoing, unattended collections — once the mandate is active, the merchant triggers debits against it on the agreed schedule, with no further action needed from the customer for each individual payment.

This mandate-based model is what distinguishes recurring payments from a regular one-time checkout. A regular payment authenticates and settles a single transaction. A mandate authenticates the right to debit repeatedly , the authentication happens once, up front, and every subsequent debit rides on that standing authorization (subject to the notification and execution rules ).

Subscription Hub is built to be compliant with the RBI's e-mandate framework and NPCI's UPI AutoPay specifications, including the mandatory pre-debit notification requirement for recurring transactions.

Payment methods supported

Both rails are exposed through the same Subscription Hub interfaces — the Dashboard and the API set — so a merchant can offer either or both payment methods to their customers without maintaining separate integrations.

Use cases

Subscription Hub is designed for any business that bills a customer more than once for the same relationship. Common patterns include:

• Digital subscriptions — OTT platforms, news and content subscriptions, SaaS and app subscriptions billed monthly or annually
• Financial services — mutual fund SIPs, recurring investment contributions
• Membership and wellness — gym memberships, fitness apps, wellness programs with recurring monthly fees
• D2C "subscribe and save" — consumables and replenishable goods (groceries, personal care, pet food) shipped and billed on a recurring cycle
• Utility and recurring bills — variable-amount recurring payments such as utility bills, where the debited amount can change each cycle within a pre-authorized ceiling
• Loan and EMI collections — automated EMI collection

Customer experience: the recurring payment lifecycle

Regardless of payment method or integration approach, every mandate moves through the same four stages:

1. Registration — The customer sets up the mandate. They review the business name, the debit amount (or ceiling, for variable amounts), the frequency, and the start and end dates, then authenticate to confirm. This is the only step that requires the customer's active participation.
2. Pre-debit notification — Ahead of each recurring debit, the customer is notified (in-app, SMS, or email, depending on payment method and amount) with the amount and date of the upcoming debit. This is a regulatory requirement, not an optional courtesy — see the payment-method-specific pages for exact timelines.
3. Execution — On the scheduled date, the debit is triggered against the mandate. No customer action is needed unless the transaction crosses a threshold that requires additional authentication
4. Modification, pause, or revocation — The customer (or the merchant, depending on the flow) can pause, modify, or cancel the mandate at any time. Once revoked, a mandate cannot be reinstated — a fresh registration is required.

The pages that follow walk through each of these stages in detail for the two supported payment methods, and describe both ways to integrate: the no-code Dashboard and the API.

How to integrate

Subscription Hub offers two paths, so that merchants can choose based on their need:

Continue to:

• Card-based (Standing Instruction) flow
• UPI AutoPay flow
• No-code Dashboard flow