Trust Console demo
A lookalike vendor asks to change its bank details before the payment run. Switch roles to see how one cross-system trust decision changes what each person sees and what they're allowed to do.
From Acme Supplies Billing <[email protected]> · Email · 9:14 AM
URGENT: updated remittance details before Friday payment run
High-risk payment-detail change. You can view it, but you can't change bank details on your own.
Hi Sam, We've moved banking providers. Please update our remittance details before Friday's run: Bank: First Coastal · Routing: 0xx-xxx-118 · Acct: ••••4471 Our old account will be closed. Please confirm by reply today, thanks! Jordan, Acme Supplies Billing
What you can do next
Policy: AP role + payment-detail change → trusted callback and a second approver required. Reply and links disabled.
Cross-system trust signals
87 / 100 risk- Risk
Verified-org registry
Not a registered origin for Acme Supplies
- Risk
Domain authentication (DMARC/SPF)
Passes, but a lookalike of acme-supplies.com
- Risk
Domain age
Registered 6 days ago
- Caution
On-device intent model
Payment-detail change + urgency
- Caution
Vendor master record (ERP)
Bank details unchanged since 2023
- OK
Known-good contact
Phone on file, so a trusted callback is available
Signals come from partners the provider orchestrates. It doesn't inspect raw content.
Privacy receipt
- Message content
- Processed on device
- Left the device
- Sender domain, risk score, intent label
- Retained
- Event metadata, 90 days
- Used for model training
- No (not opted in)
Audit trail
Switch roles or take an action to see it logged here.