KYC Events - Finogates API Documentation

Events

Event	Sent when	Additional fields
`user_kyc.applied`	The user submitted identity verification.	`status`, `verified_fields`
`user_kyc.in_review`	Verification is under review.	`status`
`user_kyc.approved`	Verification is approved.	—
`user_kyc.semi_approved`	Verification is moved to semi-approved.	`status` (`semi_approved`), `previous_status`
`user_kyc.rejected`	Verification is rejected.	`reject_reason`
`user_kyc.reopened`	Verification is reopened for the user to redo.	`reopen_reason`, `previous_status`, `reopen_count`
`user_kyc.required`	A payment needs the user to complete KYC first.	`intent_id` or `payment_id`, `status` (`required`), `note`
`user_kyc.deleted`	The verification record is deleted.	`delete_reason`

Example

{
  "id": "1c2d3e4f-5a6b-4c7d-8e9f-0a1b2c3d4e5f",
  "type": "user_kyc.rejected",
  "event_type": "user_kyc.rejected",
  "created_at": "2026-10-13T11:04:52.118904+00:00",
  "data": {
    "kyc_record_id": "3e4f5a6b-7c8d-4e9f-a0b1-c2d3e4f5a6b7",
    "user_id": "b3a9b622-cc63-4d3c-aad6-2d8e29e6f9d4",
    "reject_reason": "Document is unreadable"
  }
}

Data Fields

string

The user being verified.

string

The verification record. Status changes reported during verification (applied, in_review, and some approved/rejected events) send it as check_id.

integer | string

On applied, in_review and provider-reported approved/rejected: 1 pending, 2 in review, 3 approved, 4 rejected, 5 semi-approved, repeated in status_code. semi_approved and required send a string.

​Events

​Example

​Data Fields

Events

Example

Data Fields