Not every recurring charge is the same size each month. A distributor’s order value moves with demand. A cloud services bill moves with usage. A borrower may owe a penalty on top of a scheduled installment. Fixed-amount mandates cannot accommodate any of this, which is why NPCI built a second option into UPI Autopay.
A variable-amount mandate lets a business register a ceiling instead of a fixed figure. The customer authorises that ceiling once. Every debit after it can be any amount at or below the line.
What the customer is actually approving
At registration the mandate carries four parameters: a maximum amount, a frequency, a start date and an end date. The maximum is the only figure the customer commits to. If the cap is set at Rs 8,000 and the bill for a given cycle comes to Rs 4,300, then Rs 4,300 is what leaves the account.
This distinction gets missed frequently. Customers reading a mandate approval screen see the cap and assume it is the charge. It is not. It is the upper bound of what can be charged without fresh authorisation.
Variable mandates also support an “as presented” frequency, where the debit date is not fixed at registration. Utility billing and usage-based invoicing generally sit here.
Where the cap sits against NPCI’s limits
Two thresholds govern what happens next. Under the RBI e-mandate framework, recurring debits up to Rs 15,000 clear without additional factor authentication once the mandate is active. Above that figure the customer must authenticate the individual debit with a UPI PIN.
NPCI circular UPI/OC-151A, dated 14 December 2023, raised the threshold to Rs 1,00,000 for a defined set of categories: insurance premiums, mutual fund subscriptions and credit card bill payments. Eligibility is determined by the merchant category code submitted in the mandate creation payload, not by how a business describes itself. A miscoded mandate forfeits the higher limit.
The practical consequence deserves spelling out. Setting a cap of Rs 25,000 outside those categories does not give a business Rs 25,000 of frictionless collection. It gives Rs 15,000 of frictionless collection and a PIN prompt for anything beyond it. Cycles that cross the line will fail more often, because success now depends on the customer being present and responsive.
The pre-debit notification carries more weight here
Every mandate under the framework requires notice to the customer at least 24 hours before a debit. For fixed mandates this is largely a formality, since the amount never changes. For variable mandates it is the only point at which the customer learns the actual figure for that cycle.
Businesses that treat the notification as a compliance checkbox tend to see more disputes and more cancellations. Businesses that use it to explain an unusually high cycle before the money moves tend not to.
Retries and failure handling
Since August 2025, NPCI has tightened execution rules for Variable UPI autopay mandates. Each mandate receives one execution attempt per cycle followed by up to three retries, sequenced by the mandate’s own number. Payment service providers must throttle these at a moderated transaction rate, and recurring debits are steered towards off-peak windows rather than morning traffic hours.
For variable billing this changes retry strategy. A large debit that fails on insufficient funds is unlikely to clear on an immediate second attempt. Retries timed around salary credit dates recover materially more than retries fired back to back.
Setting the cap
A cap set too low forces manual collection every time a cycle exceeds it. A cap set far above realistic billing raises hesitation at the registration screen and pushes ordinary debits into PIN territory for no reason.
Reviewing twelve months of billing history and placing the ceiling modestly above the highest observed charge is a reasonable starting position for most businesses working with variable UPI Autopay. That figure should be revisited as billing patterns shift rather than left untouched for the life of the mandate.



