Skip to main content
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

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, 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.

For regulated buyers

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.