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.
Customer onboarding and merchant review
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.
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
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
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
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
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.
- 01
Choose the entry path
Use a portal link, independent start or invitation.
- 02
Prepare customer evidence
Collect user KYC or merchant business documents.
- 03
Confirm customer consent
Name the recipient, purpose and scope of a profile share.
- 04
Review the merchant
Assess ownership, evidence and screening candidates.
- 05
Resolve follow-up
Request missing documents or investigate a concern.
- 06
Record onboarding outcome
Authorised reviewer records the institution’s decision.
- 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.
Inside the workspace
Records, follow-up and review history.
A sample institutional record shows the relevant evidence and unresolved work.
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
How it works in practice
Orbit Payments reviews a merchant’s first application
- 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.
- 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.
- 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.
Shape your service mix
Select what your programme needs.
Choose commercial services independently to match your programme. People 360, Business 360 and Reusable KYC are shared platform capabilities. Agree service scope, commercial terms and any required source connections for your institution.
Customer-led profiles and independent onboarding decisions.
Business evidence, ownership layers and associated people.
Identity evidence, enabled checks and exception handling.
Authorised-source screening, candidate review and dispositions.
Periodic reviews, expiring evidence and customer changes.
Assignment, evidence, escalation and investigation history.
Scoped access to selected compliance workflows.
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.