Re-activate a previously deactivated (soft-deleted) KYC user, setting is_active back to true. This only restores visibility: the user's kyc_status and verification history are untouched, so a reactivated user keeps whatever verification state it had before deactivation. The call is idempotent - reactivating an already-active user is a no-op success. Returns the updated user record.

Reactivated users reappear in the default GET /api/v1/kyc/users list (deactivated users are otherwise hidden unless include_inactive=true is passed).

Authentication & access

• Requires a client API token: Authorization: Bearer <token>.
• The caller must hold the kyc.users.write permission and have the OWNER role. Any other role is rejected with 403.

Path parameters

Response

200 OK with a UserResponse object. Key fields:

• id, email, full_name - user identity.
• kyc_status - one of none, pending, approved, rejected, on_hold (unchanged by this call).
• verification_mode - urbanpayx_kyc, urbanpayx_kyb, or external_attestation.
• external_verification_status - pending, verified, or rejected (relevant in external attestation mode).
• verification_source - none, urbanpayx, or external.
• is_active - true after a successful reactivation.
• created_at - when the user was created.

Error responses

Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.