Screenshot fraud: why a picture of a transfer proves nothing

"I sent it, here's the screenshot." For many people, an image of a banking app or wallet showing a completed transfer feels like a receipt. It looks official. It has the right logos, the right fonts, a time stamp and a reference number.

It also proves nothing. A screenshot is a picture of a screen, and pictures can be made to show anything. Understanding this protects you whether you are the one sending money or the one waiting for it.

How easy it is to fake

Editing a transfer screenshot does not require special skill. The amount, the recipient, the date and the status are all just text and colored shapes. Common methods include:

• editing a real screenshot of an older transfer with any image app;
• using one of the many template generators that produce realistic-looking bank and wallet screens;
• changing the text on a real web page in the browser before taking the screenshot, which produces a perfect, pixel-accurate fake;
• taking a screenshot of a transfer that was started but later canceled or never confirmed.

That last one is not even a forgery. The image is real. It just captures a moment that did not lead to a completed payment.

Where screenshot fraud shows up

Selling online. A buyer claims to have paid and sends an image, hoping the seller will release goods before checking their account.

Peer-to-peer trades. In person-to-person crypto trades, one party sends a fake proof of payment and asks the other to release funds.

Disputes with services. Someone claims a payment was made to a service and uses an edited screenshot to demand a card, a refund or a credit.

Scams aimed at buyers. A fake seller shows "proof" that a previous customer was paid a refund, or that a card was delivered, to build credibility.

What actually confirms a payment

The only reliable confirmation comes from the system that holds the money, checked directly by the party receiving it.

• For a bank transfer: the receiving account shows the funds as settled, checked by the recipient in their own banking app.
• For a card payment: the payment processor confirms the charge as successful and not reversed.
• For a crypto transfer: the transaction is visible on the blockchain, addressed correctly, over the expected network, for the full amount, with enough confirmations. Anyone can check this with a block explorer, a public website that looks transactions up by their ID.

In every case, the recipient looks at the source, not at a picture of the source sent by someone else.

Why we ask for a TXID, not only a screenshot

When you pay for a card by manual crypto transfer, we ask for the transaction ID (TXID). That is not because we doubt you. It is because the TXID lets a person on our side look up the actual transaction on the blockchain and confirm that the amount, the network and the receiving address match your order.

You can also upload a screenshot on the final step, and it can help our team find your payment faster, especially if something about the transfer is unusual. But the screenshot is a helper, not the proof. The order is matched against the chain itself. Our process page explains what happens during that review.

This protects honest buyers too. If confirmations were based on images, anyone could claim your payment as theirs by sending a doctored copy of it.

Payments that look complete but are not

Some transfers are genuinely visible in the sender's app yet still not completed:

• Pending bank transfers that may still fail or be recalled.
• Card payments that are authorized but not yet captured, or that can later be charged back.
• Crypto transactions that are broadcast but not yet confirmed, or that were sent with a fee too low to be picked up quickly.
• Transfers sent to the wrong network or address, which show as "complete" in the sender's wallet but never reach the intended recipient.

That last case is common and painful. A buyer can sincerely believe a payment was made because the wallet shows "sent," while the funds actually went somewhere the recipient cannot reach. A screenshot of the sending wallet looks the same in both cases. A check of the receiving side shows the difference.

If you are the one paying

• Keep your own records: the transaction ID, the address you sent to, the network, the amount and the time.
• Submit the details the recipient asks for, such as a TXID, rather than relying on images alone.
• If someone insists on a screenshot only, and refuses to check the actual transaction, be careful. A real business wants to verify payments properly.

If you are the one being paid

• Never release goods, cards or funds based only on an image.
• Check your own account, wallet or a block explorer directly.
• Be wary of pressure to act quickly "because the screenshot shows it went through." A real payment will still be there in ten minutes.
• Watch for screenshots that arrive with a story about paying too much: it is the same pairing that powers the overpayment refund trick.

A habit worth keeping

The simplest defense is a rule you apply every time, whoever is asking: a payment counts when the receiving side can see it, and not a moment before. It sounds rigid, and that is its strength. Fraudsters rely on politeness and haste, on the awkwardness of saying "I'll wait until it shows up." A rule takes the awkwardness away, because you are not doubting anyone personally; you are following the same process you follow with everyone.

The same rule protects you when you are the one paying. Keep the transaction ID, not just a picture, and you can always point the other side to the record that settles the question.

Questions people ask

Can metadata in an image prove it is real?

Not reliably. Image metadata can be edited or stripped, and many apps remove it automatically.

What if the screenshot shows a real transaction ID?

Then check that transaction ID yourself. If it exists, it will show where the money went. If it does not, or it points to a different address or amount, the screenshot was wrong.

Is a screen recording more trustworthy?

It is harder to fake than a single image, but it is still a recording of a screen. Checking the source is the only reliable method.