Skip to main content

Compliance Details

Celar enforces compliance at both the customer (KYC/KYB) and transaction (KYT) levels. This page explains possible compliance outcomes, required documents, PSP responsibilities, and the broader rules around verification.

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 can be submitted through the API workflow or through the Dashboard path, depending on how your team operates. The operational steps live in Compliance Workflows & Endpoints.

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 and attaches internal file references to the customer record. When you fetch the customer via API, these values appear in fields such as verification_document or incorporation_certificate.

3. PSP Responsibilities​

  • You must create and maintain accurate customer records via API or Dashboard.
  • You must collect and maintain the required KYC/KYB documents for each customer type.
  • Compliance uploads are mandatory and payments may fail if documents are missing or invalid.
  • If customer details change, Celar may re-run verification and move the customer back into a review state.

4. Compliance Workflow​

The typical compliance workflow in Celar:

  1. Create a customer via API or Dashboard.
  2. Upload required documents through the API workflow or Dashboard path.
  3. Run identity verification and customer KYC/KYB review.
  4. When a pay-in occurs, Celar runs KYT checks.
  5. Results and summaries are available through the compliance docs and endpoints.

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