Skip to content
Lotus Comply

Lotus Comply / Industry solutions / Fintech & Payments

Bring customer and merchant compliance into your digital journey.

Connect user onboarding, merchant KYB and screening review around the same customer and business context. Give payment compliance teams clear follow-up workflows and institution-scoped API access, while keeping onboarding decisions with your authorised reviewers.

Fintech & Payments / connected context

Customer onboarding and merchant review

Institution websiteCustomer portal link
Customer chooses to continue
Digital channelCustomer portal entry
Customer consentNamed institution and frozen KYC share
Frozen authorised version
Compliance reviewUser KYC, merchant KYB and follow-up
Scoped APIService-specific operations and credentials
Integration awaiting approval
Conceptual diagram · permitted records and enabled services

The work your institution does

From first evidence to continuing review.

Each step has an owner, a requirement and a reason. Explore the work behind the institutional outcome.

01

Customer experience lead

Give users a clear onboarding entry point

Link users from your website or application to the customer portal, where they can prepare their profile and evidence. Customers can also start independently or respond to an invitation, giving your team a defined handoff into the compliance review.

  • Customer portal link from your digital channel
  • Independent profile preparation
  • Invitation-based application alternative
02

Customer & onboarding reviewer

Make customer consent part of the handoff

Customers choose the named institution, purpose and scope of a reusable KYC share. Your team receives a frozen evidence version to assess, with a clear basis for requesting additional information. Later profile changes do not rewrite the share already received.

  • Named recipient and onboarding purpose
  • Defined evidence scope and consent
  • Freshness review and additional document requests
03

Merchant onboarding analyst

Know the business behind each merchant

Use KYB to connect a merchant’s legal and trading names with registration documents, ownership and control. Review the relevant directors, signatories and beneficial owners alongside current personal evidence, so merchant onboarding addresses the business rather than just its storefront.

  • Merchant registration and business evidence
  • Holding companies and beneficial owners
  • Related-person KYC and signatory context
04

Compliance reviewer

Help reviewers resolve onboarding exceptions

Bring missing documents, screening candidates and risk questions into an evidence-led follow-up. Reviewers compare identity details, request clarification and record the reasons for their outcome. Required checks stay open when a source cannot respond.

  • Document clarification and replacement requests
  • Sanctions and PEP/PIP candidate assessment
  • Escalation and authorised onboarding decisions
05

Integration owner

Define API access around your compliance workflow

The API provides institution-bound credentials for specific operations across the services your team chooses. Agree the data fields and customer linkage, then test request validation, rate limits and safe retries so a channel connection supports the intended workflow.

  • Operation-specific scopes, expiry and revocation
  • Configured network restrictions
  • Request validation and duplicate-processing controls
06

Review officer & investigator

Plan oversight beyond the first onboarding review

Monitor supports periodic KYC, document expiry and material customer or merchant changes. Case Manager organises investigation work. Transaction Monitor is a separate service for transaction-rule reviews after an authorised data integration has been approved and commissioned.

  • User and merchant KYC refresh
  • Assigned investigation and approval history
  • Transaction source mapping and rule testing

Start to finish / Fintech & Payments

A clear route, including the exceptions.

  1. 01

    Choose the entry path

    Use a portal link, independent start or invitation.

  2. 02

    Prepare customer evidence

    Collect user KYC or merchant business documents.

  3. 03

    Confirm customer consent

    Name the recipient, purpose and scope of a profile share.

  4. 04

    Review the merchant

    Assess ownership, evidence and screening candidates.

  5. 05

    Resolve follow-up

    Request missing documents or investigate a concern.

  6. 06

    Record onboarding outcome

    Authorised reviewer records the institution’s decision.

  7. 07

    Approve the connection

    Test scoped API operations before activation.

Onboarding review complete

Required evidence and checks support the payment provider’s recorded decision.

User or merchant clarification

A document, ownership question or screening candidate needs further review.

Check or connection pending

Keep unresolved source checks and integration approval separate from onboarding clearance.

Example process. Authority, selected services, mandatory evidence and required-source availability determine the permitted next step.

Inside the workspace

Records, follow-up and review history.

A sample institutional record shows the relevant evidence and unresolved work.

Lotus Comply / Fintech & Payments
Sample record

Customer onboarding and merchant review

Sample review context
Journey
Customer portal link
Recipient
Orbit Payments
Share purpose
KYC evidence for account onboarding
Connection state
Inactive · awaiting integration approval
Example workspace · Sample data

How it works in practice

Orbit Payments reviews a merchant’s first application

  1. 01

    Inputs

    Orbit Payments directs a merchant to the customer portal. The director prepares personal evidence, and the company supplies its registration documents and ownership details.

  2. 02

    Controls & actions

    The merchant analyst checks the director’s current KYC and requests a missing company document. Separately, the integration owner defines the API operations and customer mapping needed for the planned channel connection.

  3. 03

    Outcome & exceptions

    Orbit records the merchant’s compliance outcome after the evidence and screening review is complete. The API connection has its own testing and operational approval, keeping merchant acceptance separate from integration readiness.

Questions & answers

Before you choose Fintech & Payments.

How can users enter the onboarding workflow from our app?

Your app or website can link to the customer portal. Users can also prepare a profile independently or complete an invitation-based application. Your team reviews the resulting evidence and records its own onboarding decision.

What can our integration team access through the API?

Credentials are bound to your institution and scoped to agreed operations for your chosen services. Access does not automatically extend to every product or to another institution’s records.

When can transaction monitoring be added?

Transaction Monitor requires an authorised transaction source, agreed customer linkage and mappings, tested rules and operational approval. It is separate from Monitor, which manages ongoing KYC review and evidence refresh.

Build the compliance journey your institution needs.

Discuss your requirements