How the Overpayment Scam Actually Works

An overpayment is not a mistake that happened to land on you. It is the product. The excess exists so that there is a reason to ask you to move money out of your own account.

Everything else in the exchange — the apology, the courier who needs paying, the assistant who typed the wrong figure — is scaffolding around that one request.

The sequence, from overpayment to urgent refund

It runs in five moves, and it is the same five underneath every version.

1. You agree a price, list an item, or accept a small job. 2. A payment arrives for more than was agreed, with a reason attached: a typo, a company account that pays in fixed blocks, an assistant who processed it wrong. 3. The excess is described as belonging to a third party — a courier, a supplier, a colleague — so that passing it on feels like admin rather than a transfer of your own money. 4. You send the difference from your own funds, by a method that cannot be recalled. 5. The original payment is unwound by the bank or provider that handled it, because the instrument behind it was never good.

Every detail of the story exists to make step four happen before step five.

Money in your balance is not money that has cleared

The figure in your app is provisional. Providers show incoming funds before the underlying instrument has finally settled, because showing them promptly is useful to everyone whose payments are fine.

That courtesy is the gap the whole thing lives in. When the instrument turns out to be worthless, the credit is reversed and the number in your app drops back — and by then the money you sent out has gone, because you sent it by a method chosen for exactly that quality.

Do not try to work out how long the gap is. It differs by bank, by country, by instrument and by account. Ask your own bank the specific question instead: has this particular payment finally settled, and can it still be reversed? That is something they can answer about your account today. No general rule you read anywhere substitutes for it.

Urgency is doing structural work, not decoration

The refund is needed now. Before the weekend, before the courier leaves, before the supplier cancels the order. There is a reason to feel bad about any delay attached to it: somebody is out of pocket, a driver is waiting, a shipment is being held.

The pressure is load-bearing. The window between a payment appearing and a payment settling is finite, and the whole scheme has to fit inside it.

Which gives you a free test. Say you will send it once your bank confirms the funds have finally cleared, and see what the reaction is. A genuine payer waits, because they know their money is good. The reaction to that sentence tells you more than any other part of the conversation. Manufactured deadlines show up far beyond this one pattern, and the fake urgency tactic is worth recognizing on its own terms.

The variations: payroll, invoices and accidental double transfers

The cover stories rotate. The mechanism does not.

If money you did not expect has arrived, and the same person is asking you to move money out, you have this pattern regardless of the wrapping. One variation replaces the refund with goods: rather than sending money on, you accept a delivery and forward it, which is what a package-forwarding request actually asks of you and carries risks that money never does.

Why you owe the whole amount having kept nothing

There are two separate transactions here, and only one of them gets reversed.

The credit that arrived is unwound because whatever funded it failed. The payment you sent out was funded by you, from cleared money, by an irreversible method. Nothing nets off. Your bank does not see one transaction with a surplus in it; it sees a reversed deposit and an ordinary outgoing payment that you authorized.

So the damage lands twice. The money you sent is gone, and the deposit that appeared to fund it never existed. If the reversal takes your balance below zero, arrears and charges sit on top.

If you already sent the refund back

One call before anything else: your bank, on the number printed on your card, not a number from any message.

Say it plainly and in this order. "I received a payment I now believe was fraudulent, and I sent a payment out on the strength of it. Can you attempt to recall the outgoing payment, and can you flag the incoming one?" Give the dates and the reference. Ask for a case number and write it down somewhere you will find it again. Speed is the only lever you hold — a recall attempt is worth more the earlier it is made.

After that call, three things. Send nothing further, however the story develops and whoever it comes from. Keep every message, including the ones that arrive afterwards. And if the outgoing payment cannot be recovered, the routes that remain for getting money back are worth working through in order rather than at random.

Reporting is a separate job from recovery, and where to report a scam like this is its own decision once the bank call is behind you.

Who this hits hardest: sellers and freelancers with no payment history

Somebody who has taken hundreds of payments has a baseline. They know what a normal buyer sounds like and how a normal transfer behaves. A first-time seller has none of that, so an abnormal payment has nothing to look abnormal against.

A first client also carries a strong wish for the thing to be real, and that wish quietly does the work of not asking. Being new is the vulnerability, and the only fix is to borrow the rule instead of the experience.

Other ways a buyer manufactures the look of payment — screenshots, pending-transfer stories, reversed charges — sit in the payment tricks freelancers meet on first jobs.

If more money than you agreed has arrived, the safe move costs you nothing. Leave it exactly where it is and tell the sender to have their own bank reverse it. A genuine payer can do that in an afternoon. Nobody else will ask you twice.