Skip to content
Lotus Comply

Lotus Comply / KYC

Selectable service

Customer-led onboarding. Institution-led decisions.

Let individuals start their own profile, respond to an invitation or follow your portal link. Bring their information, private evidence and authorised share into a structured, independent review.

Who uses it

Individual customers, onboarding officers, compliance reviewers and independent approvers.

Lotus Comply / KYC

Sample workspace

Alex M. · Individual profile

Evidence requested
1Personal & contactSection saved
2Address evidenceUpdate requested
3DeclarationsReview pending
4Authorised shareBank A · V02 frozen
Sample workspace data

Inside KYC

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

    Start a profile

    Customer self-start, institution portal link or single-use invitation.

  2. 02

    Save & supply

    Complete sections and upload private supporting evidence.

  3. 03

    Check readiness

    Validate required information and resolve missing evidence.

  4. 04

    Authorise a share

    Choose the institution, purpose and scope; freeze the version.

  5. 05

    Review independently

    Receiving institution checks its gates and records its own decision.

Ready for review

Required information and authorised scope are present. Readiness is not KYC approval.

More evidence needed

Stale address evidence or an unanswered declaration routes back to the customer.

Decision held

Missing required screening, risk or approval gates prevent an institutional decision.

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

KYC / entry

Three ways in. No invitation required.

An individual can sign up in the customer portal and create or update a profile independently. Institutions can link customers to that portal or issue a secure single-use invitation for a specific application.

  • Independent customer start
  • Institution website link to the portal
  • Secure invitation for a specific application
02

KYC / profile

Capture the relationship, not just a name.

Structured sections collect personal, contact and address details, occupation, intended product purpose, source-of-funds and source-of-wealth narratives, and relevant PEP declarations. Requirements depend on the institution and applicable country pack.

  • Personal and contact information
  • Occupation, product purpose and financial narratives
  • Declarations and private supporting documents
03

KYC / readiness

Save in sections. Resolve missing requirements.

Customers can save sections while server-side validation checks the information received. A readiness view identifies incomplete requirements before sharing; complete fields are not the same thing as approved evidence.

  • Section-by-section progress
  • Required-field and evidence validation
  • Specific requests rather than a generic rejection
05

KYC / review

The institution reviews its own application.

Authorised reviewers assess evidence and request more information where needed. Screening and risk are added only when separately selected and enabled; customer readiness or another institution’s decision cannot bypass review.

  • Evidence requests and reviewer reasons
  • Optional enabled screening and risk checks
  • Role-controlled review and independent approval
06

KYC / gates

Hard requirements stay hard.

A reviewer’s recommendation must satisfy mandatory evidence, policy and approval gates. An administrative role is not a shortcut to decision authority; missing checks remain outstanding even when other parts of the profile are complete.

  • Country-pack and product-specific requirements
  • Separate reviewer and approver responsibilities
  • No automatic risky-customer approval
07

KYC / updates

Keep a profile current. Preserve the shared past.

A customer can update their personal profile and separately authorise a later share. Existing submitted versions remain frozen, so an institution can explain exactly which information informed a historical review.

  • Customer-owned current profile
  • New permission for a later shared version
  • Historical institutional assessments stay unchanged
08

KYC / withdrawal

Future access and lawful retention are different.

Removing consent limits further access through the grant. It does not automatically erase institution-held compliance records that must be retained lawfully, and it does not transfer one institution’s approval to another.

  • Limit future access through revoked permission
  • Separate retained institutional records
  • Independent suitability and freshness checks

Information in context

See what the team works with.

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

Lotus Comply / KYC

Sample workspace

Alex M. · Individual profile

Evidence requested
1Personal & contactSection saved
2Address evidenceUpdate requested
3DeclarationsReview pending
4Authorised shareBank A · V02 frozen
Profile sections
Personal · contact · address
Occupation
Self-employed
Product purpose
Personal account
Funds / wealth
Narratives requested
Sharing permission
Bank A · onboarding only
Shared version
V02 · frozen
Sample workspace data

In practice / Insurance onboarding

The customer starts before the insurer sends anything.

A policyholder creates a profile independently, adds evidence and chooses Insurer B. The insurer receives a frozen authorised version, requests an updated address document and makes its own compliance decision.

What becomes clearer

Give customers continuity while preserving each institution’s evidence standards and decision authority.

Questions & answers

Before you choose KYC.

Must a customer wait for an invitation?

No. They can create and maintain a customer-owned profile in the portal and choose a participating institution to share with.

Can our website direct customers to onboarding?

Yes, through a link to the customer portal. True embedded or white-label delivery needs separate integration validation.

Are the three entry paths three separate onboarding engines?

No. Direct start and institution portal links both enter the customer portal; invitation-backed applications are an additional workflow.

Does a shared profile approve KYC?

No. The recipient independently applies its requirements and decides.

Can institutions request more evidence?

Yes. Suitability, freshness and policy requirements can require additional information.

Do profile updates rewrite an earlier submission?

No. Historic authorised shares remain point-in-time versions; later sharing is a separately authorised step.

What needs to be agreed before operational use?

Customers can start independently, follow a portal link or complete an invitation. An embedded journey requires separate agreement; each institution reviews evidence and may request updates. 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 kyc workflow for your institution.

Discuss your requirements