What a record lets you verify
- That the check was made
- A record exists for the payment, was signed before release, and nothing in it has changed since.
- Against which lists
- The record names the lists screened and the version of each. A check made against a list that had already been superseded shows as exactly that.
- With what result
- Cleared, held for the bank’s review, or stopped, and the citation behind each.
- Without the payment
- Verification needs the record and the public keys we provide. The record carries the result and what was checked, not the payment file, so a supervisor verifies without receiving payment data.
Across every institution you oversee
One record answers for one payment. Across all the institutions a supervisor oversees, the same records are designed to answer a wider question: did each of them screen against the lists in force, and when did any fall behind? That view is designed to be built from records alone, to carry no payment data, and to be the supervisor’s own.
Who decides what you see
What a supervisor sees is set by the institution and by the rules of its jurisdiction, not by us. At the least: that a record exists and verifies. Where the institution provides it, or a rule requires it: the record itself. Xattestation never supervises, never grades an institution and never replaces a supervisor’s judgement. It makes the evidence that judgement rests on verifiable.
In a sandbox
In a regulatory sandbox the supervisor can follow a test as it runs: every record made in testing verifies with the same keys, and the supervisor’s own view of the test is part of what is tested. A supervisor in any jurisdiction is welcome to observe a test.
What it costs a supervisor
Nothing. Verification is free and stays free; attestation is what a bank pays for. In production, Xattestation is designed to run in each jurisdiction as a company of that jurisdiction, under its law and whatever oversight its supervisor decides. Where it runs.