Welcome to AMLBot KYC
Welcome to AMLBot KYC Documentation
AMLBot KYC is a SaaS verification solution designed to be embedded into your product as part of your onboarding and compliance flow.
In practical terms, this is both:
- a verification infrastructure integrated into your app (via widget or hosted page)
- and a user-facing system you operate, where you configure forms, manage verification flows, review results, and control how your compliance process works
You can integrate it:
- as a web widget inside your application
- as a hosted verification page opened from your web or mobile app
Verification is performed through forms that you can customize — including data fields, verification steps, and flow logic — to match your product and compliance requirements.
All verification logic, processing, and decisioning are handled on AMLBot’s side, while you control the flow, user experience, and final actions.
The form integration itself is initialized via a simple API call.
See details here:
---
Integration Flow
The system follows a consistent and predictable flow:
- You create an applicant via API
- You provide the applicant with a verification interface (widget or hosted page)
- The applicant submits data and documents
- AMLBot processes the verification
- You receive the result via API or callback
This flow is the same regardless of whether you use embedded UI or a fully custom frontend.
---
Main Entities
Applicant
The applicant is the user being verified.
This can be:
- an individual (KYC)
- a company (KYB)
You create and manage applicants via API. Each applicant represents a single identity in your system.
---
Application
An application is a verification session linked to an applicant.
It represents a single attempt to complete verification and contains:
- submitted data
- uploaded documents
- verification results
An applicant can have multiple applications over time.
---
Verification
A verification is a set of checks performed within an application.
Depending on your configuration, it may include:
- identity document verification
- biometric checks (face match, liveness)
- address verification
- sanctions and PEP screening
- company verification (KYB)
Verifications are processed asynchronously. You trigger them via API and receive structured results once completed.
---
Interface (Widget / Hosted Page)
The interface is how the applicant interacts with the system.
You can:
- embed AMLBot as a widget inside your app
- redirect users to a hosted verification page
This is where applicants:
- enter their data
- upload documents
- complete verification steps
---
Results and Callbacks
Once verification is completed, AMLBot returns the result to your system.
You receive:
- application status
- verification outcomes
- structured data for decision-making
Results can be obtained:
- via API requests
- via callbacks (webhooks)
You decide how to use these results inside your product — approve, reject, or request additional data.
---
This documentation describes all available API methods, entities, and flows required to integrate AMLBot KYC into your system.