Lotus Comply / API
Selectable serviceConnect the workflow. Keep the boundaries.
Give authorised systems scoped access to selected compliance operations. Connect workflows with institution-bound credentials, validated requests and safe retries, supported by an agreed commissioning process.
Who uses it
Institution technology teams, integration owners, security reviewers and operations leads.
Sample workspace
Connection · Sample sandbox
{
"institution": "A",
"scope": "selected_operations",
"record": "sample_record",
"delivery": "suspended"
}Inside API
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.
- 01
Agree the integration
Select operations, data authority and commissioning responsibilities.
- 02
Issue scoped access
Set credentials, expiry and applicable network restrictions.
- 03
Validate the request
Check permission, enabled service, payload and duplicate safeguards.
- 04
Return permitted result
Expose only the authorised record or workflow operation.
- 05
Observe & govern
Review logs and activate events only after approved commissioning.
Permitted operation
Credential, scope, enabled service and validation requirements are satisfied.
Rejected / restricted
Invalid data, expired access, disabled service or network restrictions prevent the request.
Delivery awaiting activation
Events and webhooks remain inactive until an approved receiver is commissioned.
API / scope
Start with the operations the institution needs.
Integration can address customer identity records, KYC, KYB, screening, risk, cases, monitoring and transactions within selected services. An API licence or credential does not unlock every product or provider.
- Selected workflow operations
- Agreed data authority
- Service-specific enabled access
API / credentials
Credentials belong to a defined institution.
Scoped credentials keep authorised access within an institution’s boundary. Expiration and revocation support controlled access changes; private credentials should never appear in public examples.
- Institution-scoped credentials
- Expiration and revocation
- Secure credential handling
API / network
Apply network restrictions where configured.
IP or network restrictions can add a configured access boundary. They are part of an agreed security configuration, configured to your institution’s requirements.
- Configured IP/network restrictions
- Security review of permitted access
- Operational acceptance before activation
API / validation
A request still has to satisfy the workflow.
Permissions, enabled services and payload validation govern operations. A successful transport response does not remove evidence, review or approval gates in the underlying compliance process.
- Authorised operation and record access
- Validated request information
- Independent institutional decision gates
API / retries
Avoid processing the same work twice.
Rate limits and duplicate-processing safeguards support predictable request handling. Integration owners must agree retry behavior and repeated-request identity rather than repeatedly creating the same customer or case.
- Applicable rate limits
- Repeated-request safeguards
- Agreed retry and error handling
API / events
Prepare signed delivery for your systems.
Signed events and webhooks are currently inactive pending approved commissioning. Agree receiving systems, secure credentials and delivery testing before operational activation.
- Approved receiver and delivery authority
- Signed-delivery commissioning and testing
- Activation follows operational approval
API / logs
Make operational issues observable.
Request and delivery logs help authorised teams understand validation failures, restricted access and processing outcomes. Logs are operational context, not proof of customer clearance or integration success everywhere.
- Request and outcome records
- Validation and permission failures
- Authorised operational review
API / commissioning
Activate only after the connections are agreed.
Mappings, provider access, data authority and operational acceptance must be established for each institution. Connections to banking, CRM, document and transaction systems are configured and validated for each institution.
- Institution-specific source mappings
- Testing and approval responsibilities
- Agreed source coverage and operational acceptance
Information in context
See what the team works with.
A sample api workspace shows the relevant fields and outstanding work.
Sample workspace
Connection · Sample sandbox
{
"institution": "A",
"scope": "selected_operations",
"record": "sample_record",
"delivery": "suspended"
}- Credential scope
- Selected KYC operations
- Institution boundary
- Institution A only
- Network restriction
- When configured
- Credential expiry
- Policy-defined
- Delivery status
- Inactive · awaiting commissioning
- Request result
- Sample permission check
In practice / Fintech integration
One selected workflow, with an explicit access boundary.
A fintech commissions selected KYC operations for Institution A. Invalid payloads and expired credentials are rejected; permitted operations keep independent review gates intact. Event delivery remains inactive until an approved receiver is commissioned.
What becomes clearer
Connect systems without losing clarity about what is enabled, who may access it and what remains uncommissioned.
Questions & answers
Before you choose API.
Is API a separately selectable service?
Yes. Practical operations, dependencies and commercial scope are agreed for the institution.
Does a credential unlock every service?
No. Institution, operation, permission and enabled-service restrictions apply.
Are webhooks live by default?
External connections and webhook delivery are currently inactive pending approved commissioning. Agree secure receivers, credentials, testing and operational acceptance before activation.
Is a banking or CRM connector included automatically?
No. Each connection needs institution-specific authority, mapping, testing and commissioning.
Can we test an integration before activation?
Approved bounded testing can be scoped; an unrestricted public sandbox is not promised.
Can API enable an embedded KYC widget?
An embedded experience is not established by the interface alone and requires separate verification.
What needs to be agreed before operational use?
External connections and signed event delivery are currently inactive pending approved commissioning. Data mappings, provider authority, secure receivers and testing are agreed for each institution. 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.