Start individual card KYC
Starts card KYC for an existing customer (customer_id) or a new one (customer). The response may include a link for the customer to complete verification. For business cards, use POST /api/cards/kyc/corporate.
Authorizations
Your workspace client id.
All calls must include four headers:
X-Auth-Client— your workspace client idX-Auth-Timestamp— Unix secondsX-Auth-Nonce— 16-byte random hexX-Auth-Signature— hex(HMAC-SHA256({client_id}:{timestamp}:{nonce}:{raw_body}, client_secret))
The playground computes the timestamp, nonce and signature for you.
Your sandbox client secret. The playground uses it to sign the request in your browser and removes it before the request is sent. Never send your client secret as a header in your own integration.
Body
Exactly one of customer_id or customer is required.
Must be true.
What the customer will use the card for.
100Free text; must not be below expected_monthly_volume when both are numbers.
50Defaults to prepaid.
prepaid, collateral Inline customer for KYC.
Existing customer. Provide this or customer.
Employment status of the customer.
employed, self_employed, unemployed, retired, student Expected monthly spend on the card.
50Back of the same document, same limits.
2796204Front of the ID document, base64 or data URI, at most 2 MiB decoded. Used by the raw-identity flow only.
2796204Code from GET /api/cards/kyc/occupations.
50Place of birth of the customer.
100Where the hosted page returns the customer; checked against an allowlist.
2048Reusable-KYC share token. Only for companies on the company reusable-KYC flow, where it is required.
4096Callback for the KYC outcome; defaults to the company webhooks.
2048Response
OK
Successful responses are wrapped in this envelope, and so are errors a handler answers itself (request body and field validation, some not-found and conflict cases, ORG_NOT_ACTIVE): success is false and error carries a code and message. Errors raised by authentication and by the services behind a handler are a Problem instead.
true on success
When the response was written.
The payload; its shape is given per operation. Omitted when there is none.
Human-readable summary; omitted when empty.
List metadata. Page lists set page, per_page, total and total_pages; offset and cursor lists set limit, offset, has_more and next_cursor. Zero and empty fields are omitted, and metadata is absent when nothing is set.
Set on error envelopes: the request's correlation id (req_ followed by a UUID), the same value as the X-Correlation-ID response header. Quote it to support.