UPI mandate
A UPI mandate (UPI AutoPay e-mandate) is a standing instruction set up over UPI that authorises a payee to debit a fixed or capped amount from a bank account on a schedule, used for mutual fund SIPs and other recurring payments, governed by the National Payments Corporation of India (NPCI) under the Unified Payments Interface (UPI) 2.0 framework. It allows a payer’s bank to pre-authorise a debit of up to a specified maximum amount on a specified future date or on a recurring schedule, without requiring the payer to re-enter a UPI PIN at the time of each debit. The mandate construct was introduced in UPI 2.0, released by NPCI in August 2018, and the recurring-payment form was rolled out as UPI AutoPay in July 2020.
UPI mandates are distinct from immediate UPI push or pull transfers, in which funds are debited and credited in real time. A mandate creates a pre-authorisation lien or a revocable debit instruction that is executed later. This deferred execution model makes mandates suitable for:
- IPO applications through the UPI ASBA mechanism.
- Systematic Investment Plan (SIP) instalments for mutual funds.
- Insurance premium scheduled debits.
- Subscription billing (streaming, software, e-commerce).
- Recurring utility bill collections.
For the IPO-specific application, see UPI 2.0 mandate explained . For guidance on approving a mandate in a UPI app, see How to approve a UPI mandate for an IPO application .
Background: the gap that mandates fill
Before the mandate construct, UPI could handle only real-time transfers. A payee who wished to collect a future payment had to initiate a fresh collect request on the payment date, which required the payer to be online and attentive at the right moment. For capital markets applications this was inadequate: SEBI’s ASBA process for IPOs requires funds to be blocked from the application date until allotment, with actual debit contingent on allotment outcome. An immediate debit followed by a refund on non-allotment was operationally possible but unacceptable under SEBI’s blocked-amount design.
The mandate construct provided a solution: the payer pre-authorises a debit on application day, the bank blocks the funds (without debiting the account), and the actual debit occurs only if and when allotment is confirmed. This mirrors the blocked-amount model already used by bank ASBA through SCSB but extends it to UPI-based applications.
Types of UPI mandates
One-time mandate
A one-time mandate authorises a single debit on a specified future date. The most common application is the IPO ASBA mandate:
- Creation: The investor submits an IPO bid through a UPI-enabled broker. The sponsor bank for the issue (acting as the collecting bank) creates a one-time mandate request.
- Authorisation: The investor approves the mandate in their UPI app, entering their UPI PIN. The payer PSP (the investor’s bank) places a lien on the account for the bid amount.
- Execution: If allotment is confirmed, the sponsor bank triggers the mandate execution and the bank debits the allotment amount.
- Lapse: If no allotment, the mandate expires on its validity date and the lien is released without any debit.
Recurring mandate
A recurring mandate authorises multiple debits, each for up to the specified maximum amount, on a defined schedule (daily, weekly, monthly, annually, or as-and-when-presented). Recurring mandates are used for:
- SIP instalments: The asset management company’s collecting bank sends an execution request on each SIP date; the investor’s bank debits without requiring a fresh PIN each time.
- Insurance premiums: The insurer’s collecting bank executes on premium due dates.
- Subscription billing: A platform can debit on each renewal date without re-obtaining the customer’s credentials.
A recurring mandate includes a maximum-amount-per-debit cap, an end date or a maximum number of debits, and a revocation mechanism. For detailed coverage of the recurring mandate in IPO contexts, see UPI 2.0 mandate explained .
NPCI specification
NPCI publishes the UPI mandate specification as part of the UPI API documentation available to licensed PSP banks and third-party application providers. Key parameters in the mandate creation request include:
| Parameter | Description |
|---|---|
txnType | CREATE / REVOKE / EXECUTE / PAUSE / UNPAUSE |
amount | Maximum debit amount (not necessarily the executed amount) |
amountRule | EXACT (only the stated amount may be debited) or MAX (up to the stated amount) |
frequency | ONETIME, DAILY, WEEKLY, MONTHLY, YEARLY, ASPRESENTED |
recurrenceRule | Start date, end date, max number of debits |
validityStart | Earliest date on which execution is permitted |
validityEnd | Expiry date; mandate lapses if not executed by this date |
purpose | Coded purpose field (e.g., 14 for IPO ASBA, 01 for subscription) |
block | Flag indicating whether funds should be lien-blocked rather than immediately debited |
remark | Free-text note visible to the payer on approval |
The mandate creation request is sent by the payee PSP to the NPCI switch, which routes it to the payer PSP. The payer PSP presents it to the payer’s UPI app as a collect-request-type notification.
Lifecycle
1. Creation
The payee (or the payee’s collecting bank or PSP) generates a mandate creation request through the UPI mandate API. The request specifies all mandate parameters and is signed by the payee PSP.
2. Routing
The NPCI switch receives the creation request, validates the payer VPA, resolves it to the payer’s PSP, and forwards the request.
3. Authorisation by payer
The payer receives a push notification in their UPI app, opens the pending requests section, reviews the mandate details (payee name, amount cap, validity, frequency), and enters their UPI PIN to authorise. This PIN entry authenticates the mandate creation without triggering an immediate debit.
4. Lien or pre-authorisation
On successful PIN entry, the payer PSP confirms the mandate to NPCI and, if the mandate carries a block flag, instructs the payer’s bank to place a lien on the account for the mandate amount. For IPO ASBA mandates, the lien is placed immediately and the available balance visible to the customer drops by the blocked amount.
5. Execution
On the execution date (for one-time) or on each recurrence date (for recurring), the payee’s collecting bank sends an execution request to NPCI. NPCI forwards it to the payer PSP, which instructs the payer’s bank to debit the account. The debit amount can be equal to or less than the mandate’s maximum amount (subject to the amountRule).
For IPO mandates, execution is triggered by the registrar and transfer agent after allotment confirmation; only the allotted value is debited, not the full bid amount.
6. Settlement
The debit is settled through the standard UPI/IMPS settlement process. The payee’s account is credited immediately; interbank settlement is completed through NPCI’s net settlement cycle.
7. Revocation
A payer can revoke (cancel) a mandate at any time before execution, through their UPI app, by sending a revocation request. The payer’s PSP forwards a REVOKE request to NPCI. On successful revocation, the lien is released and the account’s available balance is restored. Revocation is irreversible; a new mandate must be created if the payee still wishes to collect.
For IPO mandates, revocation before the bid closing cutoff (5 PM IST on bid closing day) is treated as a bid withdrawal by the registrar.
8. Lapse
An unexecuted mandate lapses automatically on its validityEnd date. Any lien associated with a lapsed mandate is released by the payer’s bank. No debit can be triggered on a lapsed mandate.
Key failure codes
| Code | Meaning | Typical resolution |
|---|---|---|
| U16 | Duplicate mandate detected (same payer-payee-amount combination already exists and is active) | Wait for the duplicate to expire or be revoked before re-creating |
| ZD | Duplicate transaction / mandate collision | Same as U16; usually resolves within 15 minutes |
| U30 | Technical failure at payer PSP or NPCI switch | Retry after a short wait; if persistent, try a different UPI app linked to the same account |
| U09 | Payer’s VPA not registered | Verify the VPA and re-link the bank account |
| U68 | Mandate revoked by payer | A new mandate must be created |
| U73 | Mandate already executed | Mandate has been debited; no further execution possible |
| U69 | Mandate lapsed (past validity date) | Payer must re-apply; new mandate creation required |
| BT | Account balance insufficient at execution time | Ensure sufficient balance before execution date; the mandate cannot be executed if lien was released and balance is now insufficient |
Security model
The mandate authorisation relies on the same two-factor authentication as any other UPI transaction: the registered device (possession factor) and the UPI PIN (knowledge factor). No collect request, mandate creation, or mandate execution can proceed without the payer’s UPI PIN entered at the time of mandate authorisation.
A key distinction from ordinary fund transfers is that the UPI PIN is entered only once, at mandate creation. Subsequent recurring executions do not require a fresh PIN. This convenience introduces a risk: if a payer is deceived into authorising a mandate for a higher-than-intended amount or to a fraudulent payee, all future executions under that mandate proceed without further authentication. The security controls are:
- Payer visibility of mandate details before PIN entry (payee name, amount cap, frequency, validity).
- UPI app notifications at the time of each execution (giving the payer an opportunity to detect and report unauthorised mandates).
- Revocation capability at any time before execution.
- NPCI’s fraud monitoring at the switch level.
Mandate in non-IPO use cases
Systematic Investment Plans (SIPs)
Recurring UPI mandates are increasingly used by mutual fund platforms for SIP (Systematic Investment Plan) debits. The investor registers a recurring mandate, monthly, for example, authorising the asset management company’s collecting bank to debit the SIP instalment each month without requiring re-authentication. The AMFI-registered platform initiates the mandate creation; the investor authorises once; subsequent monthly debits are automatic.
The key parameters for a SIP mandate differ from an IPO mandate:
frequencyis set toMONTHLYrather thanONETIME.amountRuleis typicallyEXACT(the SIP amount is fixed) orMAX(for step-up SIPs).validityEndis set to the investor’s chosen SIP tenure end date, which may be several years in the future.- No lien or block is placed between debits; funds are available until the debit execution date.
A payer may hold multiple active recurring mandates simultaneously (one per SIP, one per insurance policy, one per subscription). NPCI does not impose a hard limit on the number of concurrent active mandates per VPA, though PSP banks may impose their own limits.
Insurance premium collection
IRDAI-regulated insurers use one-time and recurring UPI mandates for premium collection. Annual premium mandates are typically one-time mandates with an ASPRESENTED recurrence variant: the amount per execution can vary (relevant for policies where the premium is revised annually). The amountRule is set to MAX at the maximum expected premium level, and the executing bank is permitted to debit up to that amount per execution.
Subscription billing
Over-the-top (OTT) streaming platforms, software-as-a-service providers, and e-commerce subscription platforms have adopted UPI recurring mandates as an alternative to auto-debit via saved card credentials. The UPI mandate has advantages for merchants: lower failure rates (UPI infrastructure is more reliable than card auto-debit networks), lower fraud rates, and no card expiry problem. For consumers, the mandate is visible and revocable through the UPI app, providing more transparency than card-level auto-debit.
Government levy collection
Some state government departments use UPI mandates for vehicle tax, property tax, and utility collections. The mandate creation is initiated at the citizen portal; the citizen approves via UPI app; execution occurs on the tax due date.
Pause and unpause
UPI 2.0 introduced PAUSE and UNPAUSE transaction types for recurring mandates. A payer who wishes to temporarily suspend a recurring mandate without revoking it can submit a pause request through their UPI app. The mandate remains active but no executions are permitted during the pause period. On UNPAUSE, executions resume from the next scheduled date.
Pause is not applicable to one-time mandates (which either execute or lapse). For recurring mandates, pause provides a middle ground between active execution and full revocation. Common use cases include pausing a subscription during a temporary leave of absence or pausing an SIP mandate during a financial hardship period.
Mandate notifications to payer
NPCI requires PSP banks and TPAPs to notify the payer at multiple mandate lifecycle events:
- Creation request: Push notification and in-app pending-request badge when a mandate request arrives.
- Authorisation confirmation: Notification and confirmation screen when the payer authorises the mandate.
- Execution notification: Notification at the time of each mandate execution (recurring or one-time), confirming the amount debited.
- Revocation confirmation: Notification when a mandate is successfully revoked.
- Lapse notification: Some apps notify when a mandate lapses without execution.
These notifications are the payer’s primary mechanism for detecting unauthorised mandates. NPCI’s fraud guidelines require PSP banks to maintain notification delivery logs and to investigate complaints where a notification was not received.
Regulatory context
UPI mandates are governed by:
- NPCI UPI 2.0 Operational Circular: Defines mandate lifecycle, API parameters, and participant obligations.
- SEBI Circular on UPI ASBA (2019, 2022, 2023): Specifies IPO mandate parameters including the five-lakh-per-application limit, the mandate validity window, the 5 PM IST cutoff, and the roles of the sponsor bank, the self-certified syndicate bank (SCSB) and the registrar.
- NPCI Circular dated September 2025: Raised per-transaction limit for capital markets and insurance premium mandates from two lakh to five lakh rupees.
- RBI Payment Aggregator Guidelines (2020): Applicable where TPAPs or payment aggregators facilitate mandate creation for merchant subscription billing.
Related articles
- Unified Payments Interface (UPI)
- UPI 2.0 mandate explained
- NPCI
- BHIM app
- Payment Service Provider (PSP) bank
- Self Certified Syndicate Bank (SCSB)
- How to approve a UPI mandate for an IPO application
- ASBA
References
- NPCI, UPI 2.0 Product Specification, August 2018, https://www.npci.org.in/what-we-do/upi/product-overview .
- NPCI Circular, UPI Mandate, Operational Guidelines, September 2018.
- SEBI Circular SEBI/HO/CFD/DIL1/CIR/P/2019/62, Streamlining the Process of Public Issue of Equity Shares and Convertibles, Introduction of UPI as Payment Mechanism with ASBA for Retail Investors, May 2019.
- SEBI Circular SEBI/HO/CFD/DIL2/CIR/P/2022/45, Streamlining of Application Process in Public Issues, UPI Mechanism, April 2022.
- NPCI Circular, Enhancement of UPI Per-Transaction Limits for Capital Markets and Insurance Premium Categories, September 2025.
- Reserve Bank of India, Annual Report on Currency and Finance 2023-24, Payment Systems section.
- NPCI, UPI Ecosystem Statistics, Monthly, October 2025, https://www.npci.org.in/what-we-do/upi/upi-ecosystem-statistics .