Checklist

How to pay at a festival when the network dies

Indian fests go cashless. Crowds go nuclear on the towers. Your plan needs a before / during / after — not vibes and a dead GPay spinner. Use this checklist; when a venue runs Surge, the hard part gets easier.

1. Before you go

2. At the gate and in the crowd

Expect signal to get worse as density rises. Screenshot tickets and entry codes while you still have bars. Don’t wait until the pit to “just check the app.” Assume the network will ghost you during peak sets.

Why that happens (short version): UPI not working at concerts.

3. At the stall

Product deep dive: pay at concerts with no signal.

4. After reconnect

Settlement and bank debits may lag when the world comes back online. That’s normal for offline-queued systems — and sometimes for normal UPI that finally flushes a stuck request.

5. If the fest runs Surge

Setup once (UPI Autopay mandate). At the fest: pick event, browse stalls, pay offline, get status that doesn’t gaslight you. When signal returns: sync — settle to the vendor. No wallet top-up game.

Surge is pre-launch. No fake “live at 200 fests” claims. Waitlist = signal when your city’s events get the rail. Not the same as *99# banking — see offline UPI vs *99#.

FAQ

Should I bring cash to a cashless fest? +

If rules allow it, a small backup still saves nights when digital paths melt. Always check the event policy.

UPI still pending after I walked away? +

Don’t double-pay on panic. Check status, talk to the vendor, wait for reconnect. Duplicate payments are a classic fest tax.

How does Surge change this checklist? +

Mandate setup before doors; offline stall pay when the venue is on Surge; settle on sync. Pre-launch — waitlist for when it’s your fest.

Make the checklist shorter

Join the Surge waitlist — offline payments built for festivals that murder your signal.

Join waitlist