Compare
Offline UPI vs *99#: banking code vs event payments
Search “offline UPI” and you’ll mostly find *99# / USSD explainers. Useful product. Different problem. This page keeps the two honest so you don’t buy a drink with a banking menu in the mosh pit.
Two different problems
Problem A — no data for banking: you’re somewhere without mobile internet and still need basic UPI-related banking access. *99# (USSD) is the channel most articles describe.
Problem B — no usable data in a 40k crowd: you’re at a concert or fest, the stall is right there, every app times out, and “try again” is not a checkout UX. That’s live-event congestion — the space Surge targets.
Calling both “offline UPI” is how the internet confuses everyone. Same umbrella word. Different jobs.
What *99# / USSD is good for
At a high level, *99# style offline access is about reaching UPI-related banking functions without a data session — typically via USSD, subject to bank participation, telecom support, and official limits. We won’t rehash every NPCI menu step here; banks and payment blogs already own that SERP.
Strengths: works without a smartphone data plan in many setups; national footprint in the “no internet for banking” narrative. Limits for a pit checkout: session-based menus, not a polished stall QR experience, and it doesn’t redesign how a vendor line moves when the whole ground is RF-dead.
Not legal or regulatory advice — check your bank and official NPCI/bank docs for current *99# availability and steps.
What an event offline rail is for
Surge is an offline-first UPI payment rail for live events. Attendee taps or pays at a stall when signal is gone; the payment is signed and queued; settlement happens when the network returns. Vendor keeps the line moving. Fan keeps the set.
It’s not “we rebranded *99#.” It’s not a prepaid wallet story. It’s event infrastructure: scan. pay. sync.
Side-by-side
| Dimension | *99# / USSD (typical) | Surge (event rail) |
|---|---|---|
| Primary job | Banking access without mobile data | Stall checkout when crowd kills apps |
| Needs smartphone data? | Designed for no-data banking channel | Designed so payment completes offline, settles later |
| Dense concert crowd | Not built as pit merch UX | Core design scenario |
| Stall / vendor line | Menu-driven, not event POS-native | Event + stall flow, status for paid/pending |
| Who runs it | Banking / NPCI ecosystem channels | Surge for venues, vendors, attendees |
| Wallet top-up? | N/A (banking channel) | No — UPI Autopay mandate model, not prepaid pot |
When to use which
- *99#: you need offline-style banking access and your bank supports the flow. Follow official steps.
- Surge: you’re buying from event stalls and the crowd has murdered normal UPI apps — when the venue is on the rail.
More on the concert problem: UPI not working at concerts. Attendee product path: pay with no signal.
FAQ
Is Surge the same as *99#? +
No. *99# is a USSD banking channel. Surge is an offline-first stall payment rail for live events.
When should I use *99#? +
When you need basic no-data banking access and your bank supports it. Not a substitute for event stall UX in a dead crowd.
When do I need Surge? +
When the fest or concert is on Surge and you want to pay stalls without waiting for the tower to recover.
Want the event rail, not the banking menu?
Join the Surge waitlist. Built for bad signal at live shows.
Join waitlist