Submit personal KYC
Full KYC payload for a Sender registered as individual. Calling this against an enterprise Sender returns 400.
Authorizations
API key for authentication
ES256 JWT signed by the private key registered to the API key above. Claims: sub (=API key), uri, nbf, iat, exp, and bodyHash (HMAC-SHA512 of uri + rawBody + nbf using a shared secret, base64).
Path Parameters
ID of the Sender
Body
Full KYC payload for a Sender registered as individual.
Full name (English)
As on the identity document
1 male, 2 female
1, 2 yyyy-MM-dd
ID card · Passport · Driver's license
11, 13, 14 yyyy-MM-dd
ISO 3166-1 alpha-2, document's issuing country
ISO 3166-1 alpha-2, country of residence
Including house/unit number
No '+', e.g. "86"
ISO 3166-1 alpha-2, comma-separated
ISO 3166-1 alpha-2, comma-separated
1 Salary · 2 Savings · 3 Investment return · 4 Other
1, 2, 3, 4 Monthly volume (USD): 1 0–49,999 · 2 50k–299,999 · 3 >300k
1, 2, 3 Partner's fixed code, e.g. "T1040001"
1 Remittance, 2 Currency exchange
1, 2 1 $10k–$100k · 2 $100k–$200k · 3 $200k+
1, 2, 3 1Required unless is_long_term is "1".
0, 1 Required when occupation_type is "T1040099".
Response
KYC submitted
enterprise, individual Starts pending. No client action moves it — resolves automatically once asynchronous partner KYC/KYB review completes.
pending, ready, rejected Present only when status is rejected.

