Receive Result Notification

Contact Verification Guide

How the email + OTP verification flow works end-to-end

If a callbackUrl was provided when creating the verification, PCI Booking sends 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.

The callback payload uses the same structure as the Get Verification Status response.

The metadata field contains the value provided in the original Create request, making it easy to correlate the notification with your internal records.

Callback delivery is best-effort. If your endpoint is unreachable or returns a non-2xx status, the failure is logged but does not affect the verification outcome. Use Get Verification Status or Get Verification Results as a fallback.

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. `null` if not provided.

{
    "verifyId": "xLoat3F385vvFRbgI2usOeuXKXQoB8kv",
    "status": "Verified",
    "completedAt": "2026-03-15T18:47:10Z",
    "metadata": "MY-REFERENCE_098"
}

Get Verification Results Network Tokenize a Card

Start Here

Authentication & General

Capture Cards

Manage Tokens

Use Tokens

Additional Functions

Payments Library

Receive Result Notification

Contact Verification Guide

Callback Payload

Contact Verification Guide

​Callback Payload

Callback Payload