Duty to mechanism
How the machinery works
- Screening runs before delivery, not after. A payment whose payer fails screening does not produce a success webhook — see Compliance engine.
- Verdicts carry no names. A decision is
ALLOW,REFERorDENYplus reasons that do not disclose the list hit — deliberate, for SAMLA. - Every event is hash-linked. Altering a row breaks a property an auditor tests at export, not a log line someone has to notice.
- Screening data has an audit trail of its own. The screening-hit and
compliance-event chains verify independently:
/compliance/verify.
For regulated buyers
- Compliance overview — the developer-facing summary, and the
canonical binder at
algovoi.co.uk/compliance.html - Security posture — claims with source pointers, DD pack on NDA
- Verifiable Compliance Suite — run the evidence estate on your own infrastructure
- Compliance Command Center — operator console for screening, cases and evidence
This page maps mechanisms to duties. It is not legal advice, and a mapping is
not a programme: your MLRO still owns the risk assessment, the policies and the
filings.