verify_callback_record
shallowcom.psychevus/email-security · Verify this server
Verify a callback record file saved by https://psychevus.com/tools/payment-check/callback-record. It answers three questions separately (layers): integrity (both digests, the sealed verdict, the approval refers to this exact record), history (both timestamps against this site's published keys; the call dated no more than 3 days before the record was sealed and not after it; the request not dated after it; no signed time in the future; approval sealed after the callback, within 7 days, under a name different from the caller's), and current (the approval is at most 7 days old now, and it is for the change you are making: pass expected_supplier and expected_account, the full new account, both taken from the change you are about to make, not from the record). Returns approved / expired / mismatch / unbound / awaiting-approval / hold / stop / invalid. Only approved may be acted on, and it is returned only when both expectations are given and match: the full account is compared against the record's keyed fingerprint, because the last 4 characters are shared by many accounts. unbound means a valid, recent approval that isn't tied to your change (expectations missing, only the last 4 characters given, or a record sealed before account fingerprints); expired means it was a valid approval but is now only evidence of what was checked then; mismatch means it approves a different supplier or account. expected_account_last4 is still accepted: it can show a mismatch, never a match. An agent must not change a supplier's bank details unless this returns approved; approved is necessary, not sufficient. What it can't prove: that the call happened, who the people named are, or that two different people were involved (only two different names).
1 trials · measured 10 days ago
verify_callback_record scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.psychevus/email-security, measured 12 Nov 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-11-12 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/db7a6e56-ae9a-4c71-83a4-e3e4dd9285c9)