7/1/2026, 11:44:54 AM
Decision summary
Focus deliberation on caller scripts, claimed organisations, and safer customer education wording.
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
The scammer starts an account reset, login, or transaction, then calls the victim to collect the OTP needed to complete it.
The attacker creates fear, borrows the language of customer support, and tries to keep the victim on the call until the code arrives.
End the call. Contact the organisation through the official app, website, or printed card number. Change passwords and enable stronger account protection where available.
Do not read out OTPs, PINs, recovery codes, card numbers, or passwords. Genuine support teams do not need them.
Focus deliberation on caller scripts, claimed organisations, and safer customer education wording.
Forum status
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.
