collection_url.
Parameter overview
| Parameter | Description |
|---|---|
message | Human-readable description of the event. |
event_type | Event type identifier (e.g. customer.status_changed). |
customer_id | Unique ID of the customer. |
customer_email | The customer’s email address. |
old_status | The customer’s previous verification status. |
new_status | The customer’s new verification status. |
comment | Optional comment explaining the status change (e.g. rejection reason). |
updated_at | ISO 8601 timestamp of when the status changed. |
event_id | Unique identifier for this webhook event. |
type | Always customer for customer events. |
Event types
customer.created
Sent when a new customer is created for your business.customer.verified
Sent when a customer’s KYC verification is approved. The customer can now be used for Virtual Bank Account creation and other operations that require a verified customer.customer.rejected
Sent when a customer’s KYC verification is rejected. Check thecomment field for the rejection reason. Common rejection reasons include unclear or illegible document images, unsupported document types (such as national ID cards), expired documents, or fraudulent submissions.
Example payload
Rejected example
Possible statuses
| Status | Description |
|---|---|
PENDING | Customer documents are under review. Verification is not instant — it typically completes within a few minutes, but can take up to 2 hours if additional screening is required. Do not escalate before 2 hours. Contact the operations team only if pending for 5 hours or more. |
VERIFIED | Customer KYC has been approved. The customer can now be used for payouts and Virtual Bank Account creation. |
REJECTED | Customer KYC has been rejected. Check the comment field for the reason. |

