Payment-Direction Deception on a Classifieds Marketplace

1. Summary

A seller published a classifieds listing and was contacted by an unknown party within minutes. The contact sent two images — a QR-style graphic labelled as a ₹1.00 credit, and a photograph of a merchant POS terminal — then asked the seller to complete a step to "release" the money. Neither image evidenced an incoming payment. The seller checked the account balance rather than the screenshot, recognised the payment-direction reversal, and declined to act. No funds left the account.

The pattern matters because it needs no stolen credentials, no malware and no data breach. It needs one misread step: a victim who confuses receiving money with sending money.

2. Context

3. What the parties saw

  1. Listing goes live; an unknown number opens contact on a messaging app.
  2. First image: a QR-style graphic carrying a "Received Money ₹1.00" label.
  3. Second image: a photograph of a merchant POS terminal showing a payment-processing interface.
  4. Message: the "buyer" says the payment is on hold and asks the seller to scan a code or open a link to receive it.

What was visible at the time was a plausible-looking pair of screenshots. What was established later is that neither artefact can evidence a credit: a QR graphic carries no transaction record, and a photograph of a terminal shows a device, not a settlement.

4. Method

  1. Preserve first. Capture the conversation with timestamps before replying to anything.
  2. Reconstruct the timeline. Log message timestamps at second-level granularity to test whether first contact was human or automated.
  3. Examine the artefacts. Image dimensions, compression and layout — whether the graphics match genuine app screenshots or are composites.
  4. Test the claim against the mechanism. Ask what record a genuine credit would produce — a bank or UPI reference, an app notification, a balance change — and check whether any of it exists. None did.
  5. Read the ask. Every payment-direction deception ends with an action that sends money or grants access. The ask is the tell, and it is the fastest thing to check.

5. Evidence

ArtefactWhat it showsIntegrity
Listing page capturepublication time, item, contact routeheld, hashed
Chat transcript exportcontact arrived four minutes after publicationheld, hashed
Image 1 — QR-style "received ₹1.00"no transaction reference of any kindheld, hashed
Image 2 — POS terminal photographa device screen, not a settlement recordheld, hashed
Sender numberoff-platform, unverified identityreported to platform

Originals are not published and identifiers are withheld.

6. Findings

7. Indicators and red flags

8. What stopped it / what would have stopped it

9. Limitations

10. References


Disclaimer. This write-up describes a single documented instance and is published for professional education. All personal and institutional identifiers have been removed or replaced with synthetic values. Findings are limited to the evidence described above; nothing here should be read as an allegation against any named or unnamed party.