Supplier message
Someone appears to speak for a person or organisation already trusted. Warning: unexpected changes or requests. Verify using contact details you already know or find independently.
Illustrative comparison
Compare across contexts
The Fraud Map reorganises the pattern library into fictional setting-based narratives rather than separate country risk profiles.
Fraud Map
Search illustrative contexts
Fictional illustrative pattern only; not a prevalence estimate. Try broadening your search or filters, or clear all map filters.
Claimed penalty
Urgency and pressure are warning signals. The threat may be imaginary or exaggerated. Verify the claim separately and contact your payment provider promptly if money moved.
Personal correspondence
Repeated contact builds rapport over time. Warning: familiarity is offered instead of independent evidence. Verify the claim through a separate trusted source; pause any payment while checking.
Account-use offer
An unusually attractive opportunity is presented. Warning: promised benefits depend on an upfront payment or secrecy. Verify independently and decline payment until the claim is established.
Claimed emergency
An alleged danger, crisis, penalty or emergency creates pressure. Warning: an immediate deadline or demand not to check. Contact the affected person independently; pause before paying.
Colleague message
A message or identity may appear connected to someone already trusted. Identify what is observable without assuming who controls an account or who sent a message.
No illustrative contexts match
Try broadening your search or filters, or clear all map filters.
All locations and narratives are fictional sample contexts, not live crime statistics or prevalence estimates. No country or community is inherently associated with fraud. Each example follows trust → transfer → disconnect and offers safe response guidance.
Privacy: your selected pathway and filters are saved in this browser for this experience. Do not enter personal or case-sensitive information.
For analysts
Document the payment journey consistently
Capture observable facts, distinguish reports from verified findings and avoid recording unnecessary personal details here. These are prompts, not a case-submission form.
Payment method
What instrument was involved?
Transaction direction
Incoming or outgoing?
Urgency signal
Was a deadline or threat reported?
Recipient relationship
Was there a legitimate connection?
Account role
Was an intermediary described?
Geography
Where were parties and payments located?
Compare the educational patterns and use the analyst field list to record cases consistently without assuming intent.