Recognising Scams and Resisting Payment Pressure

Practise slowing down suspicious requests, verifying independently and responding without blaming the victim.

Part 7 of 10 | Mobile Money and Digital Payments Safety

Learning goals

You will recognise common ways a payment request can manipulate trust, separate warning signs from proof, and practise a calm stop-and-check response. You will prepare an incident note and understand why fraud can occur even when the account holder personally approved the transfer.

Before you begin

Allow 45 to 60 minutes. Use fictional messages written on paper. Do not contact suspicious accounts, open scam links or send a small payment to test a story. No one needs to disclose a past loss. A learner may complete the exercise alone if the topic feels uncomfortable.

Look at the requested action

A scam often asks you to do something that benefits someone else before you can verify the story. The most useful question is not whether the message looks professional, but what it wants you to authorise. A convincing profile can still ask for a harmful transfer. Focus on the destination, purpose, urgency and opportunity to check independently.

Consider an invented message: Your delivery is held; pay a release charge to this new number now. The course does not assert that every delivery charge is false. Instead, compare the claim with an order you actually placed and contact the delivery business through the route you already know. If you cannot establish the charge, do not pay merely to remove the pressure.

Notice changes to a familiar relationship

A familiar name may appear in an unfamiliar payment request. A compromised account or copied profile can exploit existing trust. Suppose a person claiming to be a supplier asks you to settle an invoice into a different wallet and says their usual phone cannot receive calls. That explanation removes a normal verification route exactly when you need it most.

Keep an agreed way of verifying payment changes with regular suppliers or relatives. It might be a call to an established contact or an in-person check when practical. Do not use only the contact details supplied in the suspicious message. An inability to verify is a reason to defer the payment, not evidence that you must trust the new route.

Challenge stories about receiving money

An unexpected prize, refund or investment return can be used to justify an advance payment. Ask what independent evidence establishes that you are entitled to the money and why this particular action is required. A demand to move your existing funds to a supposedly safe account is especially dangerous: the payment itself may be the loss.

Likewise, a request to receive money for someone and forward it elsewhere can involve disputed or stolen funds. A promised commission does not make the arrangement legitimate. Do not allow another person to use your account as their payment route. If unexpected money arrives, contact your provider about the supported correction process instead of forwarding it on demand.

Protect decision time

Create a short personal rule: stop, leave the request, check independently, then decide. Leaving the request may mean ending a call or closing a chat while retaining evidence. It gives you space to inspect the facts without someone directing every tap. You do not owe an unknown caller a live demonstration of your account.

Practise a neutral sentence: I need to verify this through my usual contact before any payment. This is useful even when the request turns out to be legitimate. A genuine business can explain its request and evidence; your decision should depend on verification, not on whether the person sounds offended. Avoid arguments or threats that prolong contact and disclose more information.

Respond constructively after a mistake

If you have already paid, contact the provider promptly, preserve relevant records and describe exactly what you approved and what you were told. A transfer you approved because of deception is different from a debit you never authorised. Both deserve accurate reporting. Do not rewrite the facts to fit the complaint category you think is more likely to succeed.

Be wary of a new person offering guaranteed recovery for an upfront charge. Keep using verified support routes. A friend helping a victim should concentrate on protecting access and organising evidence, not blame. Shame can delay reporting and make a second manipulative offer seem attractive. Recovery is uncertain, but a clear record can still support the investigation.

Guided exercise

1. Write three fictional requests: an urgent supplier account change, a prize-release payment and a request to forward unexpected funds. Do not include working links or real numbers.

2. Under each, identify the requested action and what remains unverified. Name a contact route independent of the message.

3. Role-play the neutral stop sentence. The partner may apply mild time pressure but must not request real credentials or money.

4. Create a fictional incident note showing the story, amount, time, payment action and evidence available. Mark whether the account holder approved the transfer.

5. Write a supportive response to a person who reports a loss, including one immediate practical step and no promise of recovery.

Knowledge check

1. Does a familiar profile name prove a payment request is genuine?

2. Is an approved payment always free from fraud?

3. Should a recovery guarantee justify another payment to an unknown person?

Answer guide

1. No. Verify unusual requests and changes independently.

2. No. A person can approve a payment because they were deceived; report the facts accurately.

3. No. Use verified support and investigate the claim instead of paying for a promise.

Completion standard

Identify the unverified action in all three scenarios, demonstrate a calm pause and produce an accurate incident note. Explain how to support a victim without blame and answer the checks correctly.

Sources and verification notes

FTC mobile payment scam guidance. Checked 15 September 2026. Used for general fraud awareness only. US services, reporting routes and legal protections are not Gambian rules.