Subscriptions, memberships and repeat deliveries need a reliable way to collect money over time. A fresh checkout every cycle creates missed due dates and operational work.
A recurring payment arrangement lets a business initiate future charges after the customer provides valid authorization. Automated billing coordinates the broader process: it calculates what is due, schedules the collection, records the result and manages the subscription lifecycle. The two concepts work together, but they are not identical.

Table of contents

• What is a recurring payment?
• Recurring payment vs automated billing
• How recurring payments work
• Types of recurring billing models
• Payment methods used in India
• Benefits and risks for businesses
• How to implement automated billing
• How PayU can help
• FAQs

What is a recurring payment?

A recurring payment is a payment collected from a customer on an agreed schedule or according to agreed billing terms, using a payment mandate or stored payment arrangement that the customer has authorized. Common frequencies include weekly, monthly, quarterly and annual, although permitted schedules depend on the payment rail and provider.
The customer first accepts a plan and authorizes a mandate. Later requests are initiated under its amount, validity, frequency and applicable controls. This is not permission to charge at will.
Customers should understand the price, frequency, renewal and cancellation terms and receive required notifications and controls.

Recurring payment vs automated billing

Recurring payment describes the movement of money. Automated billing manages what should be charged and when.
An automated billing platform may:

• manage plans, trials, upgrades and add-ons;
• calculate charges and generate billing records;
• trigger requests under valid mandates;
• send notifications and handle failures;
• record cancellations and refunds; and
• provide collection reports.

A business can use automated billing even if some invoices are paid manually. Conversely, a recurring debit without good billing logic can create incorrect charges, poor customer experiences and difficult reconciliation.

How recurring payments work

1. The customer chooses a plan

The customer sees the amount or pricing basis, billing frequency, trial terms, renewal policy and cancellation conditions. For variable billing, the business should clearly explain how usage or the payable amount will be determined.

2. The customer creates a mandate

The checkout collects consent through an eligible card, UPI AutoPay or supported bank mandate. After authentication, the mandate records relevant amount, frequency, validity and status details.

3. The business stores a safe reference

The merchant should use tokens or mandate references provided by its payment partner rather than storing sensitive credentials unnecessarily. Access to mandate and subscription data should be restricted and auditable.

4. The billing system creates the next charge

At each event, the system checks subscription and mandate status, calculates the amount and creates a billing record, applying plan changes or usage rules.

5. Required notifications are sent

India's e-mandate framework includes customer-protection requirements for recurring transactions. RBI's framework generally requires the issuer to send a pre-debit notification at least 24 hours before a charge covered by the framework, with limited exceptions such as specified auto-replenishment use cases. UPI AutoPay information from NPCI similarly highlights pre-debit notification and customer mandate controls.
Businesses should use current official and provider documentation for requirements applicable to their rail and use case.

6. The payment is attempted

On the due date, the payment provider submits the transaction under the authorized mandate. The bank or relevant participant evaluates it. The payment can succeed, fail or remain pending; a mandate does not guarantee that every debit will complete.

7. The result updates service and accounts

The billing system marks the invoice, updates access under the business's policy and messages the customer. Successful payments flow through settlement and reconciliation.

8. Failures enter a recovery process

A failed debit may reflect insufficient funds, an expired instrument, a revoked mandate, bank control or a technical condition. Classify it before requesting a new method, retrying or applying disclosed service terms.

Types of recurring billing models

• Fixed recurring billing

The customer pays the same amount each cycle, as with a monthly software plan or gym membership. This model is simpler to explain, forecast and reconcile.

• Usage-based billing

The amount depends on measured consumption, such as API usage, storage or units delivered. Metering accuracy, invoice transparency and mandate limits become especially important.

• Instalment payments

A fixed total is collected in scheduled parts. Installments have a defined end, unlike an open-ended subscription that renews until cancellation.

• Automatic replenishment

A debit is triggered when a balance falls below a customer-set threshold rather than on a fixed calendar date. This is a specialized use case with its own applicable requirements.

Payment methods used for recurring payments in India

• Cards

Eligible debit and credit cards can support recurring payments through an e-mandate arrangement. The initial mandate setup requires the applicable authentication, and later transactions follow RBI and card-network requirements. Tokenization and provider-supported references can reduce the merchant's need to handle card data directly.

• UPI AutoPay

UPI AutoPay lets customers create e-mandates through supported UPI apps for use cases such as subscriptions, bills, insurance and other eligible recurring collections. NPCI states that customers can manage functions such as modification, revocation, pause and unpause through supported flows. Availability can vary by participating bank, UPI app, merchant and use case.

• Bank mandates or eNACH

Electronic bank mandates can enable recurring debits. Setup, bank coverage and processing vary, so merchants should check current provider documentation.
The best mix depends on customer preference, ticket size, eligibility and integration support. A fallback can help when the primary instrument is unusable.

Benefits and risks for businesses

Recurring payments can reduce follow-up, simplify renewals and support structured forecasting. Customers benefit when payments follow transparent terms without remembering every due date.
Risks remain. Failed renewals cause involuntary churn, incorrect logic can charge the wrong amount, and weak webhook handling can update access incorrectly. Mandates and payment data also create security responsibilities.
Teams need clear ownership for plan configuration, refunds, disputes and billing exceptions.

How to implement automated billing

• Define the commercial rules

Document prices, frequency, trials, proration, taxes, grace periods, cancellations, refunds and access policy. Define how usage reaches billing.

• Choose supported payment rails

Evaluate cards, UPI AutoPay and bank mandates based on customer fit and provider coverage. Confirm current mandate limits, authentication, notification and retry requirements directly from official and provider sources.

• Design for explicit consent and control

Show the recurring nature before confirmation, store consent and mandate status, and provide straightforward plan controls.

• Build a reliable state model

Keep subscription, invoice, mandate and payment states separate. Process webhooks idempotently and verify events using current provider guidance.

• Create a measured recovery policy

Use failure reasons to govern retries. Limit and space attempts, notify customers and let them update payment methods.

• Reconcile every billing cycle

Match invoices to payment attempts, provider transactions, settlements, refunds and bank credits. Monitor active subscriptions, upcoming renewals, collection success, failed-payment recovery, cancellations, mandate revocations and disputed charges.

• Test lifecycle scenarios

Test signup, trial conversion, success, failure, pending status, plan changes, duplicate events, revocation, cancellation, refund and reactivation.

How PayU can support recurring payments

PayU's Recurring Payments Suite supports subscription collection through payment methods including eligible cards, UPI AutoPay and net banking mandates. Businesses can configure billing cycles and use APIs or dashboard-based options, while reporting helps teams track subscription and transaction outcomes. PayU also documents mandate creation, pre-debit and recurring transaction flows for developers.
Payment-method availability, limits, settlement terms and implementation requirements can vary. Businesses should confirm their approved configuration and refer to the latest PayU Recurring Payments Suite page and PayU recurring-payment documentation before going live.

FAQs

1. Is a recurring payment the same as a subscription?

No. A subscription is the commercial relationship or plan. A recurring payment is one way to collect the amounts due under that relationship.

2. Does a mandate guarantee every recurring payment will succeed?

No. A debit may fail because of insufficient funds, instrument status, bank controls, mandate status, authentication or technical issues.

3. Can customers cancel a recurring payment?

Customers should have controls consistent with the payment method, mandate terms and applicable rules. UPI AutoPay supports mandate-management functions such as pause or revocation in supported flows. Merchants should also provide clear subscription cancellation paths.

4. What happens when an automated payment fails?

The billing system should record the reason, notify the customer where appropriate and apply a defined recovery policy. Depending on the cause, the next action may be a permitted retry, a new payment method or account action under the disclosed service terms.

5. Are recurring payments suitable only for SaaS businesses?

No. They can support memberships, education, insurance, utilities, media, repeat deliveries, installments and other eligible models where customers pay on a schedule or according to agreed billing terms.