On the direct-UPI rail you are the confirmation step. This is the screen where you do it.
Finding the orders waiting on you
Orders shows a banner — "N orders are awaiting payment verification" — whatever filters you have on. The stats panel above the table has a matching tile. Either one takes you to the filtered list.
The panel
Open an order and the verification panel shows you everything needed to match it against your bank app:
Open your bank or UPI app, find the credit, and check the reference and the amount agree.
Approving
Press Verify payment and confirm. That single action does everything the gateway does automatically: the order becomes Paid, tickets are minted, the held seats become sold, and the ticket email goes out. The confirmation names the addresses it actually reached, and right beside it is Forward myself — the same manual WhatsApp link from Sending and resending tickets about sending and resending tickets, already pointed at the tickets this action just minted.
A verified UPI order is a normal paid order from that point on. Nothing downstream — exports, the attendee list, the door scanner — treats it differently.
Rejecting
Press Reject, with a note. Use it when the reference does not appear in your account, the amount is wrong, or it is a duplicate of a payment already applied.
Rejecting leaves the door open on purpose
The order stays Pending rather than being cancelled, and the mistyped reference is cleared off it. That is so the buyer can submit a corrected reference against the same order — and so that whoever genuinely made that payment can still claim it later. The reference you rejected is kept in the internal note either way.
The note is internal. Write what you actually checked — "not in HDFC statement 14/08", "amount short by ₹200" — because the person reading it in three weeks is you.
After a reject, a Tell them it didn't match button appears. It opens your own WhatsApp with a message naming the order and asking the buyer to check and resubmit the reference — nothing is sent by us, and no ticket link is in it, because none exists yet.
Working the queue, not just one order at a time
A claim that has not been decided yet also gets a message of its own — Tell them we got it — on the row in the orders list, so you can acknowledge a fresh claim before you have had time to open it. Detail: Reading the orders list about reading the orders list.
Two things to be careful about
Verify once, and do not race yourself
If you and a colleague are both working the queue, do not open the same order in two places. Approving and rejecting the same order at the same moment is the one situation this screen cannot untangle for you.
Never issue a ticket from the reference alone
The whole rail rests on somebody checking a bank statement. A reference that looks plausible is not a payment, and there is deliberately no button anywhere that turns one into a ticket without your approval.
Once verified, delivery works like any other order — Sending and resending tickets about sending and resending tickets.