On this page
Less scattered information when deciding what comes next
Self-declared form data is not always sufficient for an operation that needs to identify a person. Manual checks spread across email and conversations make it harder to track unresolved cases and associate a result with the correct account.
Contrato.Cloud KYC organizes an identification journey linked to your operation’s process. The person opens a link in a compatible browser; your system tracks the result and applies its own continuation rules.
Choose where identification adds value
- Fintech: onboarding, account opening and financing proposals, with credit decisions retained by the institution.
- Telecom: contracting, sensitive changes and account ownership transfer.
- Ecommerce: seller onboarding and selected orders requiring additional identification.
Documents, biometrics and liveness participate according to the configured journey. Verifying a person does not replace company validation, representation checks or payment authentication.
Integrate without losing context
Your backend creates a transaction, stores its relationship with the application and hands over the returned journey. Authenticated webhooks and current-state reads support tracking. Pending, rejected, expired and manual-review cases need defined paths without automatically releasing an incomplete step.
Records help reconstruct the process and support internal assessment. A result does not promise elimination of fraud or automatic compliance; workflow design must account for your operational requirements.
Explore developer documentation
Formalize the agreement too
When onboarding leads to contracting, assess document signing as a complementary layer. Identification and formalization can share process context while retaining separate requirements and results.