Skip to content
Lotus Comply

Lotus Comply / Verify

Selectable service

Look beyond the uploaded document.

Collect private identity evidence, understand what a scan actually establishes and route every unresolved check to the right next step. Commissioned checks and approved rules guide eligible automation.

Who uses it

Onboarding teams, evidence reviewers and identity operations leads.

Lotus Comply / Verify

Sample workspace

Identity evidence · V03

Technical hold
Identity evidence

Sample document

MRZ observation · extraction ≠ authentication
Sample workspace data

Inside Verify

The work behind the outcome.

From the first input to the final handoff, understand what is captured, what gets checked and what still needs a person’s judgement.

Complete process

One flow. Explicit next steps.

  1. 01

    Receive evidence

    Validate the authorised upload and required evidence slot.

  2. 02

    Process & extract

    Record document fields, MRZ observations and quality signals.

  3. 03

    Check enabled sources

    Run only commissioned checks required by policy.

  4. 04

    Evaluate every gate

    Separate completed checks, exceptions and unavailable sources.

  5. 05

    Record & route

    Retain the outcome and send unresolved work to remediation or review.

Eligible verification

All required, enabled checks meet approved thresholds. Conditional target model; not final KYC approval.

Remediation / review

Low confidence, conflicting fields or a missing mandatory check requires evidence or human review.

Technical hold

A required provider times out or is unavailable. Retry or resolve the source; never record a pass.

Example workflow. Selected services, mandatory requirements, source availability and institutional authority determine the permitted next step.

Example outcome model

Technical hold — not verified

The required check remains outstanding. Resolve the source issue or retry under authorised controls.

01

Verify / intake

Evidence starts in the right slot.

An authorised user uploads a document into a defined evidence requirement. The institution’s country pack determines accepted types; file acceptance alone does not establish identity.

  • Accepted country-specific document types
  • Type and size validation before processing
  • Private upload access and evidence metadata
02

Verify / history

Replace the scan. Keep the history.

A blurry or outdated upload can be replaced without pretending the original never existed. Reviewers can distinguish the latest evidence from earlier versions and understand why a replacement was requested.

  • Document version and replacement reason
  • Recorded evidence slot and uploader authority
  • Earlier evidence remains traceable
03

Verify / extraction

Bring document details into evidence review.

Extraction brings document fields and machine-readable-zone observations into review. Quality and confidence signals help identify unclear images; a readable MRZ is not proof that an issuer authenticated the document.

  • Extracted name and document identifiers
  • MRZ consistency and image-quality observations
  • Confidence interpreted against configured thresholds
04

Verify / providers

Configure the identity checks your institution needs.

Identity and document provider adapters support institution-specific connections. Agree lawful source access, document coverage and required checks, then validate them before activation. Issuer, NFC and biometric services require separate commissioning.

  • Confirm provider permissions and document coverage
  • Define mandatory checks before activation
  • Keep unavailable and incomplete checks visible
05

Verify / automation

Automation has an explicit eligibility boundary.

The target experience is automation-first where authoritative enabled checks and policy thresholds genuinely satisfy every required condition. A successful extraction cannot substitute for a missing issuer or biometric requirement.

  • Every required condition must pass
  • Record which checks supported the outcome
  • Keep verification separate from onboarding approval
06

Verify / exceptions

Make the next action clear.

Low confidence, inconsistent information or missing evidence leads to remediation or a reviewer exception. A timeout follows a technical-hold path, so source availability cannot accidentally become customer clearance.

  • Request a clearer or replacement document
  • Assign conflicting facts for review
  • Retry unavailable sources under authorised controls
07

Verify / configuration

Configure the standard before the queue grows.

Country packs, evidence requirements, confidence thresholds and review responsibilities make the workflow institution-specific. Changes need controlled configuration—not an informal reviewer workaround.

  • Accepted evidence by country and product purpose
  • Mandatory source and policy thresholds
  • Role-appropriate exception ownership
08

Verify / handoff

An evidence outcome is one part of a decision.

KYC or KYB teams can use permitted verification evidence when those services are selected. Screening, risk, consent and final review requirements remain independent gates; Verify does not grant a global identity approval.

  • Permitted handoff to the relevant review
  • Recorded reasons and outstanding checks
  • Independent final institutional determination

Information in context

See what the team works with.

A sample verify workspace shows the relevant fields and outstanding work.

Lotus Comply / Verify

Sample workspace

Identity evidence · V03

Technical hold
Identity evidence

Sample document

MRZ observation · extraction ≠ authentication
Document
Sample passport
Country pack
Configured document list
Evidence slot
Primary identity
Extraction confidence
Below policy threshold
Issuer check
Required · unavailable
Biometric check
Not completed
Sample workspace data

In practice / Digital banking

An uploaded passport needs more than a readable name.

An applicant supplies a clear scan. Extraction completes, but a required issuer source is unavailable. The team sees the extracted fields alongside a technical hold—not a verified customer—and resolves the source before proceeding.

What becomes clearer

Separate evidence progress from assurance, so operational gaps remain visible instead of silently becoming passes.

Questions & answers

Before you choose Verify.

Can we select Verify on its own?

Yes. The agreed scope identifies the required supporting controls, sources and provider dependencies; each service is selected independently.

Does document extraction prove identity?

No. It assists checks; identity assurance depends on the evidence and authoritative checks actually performed.

Does every document need manual review?

The target model routes eligible results through approved automation, with people handling exceptions. Current production eligibility must be confirmed during implementation.

What if a required source is unavailable?

The check remains on technical hold for an authorised retry or remediation. It cannot be recorded as a pass.

Are national identity and biometric providers already connected?

No universal source or biometric coverage is assumed. Lawful access, provider approval, testing and commissioning are required.

Does a positive result approve the customer?

No. Final KYC and other institutional decisions apply their own evidence, screening, risk and approval rules.

What needs to be agreed before operational use?

Automation eligibility depends on commissioned authoritative checks and approved policy. Issuer-registry, NFC and biometric services require separate validation and commissioning; production certification is not established. Service scope, commercial terms, institutional configuration and data authority are agreed before activation.

Connected where selected

Related modules and capabilities are optional; access depends on selected services, configuration and permissions.

Build the right verify workflow for your institution.

Discuss your requirements