Documentation Index
Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
FrankieOne uses workflows and standard bundles to provide fast, opinionated configurations for common KYC, AML, and monitoring use cases.- A workflow is a named, versioned configuration that defines:
- Which checks run (for example, AML, transaction and activity monitoring, and fraud signals).
- How results are evaluated and mapped to a final
workflowResult. - How issues or alerts are created in the FrankieOne Portal.
- A standard bundle is an out-of-the-box workflow that FrankieOne maintains and recommends for a given use case (for example, AU Essential KYC, Risk-Based Onboarding, or Basic Monitoring for Transaction and Activity Monitoring). These bundles are:
- Pre-configured based on best-practice compliance.
- API-addressable via a stable
workflowName. - Extensible – customers can start with the default and move to custom workflows as needed.
Onboarding Fraud Standard Bundle
For onboarding fraud, see Risk-based onboarding standard bundles, which covers the AU Essential KYC and Risk-Based Onboarding workflows.Transaction and Activity Monitoring Standard Bundle
All workflows under Transaction and Activity Monitoring will have lifecyclePhase: MONITORINGBasic-Monitoring-TxAM
The standard bundle for Transaction and Activity Monitoring is Basic-Monitoring-TxAM (where TxAM is a technical identifier for Transaction and Activity Monitoring used in bundle names).| Field | Value |
|---|---|
| Monitoring types | ["ACTIVITY"] |
| Checks/Steps available | ACTIVITY_FRAUD – fraud and behavioral rulesACTIVITY_AML – AML transaction monitoring rules |
| Risk profile | Essential and baseline monitoring |
| Typical users | Digital financial services, fintechs, wallets and brokers who want fraud, behavioral, and AML activity monitoring (logins, account and device changes, deposits, withdrawals, high-risk transfers) and are happy to start from FrankieOne defaults. |
| Result Types Mapping | 1. Any step HIT → workflowResult.status = REVIEW and creation of an ACTIVITY issue.2. All steps CLEAR → workflowResult.status = PASS or CLEAR.3. Any step ERROR → workflowResult.status = FAIL |
| Issue Types Mapping | 1.ACTIVITY_AML (AML-related alerts on transactions)2. ACTIVITY_FRAUD (fraud and behavioral alerts) 3. ACTIVITY_EVENT (non-transactional behavioral events) |