After creating a user_handle with /register, begin the KYC verification process with this endpoint. Check results with /get_verification or /get_verifications. This endpoint supports both ECDSA and JWT, but we recommend using JWT. this endpoint is not SDK-supported.

Note that if you call /kyc and you get a status other than passed or failed (like documents_required) the verification will expire after 30 days if it's not updated. Verification status will transition to failed and this will count against the max (2 per entity) number of attempts.

🚧

Advanced KYC ONLY

Only use this endpoint if you are utilizing the new Advanced KYC. Otherwise, use /request_kyc.

Request

Authorization / Authentication

Apps using Access Token Authorization

Use a valid access token in an Authorization: Bearer request header.

See Auth Token Overview for more details.

NOTE: Though we recommend using JWT, you can use this endpoint with ECDSA.

POST /0.2/kyc HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
Authorization: Bearer [GENERATED JWT TOKEN HERE]

{
  "header": {
    "created": 1234567890, //required
    "app_handle": "<your app_handle>", //required
    "user_handle":"user_handle", //required
    "version": "0.2", 
    "reference": "<your unique id>"
  }, 
  "flow": <uuid of KYC flow>, //required
}

***

HTTP/1.1 202 OK

{
  "success": True,
  "reference": reference_id,
  "message": "KYC successfully requested using flow <uuid>",
  "verification_ids": [{
      "entity": <user_handle>, 
      "verification_id": <verification_uuid>
    }],
  "flow_requested": <uuid of KYCFlow>,
  "checks_requested": [
  <list of strings, for example address, birthdate, etc>
  ]
}

Request Attributes

Responses