How overpayment scams work

A situation worth working through

A supposed client sends more than the agreed amount and asks a creator to forward the difference to another person. The story may involve a mistaken payment, a courier, or an assistant. The important issue is the request to move money based on a payment whose status and legitimacy have not been independently established.

Recognize the pattern

The FTC describes fake-check scams in which someone sends more than they owe and asks the recipient to return money. Funds appearing available does not establish that the check is genuine. A convincing explanation for the overpayment does not remove the risk.

Keep refunds in the proper process

Do not respond to pressure by making a separate payment to a new destination. Contact the bank or payment provider through its official channel and explain what happened. Let the provider advise you about the actual transaction.

For commissions, agree on the scope and payment process before starting. Keep the correspondence and invoice together so an unexpected change is easier to identify.

Do not turn a gift into an off-platform arrangement

If someone claims they made a mistake after supporting you on a platform, use that platform’s published support or refund process. A request to repay a different account is a reason to stop and verify, not a customer-service shortcut.

Stop the proposed onward transfer

A screenshot, email receipt, or visible balance is not a substitute for the provider’s actual transaction record. With fake checks, funds can appear available before a bank discovers the check is fraudulent. The FTC describes this as a central feature of check scams. Avoid forwarding money, purchasing gift cards, or paying a third party at the sender’s instruction.

Use the original provider’s help route

Open the payment service or contact the bank through a known official channel. Explain the unexpected payment and ask how to handle it safely within that system. Do not improvise a refund by sending a new payment to a different account. Different payment methods have different processes, so use the provider’s guidance for the actual transaction involved.

Preserve the agreement and messages

Save the agreed price, sender details, transaction reference, and request for the extra transfer. Keep sensitive account information private. If you already sent money, contact the payment provider promptly and report the incident through the appropriate official channel. Avoid promising yourself or others that a particular recovery outcome is guaranteed.

Words you can adapt

The example below illustrates the approach; it is not a customer message or testimonial. Change the details to match the actual situation. Keep the meaning accurate rather than copying a promise that does not fit your work.

A sympathetic explanation can distract from the transaction structure. The sender may sound embarrassed, rushed, or worried about someone else. You can remain polite without agreeing to move the money. The safest next step is verification through the actual provider, not deciding whether the story feels emotionally convincing.

Try the approach on a real example

Use a past message with its personal details removed, or a fictional practice message. Do not contact a suspicious sender, open an attachment, send a payment, or submit a live report merely to complete an exercise. The purpose of this review is to decide what information you would need before acting and where you would obtain it independently.

On a blank page, write the exact action the message is requesting. Keep this separate from its story about why the action is urgent. A request to share a code, send a payment, or follow a new link should be visible as an action, not hidden inside a sympathetic explanation. If you cannot describe the request clearly, pause rather than guessing.

Next, divide your notes into what you observed and what someone claimed. Record the account address, relevant date, and wording you can actually see. Put assumptions about identity, authority, and intent in the second column. A familiar name or a convincing explanation may be worth checking, but neither should move into the verified column without additional evidence.

Write down the independent route you would use next. It should begin with a service, website, or contact you already trust, not a new destination supplied by the questionable message. Describe the question you would ask through that route. Keep it specific enough that the recipient can answer without needing the whole history of your creator business.

Finally, identify what information should remain private. Remove authentication details, unrelated messages, and unnecessary personal data from any proposed report or public warning. Preserve the original evidence securely if it may be needed. A useful report gives the right recipient enough context while avoiding a second problem caused by exposing information to everyone else.

What to check afterward

For future paid work, keep the agreed amount and payment method in a clear written record. Review any mismatch before delivering additional work or sending funds elsewhere. A routine check is easier to follow than a new decision made under pressure each time an unusual request arrives.

Write down the outcome in plain language, including anything that remains uncertain. A useful review can end with a smaller change, a decision to wait, or a question that needs a better source. It does not have to end with a new post, a new tool, or a payment. Keep the lesson specific enough that you can use it the next time a similar situation occurs.