WebNotes

UPI ASBA (Unified Payments Interface — Application Supported by Blocked Amount)

From WebNotes, a public knowledge base. Last updated . Reading time ~22 min.

UPI ASBA is the retail-investor payment mechanism for Initial Public Offering applications in India, in which the applicant authorises a one-time UPI mandate that blocks (rather than debits) the application amount in the applicant’s own bank account until allotment is finalised. UPI ASBA is a specific operational form of the broader ASBA framework introduced by SEBI in 2008, layered on top of the Unified Payments Interface (UPI) rails operated by the National Payments Corporation of India (NPCI). It was made compulsory for retail individual investors applying through a stockbroker by SEBI’s Phase II circular of 28 June 2019 and is, as of mid-2026, the only payment route available to retail bidders going through an intermediary such as Zerodha, Groww or Upstox.

The mechanism works because UPI is not just a peer-to-peer transfer rail; UPI 2.0 introduced a mandate construct under which a payer’s bank can pre-authorise a future debit of up to a specified amount, in favour of a specified beneficiary, on or before a specified expiry date. For IPO applications the beneficiary is the sponsor bank assigned to the issue by the book running lead manager, the amount is the maximum bid value, and the expiry is set to the listing date plus one working day. From the applicant’s perspective the mandate is a hold on the savings account, not a debit; interest continues to accrue on the held balance, which is the working-capital relief that distinguishes ASBA from the pre-2008 cheque-and-refund regime.

Place in the regulatory stack

UPI ASBA sits at the intersection of three regulatory regimes:

For retail applicants this means three distinct rule sets interact at the moment of bidding: the SEBI ICDR rule that the retail category is capped at ₹2,00,000, the NPCI rule that a single UPI capital-market mandate is capped at ₹5,00,000 (from 15 September 2025), and the bank-by-bank operational rules that decide whether a particular bank’s UPI handle is currently eligible to handle an IPO mandate.

How the flow works end-to-end

A retail IPO application via UPI ASBA passes through six stages between bid submission and either allotment or block release.

1. Bid submission at the broker

The applicant places a bid on the broker’s interface (the canonical surface for Zerodha is Bids → IPO on Kite), entering quantity, price (or cut-off election) and a UPI ID. The broker transmits the bid to the exchange’s Issue Module, which time-stamps it and forwards it to the registrar and the sponsor bank for the issue. From the applicant’s screen, the bid status reads Pending Mandate.

2. Mandate request from sponsor bank to issuer bank

The sponsor bank, identified by the lead manager in the issue prospectus, generates a UPI mandate request addressed to the issuer bank — the bank that hosts the applicant’s UPI handle. The request specifies the block amount, the validity period (typically issue close plus listing date plus one working day), and a unique transaction reference. The mandate request travels over the NPCI mandate-API rails.

3. Mandate notification to the applicant’s UPI app

The issuer bank pushes the mandate as a Collect request to whatever UPI app the applicant uses (PhonePe, Google Pay, Paytm, BHIM, Amazon Pay, WhatsApp Pay or the bank’s own UPI app — all of these support the IPO mandate notification under NPCI’s specification). The notification arrives as a push notification on the applicant’s phone, typically labelled Block Funds for IPO or Mandate Request. A separate emailed notification is also generated by most UPI apps.

4. Mandate authorisation by the applicant

The applicant opens the UPI app, reviews the issuer name, block amount and validity, and enters the four- or six-digit UPI PIN. On successful PIN entry, the bank places a lien on the savings account against the specified amount, reducing the available balance shown to the customer but leaving the book balance unchanged. Interest on the savings account continues to accrue against the full book balance, including the lien portion. The mandate cutoff is 5 PM IST on the bid closing day; mandates not approved by that cutoff are rejected at the exchange and the bid is treated as unconfirmed.

5. Bid confirmation propagation

The issuer bank returns an acknowledgement to the sponsor bank, which propagates back to the broker. The applicant’s bid status on the broker interface changes from Pending Mandate to Mandate Accepted. The blocked amount remains visible in the bank’s own mobile app or NetBanking portal, typically under a holds and earmarks section, even though the regular available-balance display shows the post-block figure.

6. Allotment or release

On allotment finalisation (T+1 under the post-December-2023 regime), the registrar instructs the sponsor bank to debit the issuer bank for the value of allotted shares. The lien is converted to an actual debit for that portion and the remainder is released; the bank statement, depending on the bank, shows either a single IPO debit line for allotted-share consideration with a separate lien released line, or a series of memo entries that net to the correct outcome. If no allotment is made, the entire lien is released without any debit, typically within one working day of the basis-of-allotment publication.

Roles in the UPI ASBA flow

UPI ASBA involves five distinct counterparties, and a clear understanding of who-does-what helps in diagnosing the relatively common failure modes.

The sponsor bank is the SEBI-registered SCSB designated by the issuer (through the BRLM) to handle the inbound UPI mandates for that specific issue. It serves as the gateway between the exchange and the NPCI mandate API. Common sponsor banks for mainboard issues include HDFC Bank, ICICI Bank, Axis Bank, Yes Bank, Kotak Mahindra Bank and State Bank of India. The sponsor bank is named in the issue prospectus and visible on the broker’s bid-submission page; the applicant does not need to have any banking relationship with the sponsor bank.

Issuer bank

The issuer bank is the applicant’s own bank, which hosts the savings account from which the UPI ID is mapped. The issuer bank is the entity that actually places the lien on the savings account. Issuer-bank eligibility is governed by NPCI’s UPI for IPO list, which is reviewed periodically. As of 2026 nearly all scheduled commercial banks and most small finance banks are eligible; payments banks and merchant categories are typically excluded.

NPCI

NPCI operates the UPI rails and the mandate-API. It does not hold funds itself but provides the messaging layer and settlement reconciliation between sponsor and issuer banks. NPCI’s policy decisions on per-transaction caps directly bound the maximum size of any retail IPO bid.

Registrar to the issue

The registrar is the SEBI Category I intermediary (KFin Technologies and Link Intime dominate the mainboard market; Bigshare, Cameo and Maashitla service smaller issues) that consolidates bid data from the exchanges, performs third-party PAN-demat-bank verification, eliminates duplicates, finalises the basis of allotment, and instructs the depositories to credit shares.

Stock exchange

The exchange (NSE and/or BSE) operates the bidding terminal that receives bids from brokers, validates them against the master parameters, time-stamps them, and forwards them to the registrar and sponsor bank. The exchange is also responsible for publishing the consolidated subscription numbers in near-real time during the bidding window.

Transaction limits

UPI ASBA limits have been raised three times since 2019 to track the growth of retail demand and to align with SEBI’s investor-category thresholds.

Date effectivePer-transaction capDaily cumulative capNotes
1 July 2019₹1,00,000₹1,00,000Initial cap when UPI was made mandatory for retail
13 March 2020₹2,00,000₹2,00,000First revision, aligned with SEBI retail upper bound
9 December 2021₹5,00,000₹5,00,000NPCI raise for capital-market use cases
15 September 2025₹5,00,000₹10,00,000Doubling of daily cumulative cap; per-transaction unchanged

The current ₹5,00,000 per-transaction cap exceeds the SEBI ICDR retail upper bound of ₹2,00,000. Bids between ₹2,00,000 and ₹5,00,000 are technically deliverable through UPI but, since they exceed the retail definition, are treated by the registrar as Non-Institutional Investor (NII) applications and allotted from the NII bucket rather than retail. Most brokers, including Zerodha, do not currently expose NII-via-UPI as an option, so the practical retail ceiling on UPI ASBA remains at ₹2,00,000 minus one rupee for issues priced at the upper band.

UPI mandate mechanics

One-time mandate model under UPI 2.0

UPI 2.0, launched by NPCI in August 2018, introduced the concept of a mandate alongside ordinary push-and-pull transfers. A UPI mandate is a future-dated authorisation under which the payer’s bank pre-authorises a debit up to a specified amount, on or before a specified expiry date, in favour of a specified beneficiary. For IPO purposes the mandate is one-time (not recurring), the beneficiary is the Sponsor Bank assigned to the issue, and the expiry date is set to the listing date plus one working day so that any debit or release can be settled. The same construct supports SIPs, insurance premiums and subscription billing, but with different mandate types (recurring instead of one-time).

Block-and-debit flow

On mandate authorisation, the issuer bank places a lien on the specified amount, reducing the available balance though not the book balance. Interest accrues on the full book balance. On allotment, the registrar instructs the sponsor bank to debit the issuer bank for the value of allotted shares; the lien on that portion is converted to an actual debit and the remainder of the lien is released. The mandate framework does NOT involve any transfer from the applicant’s account to the sponsor bank’s account until allotment is confirmed; the debit is internal to the issuer bank and the inter-bank settlement happens through normal NEFT or NPCI rails.

Block-amount versus bid value

A retail bidder can place up to three bids per application, varying both quantity and price within the band. The amount blocked through the UPI mandate is the maximum of the three bid values — specifically, the highest bid quantity multiplied by the upper end of the price band. This is true even if one of the bids is at the cut-off price and another is at the floor price. The reason is that the registrar will, if allotment is made, allot at the issue price (which can be anywhere in the band), so the block must cover the worst case.

Eligibility and prerequisites

To use UPI ASBA, a retail applicant must satisfy these prerequisites:

Non-Resident Indians cannot apply through UPI ASBA. UPI mandates are not yet supported for NRO or NRE accounts; NRIs apply through bank ASBA NetBanking.

Common failure modes

The principal failure modes of UPI ASBA are bank-side rather than broker-side. Understanding them helps an applicant diagnose problems quickly.

Mandate not received in the UPI app

The single most common UPI ASBA problem. Typical cause: queue backlog at the sponsor bank or the issuer bank when traffic spikes (the LIC IPO of May 2022 and the Tata Technologies IPO of November 2023 generated widely reported mandate delays). Standard remedy: open the UPI app and pull-to-refresh the Pending Requests or Mandate section, log out and back in, or switch to the bank’s own mobile-banking app where the same mandate is also discoverable. The bid is preserved at the broker as Mandate Pending until either the mandate arrives or the issue closes.

Mandate rejected with code U16 or ZD

A rejection with code U16 or ZD typically reflects a duplicate mandate — the bank has already received an identical mandate request and is refusing the second. Cause is usually a re-submission of the same bid (a common UI accident on broker apps). Remedy: wait fifteen minutes for the duplicate to be cleared from the sponsor-bank queue, withdraw the current bid on the broker interface, and re-submit.

Mandate rejected with code U30

A U30 rejection reflects an issuer-bank-side technical error — usually a transient outage or a backend mismatch. Often coincides with sponsor-bank gateway throttling during peak IPO subscription windows. Remedy: the applicant can wait fifteen minutes and re-submit with the same UPI ID; in stubborn cases a different UPI ID mapped to the same bank account (for example, switching from PhonePe to BHIM if both are on the same SBI account) often unblocks the flow. The applicant should not switch to a UPI ID mapped to a different bank, since the third-party verification matches the UPI-bank PAN against the demat PAN.

Mandate accepted but block not visible in the bank statement

This is usually a propagation lag rather than a real failure; the lien shows up in the bank statement within a few hours of acceptance. The available balance in the bank’s mobile app drops immediately, even when the holds and earmarks line item has not yet posted.

Ineligible bank or UPI handle

A particular caveat applies to applicants using small finance bank or payments bank UPI IDs. The eligibility for these banks to handle IPO mandates is reviewed periodically by NPCI, and an applicant whose UPI ID is hosted on a non-eligible bank will see immediate mandate rejection. The current UPI for IPO eligibility list should be checked on npci.org.in before relying on a non-scheduled-bank UPI handle for a time-sensitive bid.

Late mandate approval

Mandates approved after 5 PM IST on the bid closing day are not forwarded to the registrar, irrespective of when the bid was placed. This produces a class of frustrating failures where the bid status shows Mandate Accepted but the registrar still rejects the application because the cutoff was crossed.

Comparison with bank ASBA

The applicant has a choice between UPI ASBA via a broker and bank ASBA via NetBanking. The two routes differ on multiple dimensions.

DimensionUPI ASBABank ASBA (NetBanking)
Eligible categoriesRetail individual investors only (and retail-bracket HUFs via karta)All categories: retail, NII, QIB are not, but small NII, large NII, employee, shareholder
Per-application cap₹5,00,000 (NPCI limit)None at the bank level, up to issue rules
Time to apply2–5 minutes via broker app10–15 minutes via NetBanking screens
Mandate channelPush notification to UPI appNetBanking session, no separate device hop
Cutoff for mandate approval5 PM IST on closing day5 PM IST on closing day
Failure modesBank-side mandate queue + UPI app reachabilityNetBanking session timeout + browser issues
Allotted-share creditT+2 (under T+3 regime)T+2 (under T+3 regime) — identical
Withdrawal flexibilityThrough broker interface, generates a fresh mandateThrough NetBanking, immediate lien release

For retail bids under ₹2,00,000, UPI ASBA is faster and more convenient. For NII bids above ₹2,00,000, bank ASBA is the only practical route.

References

  1. NPCI press release on UPI 2.0 launch, August 2018, Mandates, Invoice and Signed Intent under UPI 2.0.
  2. SEBI Circular SEBI/HO/CFD/DIL2/CIR/P/2018/138 dated 1 November 2018, Streamlining the Process of Public Issue of Equity Shares and Convertibles — Phase I framework.
  3. SEBI Circular SEBI/HO/CFD/DIL2/CIR/P/2019/76 dated 28 June 2019, Phase II Implementation — UPI made mandatory for retail.
  4. NPCI Circular dated 9 December 2021, Enhancement of UPI Per-Transaction Limit to ₹5,00,000 for Capital Market Use Cases.
  5. NPCI Circular dated 8 September 2025, Doubling of UPI Daily Cumulative Cap to ₹10,00,000 for Capital Markets and Insurance Premium Categories, effective 15 September 2025.
  6. FAQs on UPI in Public Issue Process, SEBI, July 2019.
  7. List of UPI ASBA Sponsor Banks and Issuer Banks, NPCI portal, updated periodically.
  8. Streamlining the process of IPOs with UPI in ASBA and redressal of investor grievances, SEBI Circular SEBI/HO/CFD/DIL2/CIR/P/2021/2480/1/M dated 16 March 2021.

See also

Reviewed and published by

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.