Compliance Details

Celar enforces compliance at both the customer (KYC) and transaction (KYT) levels.
This page explains possible compliance outcomes, required documents, PSP responsibilities, and how uploads are managed.

1. States & Verdicts

Compliance checks can result in the following outcomes:

• allow → Passed all checks.
• failed → Blocked transactions due to compliance rules.

2. KYC Document Requirements

Celar enforces different requirements for individuals and businesses.
These documents are always uploaded via the Dashboard, never directly via API.

Individual Customers

Must provide one of:

• id_card
• passport
• driver_license

Business Customers

Must provide:

• incorporation_certificate

note

Once uploaded, Celar securely stores these files, generates a URL, and attaches it to the customer record. When you fetch the customer via API, these URLs appear in verification_document or incorporation_certificate.

3. PSP Responsibilities

• You must create and maintain accurate customer records (via API or Dashboard).
• If customers are added via API or CSV bulk upload, you are still responsible for logging into the dashboard and uploading their compliance documents individually.
• Compliance uploads are mandatory — pay-ins and payouts may fail if documents are missing or invalid.

4. Compliance Workflow

The typical compliance workflow in Celar:

1. Create a customer (via API or Dashboard).
2. Upload required documents via Dashboard.
3. Celar runs KYC checks on the documents → result in allow or kyc_failed.
4. When a pay-in occurs, Celar runs KYT checks → result in allow or failed.
5. Results are available through compliance endpoints.

This makes Celar secure, auditable, and regulator-ready.