Skip to main content
WEBHOOK
customer.status
{
  "event": {
    "id": "29ceb6c4-4849-4312-9b2b-5e8360647da0",
    "event_reference_id": "f9e1b162-8a05-4611-9e13-f38e0eb24a29",
    "type": "customer.status",
    "created_at": "2026-01-18T09:08:18.66348Z",
    "sandbox_mode": true
  },
  "data": {
    "customer_id": "f9e1b162-8a05-4611-9e13-f38e0eb24a29",
    "customer_status": "QUEUED",
    "email": "john.doe@acmecorp.com",
    "first_name": "John",
    "last_name": "Doe",
    "type": "INDIVIDUAL",
    "verification_type": "STANDARD"
  }
}

​
Customer Status Values

The status values in the payload depend on which API version was used to create the customer. V1 and V2 use different status names for the same underlying states — V1 has not been deprecated and both sets of statuses are active.
StatusV1 NameV2 NameDescription
Awaiting processingQUEUEDPROCESSINGVerification request sent to the work processor
Under reviewREVIEWINGREVIEWINGCustomer verification is currently under review
VerifiedAPPROVEDAPPROVEDSuccessfully verified and approved
Parties pendingASSOCIATED_PARTIES_REMAININGASSOCIATED_PARTIES_REMAININGAdditional associated parties need verification
PausedON_HOLDIN_COMPLIANCEVerification paused for compliance review
Action neededREINITIATEACTION_REQUIREDNew document upload required
RejectedREJECTEDREJECTEDCustomer verification rejected
ACTION_REQUIRED (V2) is also set by the customer.rfi webhook, which includes a structured payload describing exactly which documents or fields are missing or invalid.
All webhook requests include HMAC signatures for verification.

Body

application/json
​
event
object
​
data
object

Response

200

Webhook received successfully