If a callbackUrl was provided when creating the verification, PCI Booking will send a POST request to that URL when the session reaches a terminal state (Verified, Failed, or Expired).
Your endpoint must be publicly accessible and should return a 2xx HTTP status code to acknowledge receipt.
š Callback payload mirrors the status responseThe body of the callback POST uses the same structure as the Get Verification Status response.
š MetadataThe
metadatafield in the callback payload will contain the value provided in the original Create request, making it easy to correlate the notification with your own internal records.
š Callback delivery is best-effortIf your endpoint is unreachable or returns a non-2xx status, the failure is logged but does not affect the verification outcome. We recommend using Get Verification Status or Get Verification Results as a fallback if your endpoint does not receive a notification.
Callback Payload
| Field | Type | Description |
|---|---|---|
verifyId | string | The unique ID of the verification session. |
status | string | The terminal status. Possible values: Verified, Failed, Expired. |
completedAt | datetime | The UTC datetime at which the session reached its terminal status. |
metadata | string | The metadata string provided in the original request. Returns null if not provided. |
{
"verifyId": "xLoat3F385vvFRbgI2usOeuXKXQoB8kv",
"status": "Verified",
"completedAt": "2026-03-15T18:47:10Z",
"metadata": "MY-REFERENCE_098"
}
