Home/Documents/P2P Payment Screenshot

Is this P2P payment screenshot real? Check for edits and AI fakes

A P2P payment screenshot is a picture of an app saying money was sent, and that is all it is. Sellers, landlords and marketplace users are routinely sent edited or fabricated screens from payment apps as cover for goods released before any money moves. The payment either shows up in your own account or it did not happen. TamperCheck examines whether the screenshot itself was edited, so you know when the image is the problem.

Last updated:

Most edited
  • amount sent
  • recipient
  • payment status
  • date and time
Reviewed by
Marketplace sellers, landlords and small businesses paid through P2P apps

How P2P payment screenshot forgeries are made

  1. Fake payment generators

    Websites and apps produce a sent screen for any amount and recipient. The result looks like the real app but no payment exists behind it, and the confirmation number is invented.

  2. Edited amounts and recipients

    A real screenshot of a smaller payment, or of a payment to someone else, has its amount or recipient retyped in an image editor. The replacement text seldom matches the app's own font rendering exactly.

  3. Pending payments passed off as complete

    A payment that is pending, scheduled or later cancelled is screenshotted before it can fail, or its status is edited to read completed. The money never arrives, or is reversed after the goods are gone.

  4. Fake payment notification emails

    Instead of a screenshot, the buyer sends an email that claims to come from the payment service and asks the seller to ship before the funds are released. Payment services do not hold funds pending shipment in this way.

Frequently asked questions

How do I know if a payment screenshot is fake?

Check the payment in your own app or bank account rather than on the screenshot. If it is not there, you have not been paid, however genuine the image looks. A forensic check can show whether the screenshot was edited, which is useful evidence when you report a scam.

Is a screenshot proof of payment?

No. A screenshot shows that a screen existed. It cannot show that money left one account and reached another. Treat it as a claim to be confirmed, and release goods only once the payment appears in your own account.

Can someone fake a sent payment screen?

Yes. Fake payment generators and ordinary image editors produce sent screens for any amount and recipient. Neither needs a real account or a real payment, which is why scammers use them to rush a seller into handing over goods.

What should I do if a buyer sends a screenshot instead of paying?

Wait until the payment shows in your account before releasing anything. Ignore emails or messages saying the money is held until you ship or pay a fee. If the screenshot turns out to be edited, keep it and report the buyer to the marketplace and to the payment service.

Where does a forensic review of a P2P payment screenshot start?

On a P2P payment screenshot, the review prioritises the amount and recipient, the phone clock against the payment time, and text rendered differently from the rest of the screen. The rest of a P2P payment screenshot is covered by the general pixel, font and metadata layers.

How do I catch altered payment details on a P2P payment screenshot?

Confirm any change out of band using contact details you already hold, and compare amount sent against earlier documents from the same sender. A forensic check on the file shows whether the region around recipient was edited.

What should accounts payable do when a P2P payment screenshot looks right but feels wrong?

Pause payment and confirm through a known contact. Then check the file: metadata, fonts and compression around amount sent usually say whether a P2P payment screenshot was produced by one system or assembled from parts.

Is a forensic check the same as confirming a P2P payment screenshot with the issuer?

No. It tests whether the file of a P2P payment screenshot is genuine, not whether the issuer holds a matching record. Many teams that rely on a P2P payment screenshot do both: a forensic check at intake, and issuer confirmation for the cases that are flagged.

What a genuine P2P payment screenshot contains

A sent or completed screen from a person-to-person payment app shows the amount and currency, the recipient's name with their tag, email address or phone number, a status such as sent or completed, the date and time, and often a memo. Many apps add their own confirmation number or transaction ID. A phone screenshot normally keeps the status bar too, with the device clock, signal and battery.

On a genuine screen those details belong together. The recipient's name matches the identifier under it, the status matches the wording around it, and the device clock in the status bar reads no earlier than the payment time when the screenshot was taken the same day. Edits tend to touch one field and leave its partner behind.

Red flags in a P2P payment screenshot

  • An amount sent that does not sit with the figures around it

    The amount sent is the figure a forger most wants to change. Read it against the other amounts on the page and against any second document that should agree with it. A careless edit updates this line and leaves the rest of the file describing the original.

  • A recipient that reads right but renders oddly

    Zoom in on the recipient and look at the background behind the characters. Edits often leave a faint halo, a patch of slightly different texture or spacing that was fine at full-page view.

  • A date or period that quietly moved

    Check issue, due and service dates against the period they claim to cover and against the file's own creation date.

  • Bank details that differ from earlier documents

    Compare the payee account against the last genuine document from the same sender. A changed account number is the single most expensive edit on this class.

  • A logo and layout that look perfect

    A flawless layout proves nothing, because the template is the easy part. Look at the fields that carry money and identity instead.

How to verify a P2P payment screenshot in 4 steps

  1. 1. Check the fields against each other

    Read amount sent, recipient, and payment status together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.

  2. 2. Inspect the file metadata

    Open the document properties and look at the producer, creation date, and modification date. A document produced by a consumer PDF editor, or created long after the date printed on its face, is worth a closer look.

  3. 3. Ask for a second document

    Request a corroborating document from the same issuer or an adjacent period. Forgery effort concentrates on one file, so inconsistencies surface as soon as there are two to compare.

  4. 4. Run a forensic check

    Manual review catches obvious edits but not field-level pixel manipulation or synthetic generation. TamperCheck runs 300+ forensic checks on a P2P payment screenshot and returns a risk score from 0 to 100 within seconds, on published per-document pricing.

What TamperCheck checks on a P2P payment screenshot

  • Arithmetic reconciliation

    Stated totals are recomputed from their components, and running or cumulative figures are checked for continuity across periods. A single edited value breaks the chain even when the page still looks right.

  • Date and validity consistency

    Issue, expiry, and period dates are checked against one another and against the file's own creation metadata, which catches backdating and validity extension.

  • Field-level forensics

    Every text region is analysed in its own right rather than as part of one whole-page image. This catches the smoothed and feathered edits that whole-image Error Level Analysis misses entirely.

  • And many more checks

    The three above are the layers that carry the most weight on a P2P payment screenshot. Every upload runs the full suite of 300+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.

Check a document

Upload a PDF or a photo of P2P payment screenshot. TamperCheck returns a risk score from 0 to 100 and marks the region that was edited, usually within seconds.

For developers, the API class is p2p_payment_screenshot. See the API and MCP documentation.

Often checked alongside

All supported document types