UPP Docs
Compliance

Verification concluded

Sent when the verification becomes approved or rejected. data has the same shape as GET /customer-verifications/{verificationId} and contains no identity data.

Not sent when the provider asks the customer to resubmit (the verification stays pending).

Request Body

application/json
  1. body
id*string

Event ID (starts with evt_), unchanged across retries

type*string
created_at*string

When the event happened

Formatdate-time
data*

Response Body

Received by the merchant; any 2xx is a success

Example Requests
POST/customer_verification.status_changed
Request Body
application/json
{  "id": "evt_01m5earqne93w8xvs05exdabnx",  "type": "customer_verification.status_changed",  "created_at": "2026-10-21T04:16:02.000000Z",  "data": {    "id": "cvr_01m5earq6ehhk7972htrkvtwx3",    "customer_id": "cus_01m5ead2k7knsqfa65tpt1an6r",    "usage": "test",    "status": "approved",    "rejection_reason": null,    "verified_at": "2026-10-21T04:16:02.000000Z",    "created_at": "2026-10-21T04:16:02.000000Z",    "updated_at": "2026-10-21T04:16:02.000000Z"  }}