Recurring Payment Meaning, Types and How It Works

A recurring payment is a payment you approve once that is then charged automatically on a set schedule, for a fixed or changing amount, until you cancel it.

The definition of recurring payment covers a monthly software subscription, a cloud hosting bill and an insurance premium alike.

In India, card and UPI recurring payments run on a standing permission you give your bank, called an e-mandate, which the Reserve Bank of India (RBI) regulates.

Charges up to ₹15,000 go through without a fresh OTP each time, while larger ones need you to confirm again.

Every subscription payment follows the same pattern, whether you pay by card, UPI or bank account. You give permission once, the merchant charges you on schedule, and nothing more is needed from you while the arrangement stays active.

The three stages look like this:

1. Initial authorisation - you approve the merchant once, using your card, a UPI app or a bank mandate, and confirm it with an OTP or PIN.
2. Scheduled charges - the merchant charges you on the agreed date, for either the agreed amount or what you actually used that cycle.
3. No extra steps - you do nothing each month until you change the plan, pause it or cancel it.

When you save a card for repeat charges, the merchant does not keep your actual card number. It stores a substitute value instead, under RBI's card-on-file rules, and our explainer on payment tokenization covers how that works.

How UPI AutoPay runs recurring debits

UPI AutoPay is NPCI's recurring mandate system, and it works inside any UPI app you already use. You approve the mandate once with your UPI PIN, and later charges run on their own.

It is common for utilities, OTT plans, insurance and mutual fund SIPs.

Card and UPI mandates follow RBI's Digital Payments E-mandate Framework, 2026 (RBI/DPSS/2026-27/396). Each charge up to ₹15,000 runs without fresh approval, and your bank or app must notify you at least 24 hours before each debit.

How card standing instructions work

A standing instruction is the card version of the same idea. You register it once with an OTP from your card issuer, and the merchant can then charge your card each cycle as an automatic debit.

This is how most software, streaming and cloud bills reach a card.

Bank accounts use a separate route called an e-NACH mandate, which lenders, insurers and fund houses use to collect loan EMIs and SIPs straight from your account.

Recurring payments differ mainly in how the amount is set each cycle. Some change with use, some stay flat, and some end after a fixed number of charges.

Usage-based billing is the type most likely to surprise a finance team at month end, because the amount is only known once the cycle closes.

AWS describes its own pricing as "similar to how you pay for utilities like water and electricity. You only pay for the services you consume”.

Here is an illustrative example, not a real customer bill. A startup's cloud account is charged USD 800 in March and USD 1,150 in April on the same card authorisation.

You approved the vendor once, yet the April charge is higher because usage grew. Nothing new was signed, so the only warning you get is the bill itself.

Fixed plans are easier to forecast, though they grow when you add seats. Whatever the type, each one is a charge that repeats under one earlier approval.

For how these sit among other methods, see our overview of types of online payments.

Recurring billing is the merchant's system that raises each charge, while the recurring payment is the money leaving your account when it does. Both describe one event from opposite ends.

For a business paying for software, the benefits look like this:

• No missed renewals - a design team's Figma seats stay active through a busy month-end, because nobody has to remember to pay.
• Predictable spend - a per-seat plan such as a chat tool at a set price per user lets finance forecast the month's cost and spot a jump early.
• Less manual work - a team on ten monthly tools sets up ten mandates once instead of raising 120 separate payments a year (an illustrative count), so accounts payable handles exceptions only.
• Steady revenue for the vendor - the reason software companies push monthly and annual plans.

The downside is visibility. Charges up to ₹15,000 run without fresh approval, so nobody may check them each cycle.

Recurring charges, often set up as auto debits, cover far more than software. For a business, software and cloud bills usually dominate, while personal finances lean on insurance, investments and loans. Each tends to use a different method in India:

Most foreign software vendors bill in US dollars on a card, and that is where recurring charges most often break for Indian businesses.

Once you have more than a handful running, a simple register helps, and our guide on how to track SaaS subscriptions sets one up.

Most failed or unwanted charges come from the rules around the e-mandate rather than from an empty account. The common ones:

• The ₹15,000 approval limit - any recurring charge above ₹15,000 needs a fresh OTP or PIN. The higher ₹1,00,000 limit covers only insurance premiums, mutual fund subscriptions and credit card bills, so a software plan that grows past ₹15,000 fails if nobody approves it.
• Foreign SaaS declines - many global SaaS tools and cloud platforms bill through US card systems that do not register an Indian e-mandate, so your Indian bank may decline the charge at any amount.
• Replaced or reissued cards - a mandate sits on one card, so when that card is replaced or its holder leaves the company, the subscription can stop without warning.
• Forgotten renewals - a free trial converts to a paid plan, or a recurring invoice lands in a shared inbox, and the tool keeps billing for months.
• Missed pre-debit alerts - the 24-hour notice before each charge is your window to stop one you do not recognise, but only if someone reads it.

For foreign software bills, we built a prefunded USD virtual card, and our guide to virtual cards for SaaS subscriptions shows how it compares.

Your business funds Xflow Payments Inc. once and pays overseas vendors from that USD balance on a US-issued card, which vendors charge like any US card.

You can review and cancel Indian mandates any time in your bank app or your UPI app's mandate list.

The recurring payment meaning comes down to three parts: you approve once, the charge repeats, and it continues until you stop it.

That convenience only works while someone keeps track of what is running, and a few habits keep your recurring charges from failing or overrunning:

• Keep one register of active mandates - list each tool, the person who owns it, the card or account it bills and its renewal date, so you know what should be charging and when.
• Bill business tools to a company card - a mandate follows the card, so a subscription on an employee's personal card goes with them when they leave.
• Set a budget for usage-based plans - a spend alert, where the vendor or your card issuer offers one, or a monthly check of your usage shows a jump like USD 800 to USD 1,150 before the statement arrives.
• Name an approver for charges above ₹15,000 - a plan that grows past the limit needs a fresh OTP or PIN each cycle, so decide in advance who gives it, or the renewal fails.
• Act on the 24-hour notice and review quarterly - check each pre-debit alert you do not recognise, and every quarter cancel unused mandates in your bank or UPI app and with the vendor.

For a business, the harder cases are foreign software bills in US dollars, where your Indian card may not be able to accept the charge at all.

If that is where your subscriptions sit, a USD card that vendors charge like a US card is the usual fix.