KENNETH / SCOPE & AVAILABILITY
Database, liveness & fraud checks
Document capture, a live face and a database lookup answer different questions. Each check has its own prerequisites and availability.
Kenneth creates a hosted verification session against a configured workflow. The repository does not expose that workflow’s current enabled checks. Confirm document, biometric, fraud and database settings for your account before relying on them.
FACE CAPTURE / ILLUSTRATIVE PREVIEW
A live person.
A face to compare.
Liveness checks assess the capture. Face matching compares it with the document portrait. Together, they give your team evidence to review.
Document fraud analysis
Where configured, document analysis checks templates, tampering and data consistency. Document liveness looks for screen replays or reproduced documents. A check is a signal for assessment, rather than a guarantee against fraud.
Face comparison
Compares a captured face to the identity-document portrait. It answers whether the images appear to show the same person. It is separate from Kenneth’s review of the expected director or shareholder.
Liveness & anti-spoofing
Passive or active liveness, where enabled, assesses whether capture comes from a live person rather than a presentation attack. This is a capture-time check, not an ongoing watchlist-monitoring service.
Identity database checks
Database validation can compare extracted identity data with a specific government, civil-registry, tax, electoral or credit-bureau source. Service prerequisites can include an identification number, date of birth, consent and commercial provisioning. Some countries have catalogue services that are not activated.
Additional fraud signals
Device and IP analysis are supported by the verification technology, but Kenneth account configuration has not been verified. No claim is made here for enabled NFC, digital wallets, face search, transaction monitoring or ongoing AML monitoring.