How the ceremony works

WireWatch is a process control, not a detection tool. Every payment instruction passes through the same four deterministic steps.

1. Hold — deterministic risk rules

The rules engine scores every instruction 0–100 from amount × beneficiary-novelty × channel × urgency. Score ≥ 20 holds. Signals that hold on their own:

Same inputs, same verdict, every time. No ML, no voice detection, no guessing.

2. Callback — out-of-band, to the known-good number

Your team calls the number on file — never the number in the message — and records who called, when, and whether the confirmation code matched. WireWatch never calls anyone for you; it records your evidence.

3. Dual approval — two people, two devices

Release needs two approvals from different people on different devices. A single approver, or two approvals from one phone, cannot release. A reject blocks the payment.

4. Release — into a hash-chained ledger

Every step — hold, callback, approval, release — lands in a SHA-256 hash-chained audit ledger. Tamper-evident, exportable (Pro), and ready for your insurer or auditor.

Drill mode (Pro)

Run consent-based attack drills on your own team — fake CEO WhatsApp, vendor email change, urgent voice call:

Drills score ceremony discipline: hold (+40), callback (+30), dual approval (+30).

Vendor master & imports

Keep known-good contacts in your vendor master. WireWatch stores only a SHA-256 hash of bank account numbers — never the numbers themselves. Pro plans can import vendors from a CSV (compatible with Xero/QuickBooks contact exports). This is a CSV import, not a live accounting sync.

What WireWatch does NOT do

Honest scope is the product. The ceremony is what stops the wire.