Compliance

The Compliance area is the operator triage queue. When a payment or a ramp trips a screening review, a case lands here for a compliance officer to work. The console lets you review the queue, move a case through its lifecycle, and place or lift a hold on an account holder.

Where cases come from

A case is created when a screening decision asks for review. That happens when a payment, an on-ramp, or an off-ramp is flagged by transaction screening. XKOVA orchestrates screening through interchangeable providers, so the decision that creates a case comes from the screening pipeline. For the model, see Screening.

Work the queue

The queue lists cases for the active tenant. Filter by state to focus on what needs attention, then click a case to open its detail. The detail panel shows the case type, priority, evidence, and the transitions that are valid from its current state.

Action	What it does
Filter by state	Narrow the queue to open, investigating, escalated, SAR filed, closed, or all.
Open a case	Expand the detail panel with its transitions, comments, and evidence.
Transition state	Move the case along its lifecycle using the buttons valid for its current state.
Add a note	Attach evidence or rationale as part of a transition.
Escalate	Move the case to the escalated (manager review) state, optionally reassigning and attaching a note.
Close	Reach a terminal state with a recorded reason.

The case lifecycle

A case moves through a defined set of states, and only the transitions valid from the current state are offered. A typical path runs from open, through investigating or escalated, to closed. Each transition is recorded in the audit trail with the actor and the rationale.

Hold and release an account holder

Triage can also act on the member behind a case. From the Accounts directory, a compliance officer can place a hold on an account holder, recording a reason, which blocks further activity for that member. The same surface lifts the hold with a release. Both actions emit audit events so a later reviewer can see what happened.

The Accounts page is a unified directory: it lists end-user account holders, staff operators, and treasury vaults together, each row opening that kind's own detail page. Holds and releases apply only to end-user account holders in that list.

Holds and releases are deliberate, audited actions. The reason you record travels with the event, so a later reviewer can see why a member was held and by whom.

Verification gates fail closed

Where an action depends on a member's verification status, an unknown or missing status is treated as not verified, never as a pass. Identity verification itself is orchestrated through interchangeable providers; see Identity Verification.

For the audit trail behind every action here, see the Audit Log. For the exact operations, see the operations list or the interactive reference. To receive case events in your own systems, see Webhooks.

Was this helpful?