KYC as pass or fail steps
Company data, ownership, sanctions, and identity. Your team only acts when judgement is needed, and the contract is not signed until identity validation succeeds.
KYC inside the application
KYC is often an afterthought, or identity sits outside the process. Here it is a set of steps. Checks run when they are needed, and your team only acts when judgement is needed.
- Identity before signing
- The signer must pass digital identity validation before the contract is signed.
- Sanctions checks
- Each entity and individual is screened against 231 global sanctions lists.
- Routing from the outcome
- Low, medium, or high can trigger an alert or a scheduled re-check.
- UBO in the same application
- Applicants declare UBOs. The data is checked against the register.
- On the timeline
- Each check, match, discrepancy, and identity method is recorded.
Frequently asked questions
- Is identity verification mandatory?
- The contract cannot be signed until an identity validation strategy succeeds. Several fallback strategies are supported.
- What if no risks or matches are found?
- The checks are logged. The step completes. No person is required.
- Can we configure the scoring mechanics?
- Yes. Thresholds, escalation rules, and activity risk lists follow your policy.
- How are system and human risk assessments used?
- A difference between the automated score and the handler’s score is flagged.
