Fake transfer alert review
7/1/2026, 11:44:57 AM
Decision summary
If you see this, take these steps
Collect alert wording and merchant controls that reduce pressure at point of sale.
Verify payments independently
Do not release goods or funds until you confirm inside your bank app.
Escalate suspicious requests
Use the official support channel instead of replying to the scam chat.
Report identifiers
Send handles, phone numbers, and payment links so TrustOps can corroborate.
Playbook sections
- What happened
- How it works
- Red flags
- What to do now
- Evidence / references
What happened
The scammer presents a fake or edited payment confirmation and uses urgency to obtain goods, refunds, or services before a real credit lands.
How it works
Fake alert templates imitate bank sender names and transaction wording, but the merchant account never receives the funds.
Red flags
- The alert arrives as a screenshot instead of in your own banking channel.
- The buyer claims network delays while demanding immediate release.
- The reference number cannot be confirmed in your bank app.
What to do now
Confirm the credit in your own banking app or USSD channel before release. Preserve the screenshot, chat, and phone number for review.
What not to do
Do not release goods, issue refunds, or pay delivery charges because another person shows you a receipt.
Evidence notes
- Fake alerts often reuse the same wording across multiple merchants.
Moderation brief
Collect alert wording and merchant controls that reduce pressure at point of sale.
Forum status
Read-only curated thread
This public thread is a moderated briefing surface. Fresh evidence and supporting notes go through reviewed submission routes before TrustOps updates the public thread. Use reports for incident evidence, Ask TrustOps for questions, and fraud cards for card-specific deliberation.
Have more intelligence to add? Return to the forum index or review community rules.