Glossary¶
Shared vocabulary for MasteryHive product and partner docs. Where a term differs by product, both meanings are noted.
| Term | Meaning |
|---|---|
| Baseline | Fraud: behavioural profile built from a customer’s historical transactions (temporal, location/device, amount patterns) before or alongside scoring. |
| Check | A discrete verification or baseline computation (for example a KYC ID check, or a Fraud temporal/location/transaction check). |
| Prediction | Fraud: ML or rule output describing risk for a transaction (score / level / flags). Must satisfy the fraud output contract before report compose. |
| Report | Fraud: structured investigator payload delivered to the dashboard after contract validation, policy, and narrative. |
| Post-action | Work that happens after scoring/report handoff (for example dashboard case workflows). Often outside the AI backends. |
| Case | In Fraud AI docs: usually case-management rule evaluation (synchronous prediction). Durable case records (assignee, closure) live in the application backend where implemented. |
| Exception | Reconciliation: a detected mismatch or anomaly cluster awaiting operator decision (approve, reject, escalate, reopen, reconcile). |
| Reconciliation session | A single money or asset reconciliation run scoped by identifiers such as session_id, partner, and tenant. |
| Tenant | Customer isolation key. Fraud: x-tenant-id header on scoring. Reconciliation: tenant_id in bodies. KYC: no tenant field — isolation is by userId and environment agreement. |
| Partner | Organisation integrating with MasteryHive; Reconciliation often carries partner_id alongside tenant_id. |
| PEP | Politically Exposed Person — screening category in KYC/AML. |
| STR | Suspicious Transaction Report — regulatory report type (goAML-related programmes). |
| CTR | Currency Transaction Report — regulatory report type (goAML-related programmes). |
| FTR | Funds Transfer Report — regulatory report type in some jurisdictions / goAML programmes. |
| Cold start | Fraud: customer has too little history for a stable baseline; profile persistence may be skipped. |
| Ingestion | Reconciliation: starting ETL / matching for money or asset files. |
| Resolve | Reconciliation: applying an operator decision to exception clusters (messaging-primary in production; HTTP fallback). |
| GA | General availability — product ready for broad customer use after evidence gates. |
| PARTIAL | Capability exists in code but is incomplete for production claims (wiring, submission, lifecycle, etc.). |
See also: Platform overview · Documentation map