Day-0 Fraud Telemetry for FMS
Waspada AI
Pitch workflow · Bank case ⨝ Threat indicators
Partner bank app Bank-side only
Victim is already logged in. Identity stays in the bank case system — never sent to Waspada.
CIF-DEMO-0001
+60-12-000-0001
000000-00-0001
—
Creates an opaque partner_case_id the bank keeps with the victim record.
Waspada edge extract Indicators only
On-device extraction from receipt / chat evidence. Optional suspicious link → RDAP domain age (registry lookup — not a web search, not a “scam verdict”).
What the bank keeps
- DEMO VICTIM 001
- CIF-DEMO-0001
- +60-12-000-0001
- 000000-00-0001
Never in Waspada telemetry.
What Waspada receives
Run synthetic extract to populate.
Pitch story: mule account from the receipt + domain age from RDAP on the link. We do not open or crawl the page.
Uses unmistakably fake mule/URL fixtures — not live FI data. Optional: upload a file in the main sandbox for a live OCR run.
Join in FMS Bank ⨝ Waspada
The Fraud Management System (FMS) sees one case: victim context from the bank + advisory indicators from Waspada.
Bank case
- partner_case_id
—- Victim
- —
- CIF
—- Contact
—
Held only by bank
Waspada advisory alert
- partner_case_id
—- Mule account
—- Bank BIC
—- URL / RDAP
- —
- Disposition
- advisory · MONITOR
No victim PII
Where this sits on the real timeline
- Minutes: Join alert → bank case via
partner_case_id; structured mule + RDAP signal in FMS - Earmark window: Check ledger — did this mule account actually receive funds? Bank policy decides any hold — Waspada does not freeze
- Days 1–14: Investigation Pack supports police / legal while the court order path runs
- Not in scope: Replacing 997 / NSRC, authenticating images, or issuing freezes