Solutions · Fintech
Add the checks you need to your product flow.
Assess your KYC, AML and blockchain screening needs separately. Build your integration plan by defining the API scope and operational requirements.
Scope approach
Start with a small scope, grow with the requirement.
First decide which check is needed at which user step. Reassess the control scope when you add a new product, market or transaction type.
- Start with a single check
For example, name screening at account opening. Result fields and the review step connect to the product flow.
- New market or product
The control scope is reassessed; document, country and data requirements may change.
- Additional check
If needed, identity verification or wallet assessment is added as a separate step.
For the technical team
Clear outputs for the technical team.
Design not only the successful response but also the review and error states.
Request
Required data fields.
{
"subject": { "type": "person", "name": "…" },
"reference": "customer-2481"
}Response
Result and review context.
{
"status": "review_required",
"matches": [ ],
"decision": null
}Error
Retry and user-guidance conditions.
{
"error": {
"type": "validation_error",
"retryable": false
}
}Cost and responsibility
See cost and responsibilities together.
Make plan, consumption and service terms part of the integration decision. Adding checks to software does not remove the institution's own assessment responsibility.
Frequently asked questions
For fintech teams.
How soon can we go live?
Timing depends on product scope, your systems and assessment requirements. No fixed go-live time is given before the scope is clear.
Is the same flow enough when entering a new market?
New market and product requirements must be assessed separately.
Let's define the integration scope together.
Let's talk about which check is needed at which user step and what the API requires.