Help Center

Context-aware help. You came from: /help

Getting started

Link

This help center is organized by feature. Use the search box or pick a section in the left sidebar.

If something looks “wrong”, first confirm your API base URL (runtime-config) and that you’re on the intended environment (UAT vs Production).
For access issues, check Roles & Permissions.

Dashboard

Link

Use the dashboard to monitor volume and workload at a glance.

What the cards mean

Customers (last 7 days): customers created during the last 7 local days.
Transactions today: count of transactions ingested/stored by the system “today” (backend definition).
Transactions (last 7 days): charted by transaction occurrence time (CreatedAtSourceUtc when available).
Screening (last 7 days): sanctions/custom-list searches executed.
Screening (last 7 days): screening activity over the last 7 days.

Time & timezone notes

Charts are displayed by local browser date to avoid “tomorrow” appearing early.
Filters and stored timestamps are typically UTC in the API; when comparing to local day, keep timezone in mind.

Common issues

If a card is zero but you expect data, verify your API base URL (runtime-config) is pointing at the correct environment.
If you see 401/403, your role may be missing required permissions.

Customers

Link

Customers are the core entity for screening, monitoring, and case management.

Quick actions

View customers Add customer Import CSV Duplicates

Importing customers (CSV)

Go to Customers → Import and upload a CSV.
Review the preview/validation and fix missing required fields.
Submit the import and confirm the results report.

Common errors

401 Unauthorized: log in again (session expired) and retry.
400 Tenant not resolved: ensure the browser is logged in and tenant is selected (backend requires tenant context).
CSV import failing: confirm you are using the correct environment API base and required headers/columns.

Transactions

Link

Transactions can be imported or ingested via integrations, then screened and monitored.

Searching transactions

Use Transactions → Search and filter by date range, amount, status, and participants.
If results look incomplete, widen the time range and verify your filters.

Importing transactions

Go to Transactions → Import and upload a CSV/Excel file.
Run a dry-run first if available; then submit the job.
Download the results report to see any rejected rows and reasons.

Transaction timestamps

Charts can use the transaction occurrence time (CreatedAtSourceUtc) when available.
“Transactions today” may use ingestion/stored time depending on backend configuration.

Screening, cases & triage

Link

Screening helps you identify potential matches and manage alerts through case workflows.

Quick links

Cases Screening activity Customers

Typical workflow

Screen a customer or transaction and review the matches/alerts.
Create or open a case for items that need review.
Add notes, assign an owner, and set disposition/status.
Export evidence when needed (audit/reporting).

Common tasks

Re-run screening after customer data changes or on schedule.
Use presets to tune strictness (reduce false positives / increase recall).
Link alerts to cases to keep an audit trail.

Common issues

If alerts are missing, check your preset configuration and enabled sources.
If you cannot create/update cases, verify your role permissions.

Sanctions

Link

Sanctions screens names against configured lists and shows likely matches.

Quick links

Screen Lists

How to use

Open Sanctions → Screen and enter a name (and optional details).
Review matches and validate with supporting attributes.
Use Lists to confirm list coverage and freshness.

Troubleshooting

If results look noisy, tighten the screening preset (Risk → Presets).
If lists are empty/stale, verify the sanctions importer is running and up to date.

Monitoring

Link

Monitoring surfaces ongoing risk signals and alert inboxes for triage.

Quick links

Monitoring overview TM alerts Cases

Alerts and triage

Use alerts as your inbox for high/critical items that need review.
Assign alerts/cases to owners to track accountability.
Create cases from alerts when you need notes, evidence, and disposition.

Transaction Monitoring (TM)

TM evaluates transactions over a rolling window and produces alerts based on scenarios.
Use TM alerts to quickly triage and escalate.

Common mistakes

Too many enabled scenarios/rules at high sensitivity creating noise.
Not validating alerts against real examples after changing rules/presets.

Billing & Plans

Link

Billing shows plan, add-ons, and usage that impact limits and costs.

What you see

Current plan and included allowances (e.g., searches/month).
Add-ons currently enabled for your tenant (if any).

Common questions

Why is search allowance low/high? It comes from your active subscription plan.
Why can’t I see billing? Your role may be missing billing:view / billing:manage.

Risk Management

Link

Risk Management controls how risk is computed and how screening/monitoring behaves for your tenant.

Quick links

Risk overview Rules Signals catalog Screening presets Country risk UCID matching settings

Core concepts

Signals are the individual risk factors (e.g., country, behavior, transaction patterns).
Rules decide how signals contribute (enabled/disabled, weight, thresholds, overrides).
Presets control screening behavior (how strict name matching is, candidate pool size, etc.).

Recommended setup order (initial rollout)

Start with the Risk overview to see current distribution and any obvious outliers.
Review Signals to understand what is available and what each signal means.
Configure Rules (enable/disable + weights + thresholds) for your policy.
Tune Screening presets and Country risk to match your risk appetite and jurisdictions.

Rules (how to use)

Enable only signals you want enforced. Disabled rules should not affect scoring.
Weights increase/decrease the contribution of a signal to the overall score.
Use thresholds/overrides to force a minimum risk level for certain conditions when needed.

Signals catalog (what it is)

This is a reference list of all signals the system can evaluate.
Use it to decide what rules to enable and how to weight them.

Screening presets (how to tune)

Presets control how fuzzy matching and candidate selection behave during screening.
Start with a recommended preset, then tighten/loosen based on false positives/negatives.
If you change presets, validate with known good/bad examples before rolling out broadly.

Country risk (how to use)

Set per-country scores (0–100) to add extra risk for higher‑risk jurisdictions.
If a country is not configured, it behaves like risk=0 (no extra risk added).

UCID matching settings (identity clusters)

These settings affect how customers are clustered into UCIDs (identity graphs).
Change carefully: clustering affects monitoring, alerting, and downstream reports.

Permissions

To view: risk:view (and related view permissions).
To edit: risk:manage and/or country-risk:manage and screening:presets:manage.

Common mistakes

Changing many rules at once without validating against historical examples.
Over-weighting multiple signals so most customers become High/Critical (noisy).
Editing UCID matching settings without understanding how it impacts monitoring results.

UCIDs (Identity clusters)

Link

UCIDs group related customer identities so monitoring and risk can be evaluated at the cluster level.

Quick links

UCIDs Matching settings

What this affects

Clustering changes what’s considered “the same entity” across customers.
Monitoring and transaction risk can be elevated by cluster risk (highest member risk).

Audit log

Link

Audit log records key actions for compliance traceability.

How to use

Open Audit and filter by date, table/entity, or operation.
Use correlation IDs to trace a change across multiple events.
Export or capture evidence for compliance reviews if needed.

Notes

Audit is read-only for most users.
If audit is empty, verify permissions and that the environment has audit enabled.

Admin (Roles & API)

Link

Admin controls permissions (roles) and API access (keys).

Roles & permissions (recommended workflow)

Create a role with the permissions you want to grant.
Create users (or invite them) and assign the role.
If a user sees 403/hidden menus, verify their role includes the required permissions.

Open Roles & Permissions

API keys

Create an API key for integrations; copy it immediately (it won’t be shown again).
Rotate keys by creating a new key and revoking the old one.

Open API page