Fake payment screenshots: the scam hitting travel counters

A client messages you a screenshot: GPay, ₹15,000, "payment successful", green tick and all. You block the seats, confirm the booking, and move to the next enquiry. Then the money never shows up in your account.

That is the fake payment screenshot scam, and it is hitting travel counters because agents confirm bookings off a photo on someone's phone instead of off their own bank statement. The habit is understandable. WhatsApp is how your business runs, and a screenshot feels like proof. It isn't.

Screenshots can be edited in any photo app, generated by apps built to spoof GPay and PhonePe, or attached to a real payment for the wrong amount. This post covers how the scam actually works, the hard rule that stops it, and how to verify a UPI payment received before you touch the "confirmed" button.

How the fake payment screenshot scam actually works

The scam relies on one gap: you confirming a booking based on what a customer's phone shows you, not what your own bank or UPI app shows. Reporting on this fraud describes three common variants that agents should know by name.

• Photo-edited screenshots. A genuine payment receipt, theirs or someone else's, edited in any photo app to change the amount, the recipient name, or the date, then sent as if it were your payment.
• Spoof apps. Apps built specifically to mimic the GPay or PhonePe confirmation screen. No transaction happens anywhere. The "successful payment" screen is generated locally on the scammer's phone, screenshotted, and sent to you.
• Inflated payment, then a cash-back ask. A real UPI payment, but for more than the invoice, say ₹20,500 against a ₹20,000 balance. The customer immediately asks you to refund the ₹500 difference, before you've had time to check the transaction properly. Days later, the original payment is disputed or reversed through the bank, and you are out both the refund and the fare.

None of this is hypothetical for small businesses handling walk-in and phone payments. Reports circulating in the retail trade describe shopkeepers cheated through fake payment apps and fake QR-scan screenshots. A travel counter is an easier target than a shop counter: a "seat blocked, non-refundable in an hour" workflow means a fake screenshot can lock your inventory and cost you the real booking before anyone checks a bank statement.

Careful: the inflated-payment variant is the one that fools experienced staff, because real money does land in your account first. The trap is refunding the "excess" before the original credit has actually settled. Treat any refund request that arrives within minutes of a payment as a reason to wait, not a reason to hurry.

The rule that stops it: confirm against your account, never their screen

One rule ends this scam. A booking gets marked confirmed only when the amount shows up as credited in your own bank account, your own UPI app, or your payment gateway dashboard, never off a screenshot, a video, or a verbal "payment ho gaya".

Build the counter workflow around these lines, and print them at the desk if you have to:

• Never confirm a booking, release a hold seat, or hand over a voucher on the strength of a screenshot alone.
• Open your own banking or UPI app and check the credit yourself. Don't take a staff member's or a customer's word for what the balance shows.
• Match the UTR (the transaction reference number visible in the screenshot) against your own bank statement entry, not just the amount and the payee name in the image.
• Treat "money is stuck, here's the screenshot as proof" as a stalling line, not a status update. A real UPI payment settles in seconds; a stuck one settles within the day, or it fails and the amount bounces back to the sender.
• If a payment comes in for more than the invoice and the customer asks for the difference back immediately, hold the refund until the credit has been sitting in your account for at least a day.
• Log every payment against a booking reference inside whatever system tracks your pipeline, so "confirmed" and "paid" can never be the same click made on the strength of an image.

Example: say a client sends ₹18,000 for a ₹18,000 Goa package via a WhatsApp screenshot on Friday evening. Your desk is busy, so someone confirms the hotel booking off the image. On Monday, the bank statement shows no such credit ever landed. The hotel booking is non-cancellable by then. That gap, screenshot on Friday, verification on Monday, is exactly the window the scam is built to exploit.

Verify UPI payment received before you confirm anything

Verifying a UPI payment takes under a minute and should happen before any booking status changes, not after. Open your own UPI app or net banking, search the exact amount and date, and confirm the credit and the sender's UPI handle match what you were told. If the amount is significant, cross-check the UTR number against your bank's transaction history rather than trusting the number printed on the screenshot itself, since that number can be edited too.

If your business takes payments across multiple UPI handles, cards and bank accounts, this check gets slower and more error-prone the busier your season gets. That is the exact moment a fake screenshot slips through.

The workflow that removes this risk almost entirely is to stop treating payment confirmation as a manual, human judgment call at all. Route client payments through a payment gateway or a UPI collect link that fires an automatic signal the instant money actually lands, and let a booking's status flip to "paid" only when that signal arrives, never when a staffer eyeballs an image and clicks a button. If you're still deciding how to set this up, the honest playbook on why banks treat travel as high-risk covers what a gateway costs and what it takes to get one approved for a travel business.

Whatever collection method you use, tie it back to the advance receipt you issue for every booking, so there's a paper trail that only gets generated after a real, verified credit, not after a screenshot arrives in your inbox.

Customer sent fake payment proof: what to do now

If you've already confirmed a booking or released inventory against a screenshot that turns out to be fake, act within the hour, not the day. Report the transaction to the national cyber crime helpline 1930 or cybercrime.gov.in immediately, as of July 2026 this remains the fastest route to attempting a freeze on the mule account before the money moves further. Note down the UPI handle, the phone number used, and every screenshot the "customer" sent you, since these become the evidence trail.

Separately, contact whichever vendor, hotel or transport partner you confirmed on the strength of that payment, and try to cancel or hold before the booking becomes non-refundable on their end too. A fast internal escalation here often saves the vendor-side loss even when the payment itself is unrecoverable.

Common questions

Can a payment screenshot really be faked?

Yes. A screenshot is just an image, and images are trivially editable in any photo app, plus there are apps built specifically to generate fake "payment successful" screens that mimic GPay and PhonePe without any real transaction occurring. Treat every screenshot as a claim to be checked, never as proof on its own.

What if the customer paid more than the invoice and wants cash back?

Hold the refund until the original payment has actually settled in your account for a day, not minutes. This variant relies on you refunding the "excess" before the underlying payment can be reversed or disputed, leaving you out both amounts.

Should a small agency bother with a payment gateway just for this?

If you're taking advances by screenshot because a gateway feels like overhead for a two- or three-person desk, weigh that against a single lost booking. A gateway or UPI collect link with automatic payment confirmation removes the judgment call from your staff entirely, which is worth more than the setup effort once you're handling more than a handful of advances a week.

The short version

• The fake payment screenshot scam works because agents confirm bookings off a photo, not off their own bank statement.
• Three variants to watch: photo-edited receipts, apps that spoof the GPay/PhonePe confirmation screen, and a real but inflated payment followed by a rushed cash-back demand.
• Confirm a booking only when the credit shows in your own account or app, never off a screenshot, video, or verbal claim.
• Match the UTR number in your own bank statement, not the number printed on the screenshot.
• Hold any "refund the excess" request for at least a day so a disputed payment can't reverse before you notice.
• Route payments through a gateway or collect link so booking status changes on a payment webhook, not a staffer's click.
• If you're already stuck with a fake screenshot, report to 1930 or cybercrime.gov.in within the hour and chase the vendor-side hold in parallel.