Static snapshot. A frozen copy of the operator dashboard, safe to open anywhere. The buttons below are drawn but inert — recording a verification and being refused the release is a state change, so it runs on the live app: python src/demo.py --serve.
- From
- billing@surakshaagro.com
- Received
- 28 Jun 2026, 21:57
- Subject
- INV-4436
- Reply to
- not a reply
- Thread
- THR00666
The message
Hi there,
Our treasury has consolidated everything into a single facility this quarter, and settlements now arrive at 205365396037 (PUNB0120913).
That covers INV-4436, which remains unsettled, as well as the monthly billing that continues.
Our GST registration is 07URYVC7671V1Z9.
Total on this one is Rs 83,908.
If this could go out in today's run it would help us enormously.
Copying our shared inbox as well, in case I am away when this lands.
Thanks,
Vikram Sethi
Suraksha Agro
What the sender resolved to
- Supplier
- VEND0073
- Matched on
- Known sender
- Because
- the email domain is in our supplier records
- Domain matched
- surakshaagro.com
- Triage decision
- Needs review
- Change request filed
- doc_a51d6cedfd2c643d
mentions an account, a bank or a settlement destination
Sender matching decides whether a message is read in full. It never decides a payment on its own — a lookalike domain is a reason to look, not a reason to reject.
What happens to the payment
Released
Routine payment — nothing was being changedR2a_no_change_confirmed