You do not call any special “compliance” endpoint to be covered. Keep using the documented Self-Exclusion and Deposit Limits APIs — the regulatory ingest and reporting run on Anunnaki’s side.
The three obligations
| Obligation | What it covers | How Currents satisfies it |
|---|---|---|
| Self-exclusion | The KGC comprehensive master self-exclusion list must block listed players across all licensed brands. | The master list is ingested centrally and matched cross-tenant by default at GET /v1/exclusions/check. |
| $10,000 threshold (s.28) | Any transaction or series of transactions over USD 10,000 in a defined window must be reported. | Detected from the transactions you already stream to the AML API (rules R-001 and R-009) and compiled into the KGC threshold report. |
| Self-limitations (s.229A) | Player-set self-limits (deposit caps, etc.) and their changes must be reported regularly. | Every change made through the Deposit Limits API is recorded and compiled into the KGC self-limitation report. |
How you get coverage
Stream events as documented
Keep calling Self-Exclusion, Deposit Limits, and AML (
POST /v1/aml/event) exactly as described in their reference pages. No extra fields, no extra calls.Cross-brand enforcement is automatic
KGC master-list exclusions are matched on every
check regardless of tenant, so a player excluded on one brand is blocked on all of them.What this does not change for you
- No new request/response shapes. The compliance coverage is additive and invisible at the API surface.
- No tipping-off risk. As with AML, never surface compliance internals (rule codes, report status, master-list membership) to end users — use neutral language only.
- Report generation is internal. The admin ingest and report-export tooling is operated by Anunnaki and is intentionally not part of this public reference.
Questions about your brand’s KGC coverage? Contact Anunnaki compliance via your integration manager.