> ## Documentation Index
> Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance duties

> UK MLRs, SAMLA, OFAC, OFSI, EU consolidated, travel rule, AI Act and DORA record keeping, each mapped to the AlgoVoi mechanism that discharges it.

A stablecoin payment desk carries the same duties as any other money
transmission business, plus record-keeping duties that attach to the payment
event itself. This page maps each duty to the thing that discharges it, so you
can take the mapping to your MLRO rather than to a sales deck.

## Duty to mechanism

| Duty | What it requires | What AlgoVoi does | Evidence you can hand over |
| - | - | - | - |
| UK MLRs 2017 | Customer due diligence, risk-based approach, record keeping | Risk-tiered onboarding, KYB gating, 4-tier risk classification, retention | [Compliance overview](https://docs.algovoi.co.uk/compliance.md) · [KYC and mainnet](https://docs.algovoi.co.uk/concepts/kyc-and-mainnet.md) |
| Sanctions — OFSI, OFAC SDN, EU consolidated, UN via EU cascade | Screen the parties to a payment against designated persons | Daily-refreshed wallet and name screening before the payment event is released | [`/compliance/screen`](https://api.algovoi.co.uk/compliance/screen) · [Sanctions monitor](https://docs.algovoi.co.uk/sanctions-monitor.md) |
| SAMLA 2018 | No tipping off; the subject must not learn they were reported | Generic verdicts only — a decision code, never a list name | [No-PII compliance receipts](https://docs.algovoi.co.uk/no-pii-compliance-receipt.md) |
| FATF Travel Rule (Rec. 16) | Originator and beneficiary data travel with the transfer | Signed travel-rule payloads, no PII in the receipt | [Travel rule](https://docs.algovoi.co.uk/travel-rule.md) |
| Audit and record integrity | Records cannot be altered after the fact | SHA-256 JCS hash chain across audit, screening and compliance events | [Audit chain](https://docs.algovoi.co.uk/platform/audit-chain.md) · [Audit log](https://docs.algovoi.co.uk/audit-log.md) |
| EU AI Act Art. 12 | Automatic logging for high-risk AI systems | Append-only event records with per-entry verification | [EU AI Act record keeping](https://docs.algovoi.co.uk/eu-ai-act-recordkeeping.md) |
| MiCA 68(9) and DORA logging | Retention and ICT incident records | Hash-chained retention plus post-quantum signing | [MiCA and DORA evidence](https://docs.algovoi.co.uk/mica-dora-evidence.md) |
| UK GDPR | Data minimisation in what you retain | No-PII receipts; KYC documents encrypted at rest under a separate key | [Compliance and security](https://docs.algovoi.co.uk/compliance.md) · [No-PII compliance receipts](https://docs.algovoi.co.uk/no-pii-compliance-receipt.md) |

## 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](https://docs.algovoi.co.uk/platform/compliance-engine.md).
* **Verdicts carry no names.** A decision is `ALLOW`, `REFER` or `DENY` plus
  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`](https://api.algovoi.co.uk/compliance/verify).

## For regulated buyers

* [Compliance overview](https://docs.algovoi.co.uk/compliance.md) — the developer-facing summary, and the
  canonical binder at `algovoi.co.uk/compliance.html`
* [Security posture](https://docs.algovoi.co.uk/security.md) — claims with source pointers, DD pack on NDA
* [Verifiable Compliance Suite](https://docs.algovoi.co.uk/verifiable-compliance-suite.md) — run the
  evidence estate on your own infrastructure
* [Compliance Command Center](https://docs.algovoi.co.uk/compliance-command-center.md) — operator console
  for screening, cases and evidence

> [!NOTE]
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.