SimpleKYC connector — verification lifecycle
A KYB verification is the connector's stateful resource. This page describes how it progresses and how SimpleKYC statuses map to Ark's. How each step is implemented is in the architecture; how to call each one is in endpoints.
End-to-end process
The connector holds no status of its own — every status and report is read live from SimpleKYC. The
stored mapping's STATUS column is set once at creation and is not used for reads
(see the connector notes).
Status mapping
POST /v1/kyx, GET /v1/kyx/{id}, and the document upload all return a verificationStatus
normalised from SimpleKYC's overallStatus:
| SimpleKYC status | Ark status |
|---|---|
verified, complete | VERIFIED |
in_progress, pending | IN_PROGRESS |
incomplete | INCOMPLETE |
under_review | UNDER_REVIEW |
declined | DECLINED |
error, errored | ERRORED |
failed | FAILED |
An unrecognised SimpleKYC status is not mapped — it surfaces as a 500
(see the connector notes).