KYC event types
Identity verification: identity.verification.completed
Youverify delivers this event when an identity check against a government-issued ID — such as a BVN, NIN, or national ID — finishes processing. The data object contains the full verified record, including all validated fields.
Example payload
Identity verification payload fields
string
Always
identity.verification.completed for this event type.string
Result of the verification. See status values below.
string
The ID type checked, for example
nin, bvn, drivers_license, passport.string
ISO 3166-1 alpha-2 country code, for example
NG.boolean
true if all submitted fields matched the authoritative record.boolean
true if every individual field validation passed.object
Address verification: address.verification.completed
Youverify fires this event when a physical or digital address verification task is completed. The data object includes the full agent report, geo-coordinates, property details, and images.
Example payload (individual)
Address verification payload fields
string
Agent-reported outcome. Common values:
VERIFIED, NOT_VERIFIED, UNABLE_TO_VERIFY.string
Workflow status of the report, for example
completed, awaiting_qa.boolean
true if the agent flagged something notable at the address during the visit.string
URL to download the full PDF address verification report.
string
Verification subject type:
individual, guarantor, or business.Verification status values
Thedata.status field on identity events can hold the following values:
When
status is pending, do not treat the check as failed. Youverify will deliver a follow-up identity.verification.completed webhook once the upstream provider responds.Common use cases
Unlock account features on verification
Unlock account features on verification
Listen for
identity.verification.completed with allValidationPassed: true to automatically promote a user to a verified tier in your platform — enabling higher transaction limits, wallet top-ups, or other gated features.Send real-time notifications to your user
Send real-time notifications to your user
On receipt of either KYC event, trigger an in-app notification or email to your user informing them whether their verification succeeded or failed.
Update internal records
Update internal records
Persist the
verificationId, status, and validated fields from the webhook payload to your own database so you have an auditable record of every KYC outcome alongside your user record.Handle pending checks gracefully
Handle pending checks gracefully
If a user’s identity check returns
status: pending, show them an “in progress” state in your UI and flip it to verified or failed once the follow-up webhook arrives.