Customer Payment and Refund Scams

Common scenario

A solo freelancer receives a message from a new customer saying they accidentally overpaid for a service. The customer asks for the extra amount to be returned quickly through a different payment method because they say the original method is unavailable.

Warning signs

• A customer says they overpaid and asks for a refund through a different method.
• The request includes pressure, emotion, or a same-day deadline.
• The customer sends a screenshot or forwarded receipt as proof instead of waiting for normal confirmation.
• The refund destination does not match the original payment path.
• The customer asks the business to buy something, forward money, or pay a third party.
• The request moves the conversation away from normal business channels.
• The transaction involves a QR code, payment link, wallet, or unfamiliar platform.
• The customer becomes upset when staff ask to follow the normal refund process.

Questions to ask

• Can we match this refund to a real order, payment, booking, or service record?
• Has the payment fully appeared through our normal business system?
• Is the refund method the same as the original payment method?
• Is the customer asking us to move money to a third party?
• Is pressure being used to skip normal refund timing?
• Who is approved to review unusual refunds or overpayment claims?

Verification workflow

• Pause the refund until the order and payment are checked in the normal business system.
• Do not rely on screenshots, forwarded receipts, or customer-provided proof alone.
• Use the business's standard refund method whenever possible.
• Require owner or bookkeeper review for overpayment claims, third-party requests, or unusual destinations.
• Keep customer communication calm and refer to the standard refund process.
• Record the general reason for the pause and the review outcome.
• Continue only when the request fits the business's normal refund workflow.

Example internal policy

• Refunds must match a real order, payment, booking, or service record.
• Refunds are not sent to unrelated third parties or unusual destinations without approved review.
• Screenshots and forwarded receipts do not verify payment by themselves.
• Overpayment, accidental payment, and duplicate-payment claims require owner or bookkeeper review.
• Staff may tell customers that verification is part of normal business policy.

What not to do

• Do not refund money before confirming the original payment through normal records.
• Do not send refunds through a different method just because the customer asks.
• Do not rely on screenshots, forwarded receipts, or payment notifications alone.
• Do not pay a customer's vendor, shipper, assistant, relative, or outside party as part of a refund request.
• Do not share private business, customer, payment, login, or document information in response to pressure.
• Do not accuse the customer or argue if the request seems suspicious.
• Do not bypass review to avoid an uncomfortable conversation.

If something already happened

• Pause additional refunds or payments related to the same customer or order.
• Notify the owner, bookkeeper, or approved refund reviewer.
• Save the message, general order category, timing, and action taken in internal notes.
• Check whether other staff received similar payment or refund messages.
• Review the public refund process so staff can point customers to one clear rule.
• Update training to include overpayment, chargeback pressure, screenshots, and alternate-destination refund requests.