Failure Patterns, Disputes, Security and Official Sources
Fake payment screenshots, QR swaps and refund scams: protecting a shop's digital payments
Common payment frauds against Indian merchants at the counter and online, how soundboxes and settlement checks help, and where to report fraud.
The costliest payment problem for many small shops is not a fee but a payment that never arrived. Common patterns in India include a customer showing a fake "payment successful" screen, a fraudster pasting their own QR sticker over yours, callers asking for a "refund" to a different account, fake "collect" requests sent to the merchant's own UPI app, and messages pretending to be your payment provider asking for OTPs or app installs. The protection is simple but must be a habit: trust only confirmation from your own soundbox, provider app or bank, check your QR daily, never approve a collect request or share an OTP to "receive" money, and report fraud quickly on 1930 or the National Cyber Crime Reporting Portal. The patterns here are generic. This guide belongs to the failure patterns overview.
Common frauds and defences
| Fraud | How it works | Defence |
|---|---|---|
| Fake payment screen | Customer shows an edited screenshot or a fake app's success screen | Rely on soundbox announcement or provider app; check the credited amount |
| QR swap | A sticker with another person's QR is pasted over yours | Check the QR daily; use a fixed holder; check the name shown when you scan your own QR |
| Collect request scam | Fraudster sends a UPI "collect" request; merchant approves thinking it is incoming money | Receiving money never needs your UPI PIN; decline unknown requests |
| Refund to another account | Caller claims an overpayment and asks for refund to a different UPI ID | Refund only to the original payment method through your provider |
| Provider impersonation | Calls or messages claiming to be your bank or PA, asking for OTP, KYC update or remote-access app | Verify on official numbers; never install screen-sharing apps on request |
| Card skimming at the counter | Card taken out of sight and copied | Keep card in the customer's view; use contactless or the customer's own insertion |
| Split-sale or test transactions | Stolen cards used for small test payments, then large ones | Watch for many small declined attempts; alert your acquirer |
| Online friendly fraud | Customer receives goods then disputes the payment | Delivery proof; see chargebacks |
Why a soundbox helps (and its limits)
A soundbox announces only payments that reach your merchant account, so it defeats the fake screenshot. It does not stop a QR swap, because the customer's payment goes to the fraudster's account and your soundbox stays silent. Train staff: no announcement, no goods. See soundbox rental vs purchase.
A daily and monthly routine
Every day:
- Before opening, scan your own QR with a phone and check the name displayed is your business.
- Keep the soundbox switched on and charged, volume up.
- At closing, compare digital sales in the provider app with your billing.
Every month:
- Reconcile settlement reports with sales; investigate any shortfall.
- Review the list of devices and users with access to your provider app.
- Update app and phone software.
- Remind staff of the rules above.
Worked example: the cost of a two-day QR swap (illustrative)
A café takes ₹12,000 a day through its QR. A swapped sticker goes unnoticed for two days during which half of UPI payments go to the fraudster.
| Item | Amount |
|---|---|
| Lost receipts: 2 days × ₹6,000 | ₹12,000 |
| Recovery | Uncertain; depends on how fast you report and whether funds can be frozen |
| Prevention cost | 2 minutes a day to scan your own QR |
Reporting within the first hours gives the best chance of funds being held in the recipient account.
Online sellers
- Use hosted checkout and do not take card details by phone or chat.
- Enable alerts for unusual activity in your gateway dashboard.
- Be cautious with high-value first orders to new addresses; consider delivery with OTP.
- Watch for account takeover of your gateway login; use two-factor login.
- Keep evidence for disputes; see chargebacks.
- Protect customer data under DPDP and RBI rules; see tokenisation and data rules.
Where to report
| What | Where |
|---|---|
| Financial cyber fraud, urgently | Helpline 1930 and cybercrime.gov.in |
| Fraud involving your payment provider | Provider's fraud or grievance desk, then nodal officer |
| Suspicious calls or messages claiming to be a bank or government | Report through the Department of Telecommunications' Sanchar Saathi portal (Chakshu) |
| Unresolved complaint against a bank or RBI-regulated entity | RBI complaint management system, if eligible |
| Police complaint | Local police station or cyber cell |
FAQ
Can I get money back if a customer paid to a swapped QR?
The payment went to someone else's account. Report immediately to 1930 and your bank; recovery depends on the case.
Does the customer lose money in a QR swap?
The customer paid, so from their side the payment was made; disputes between you and the customer can follow. Prevention is easier than resolution.
Is it safe to accept payment on my personal UPI ID?
Small vendors often do, under NPCI's P2PM framework. Keep business and personal transactions clear for accounting, and protect your UPI PIN.
Should I accept card payments over the phone?
Taking card numbers by phone means handling card data, which raises security and compliance risk. Use payment links from your gateway instead.
Sources
- National Cyber Crime Reporting Portal — report financial fraud; helpline 1930
- Sanchar Saathi — report suspected fraud communications
- Reserve Bank of India — customer awareness and complaint system
- NPCI — UPI safety guidance
