Reset a user's KYC

POST/kyc/checks/{transactionUserId}/reset

kyc:write reset_user_kycDestructiveDeprecatedSunset 2027-06-30

Resets the transaction user's KYC: the stored check rows are soft-deleted, and the user's Sumsub applicant is reset when one exists. The id is resolved org-scoped → a cross-org / unknown id 404s leak-safely. Deprecated: withdrawn on 2027-06-30. POST /kyc-checks/{id}/actions/reset replaces it, keyed by the investor id; every answer carries a Link header with rel="successor-version".

Path parameters

transactionUserIdstring (uuid)Required#
The deals-service transaction user id.

Responses

200

The KYC was reset.

KycResetEnvelope

{
  "data": {
    "transaction_user_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
    "applicant_id": "5f6a7b8c9d0e4f1a8b2c3d4e",
    "reset": true
  }
}

401

Authentication failed. error.code is one of invalid_token, expired, revoked.

Error

403

Authorization failed. error.code is one of org_disabled, ip_blocked, missing_scope, scope_disabled, user_disabled.

Error

404

Resource not found (error.code = not_found).

Error

429

Rate limit exceeded (error.code = rate_limited).

Error

502

An upstream dependency (e.g. Sumsub) was unavailable (error.code = upstream_error).

Error

503

An upstream dependency (e.g. Sumsub) could not be reached or timed out (error.code = upstream_unavailable). Retry after the Retry-After delay.

Error

Examples

curl -X POST https://your-org-domain/kong/core/api/v2/kyc/checks/{transactionUserId}/reset\
  -H "Authorization: Bearer $HELM_API_KEY"\
  -H "Content-Type: application/json"