Contact Details Verification

PCI Booking allows you to verify that the email address and phone number you have on file for a property are valid and reachable.

There are two common use cases for this feature:

  • Validating newly submitted details — When a property submits contact details directly (for example, via a self-service portal), you can trigger a verification to confirm the details are correct before storing them.
  • Periodic re-verification — Contact details can go stale without notice. By periodically re-verifying stored details, you can proactively detect outdated information and prompt the property to update their records.

How It Works

Contact Details Verification is a two-party process. You initiate it via the API; the property completes it through a hosted verification page that PCI Booking provides.

  1. You call Create a Verification with the property's email address and phone number.
  2. PCI Booking emails the property a link to a hosted verification page.
  3. The property opens the page, where they can see the last four digits of the phone number on file.
  4. The property requests a one-time passcode (OTP), which PCI Booking sends to their phone via SMS or voice call.
  5. The property enters the OTP on the verification page.
  6. The session reaches a terminal state: Verified if the OTP was correct, Failed if it was not, or Expired if the session timed out before the property acted.
  7. If you provided a callbackUrl, PCI Booking POSTs the result to your endpoint. You can also poll for the outcome using Get Verification Status.

📘

Both email and phone are used

The email address is how the property receives the verification link. The phone number is what gets confirmed via OTP. To run a complete verification, provide both.

Session Lifecycle

A verification session progresses through the following statuses:

StatusDescription
PendingThe session was created and the verification email has been sent. Waiting for the property to act.
OtpSentThe property opened the verification page and requested an OTP.
VerifiedThe property entered the correct OTP. The phone number is confirmed. Terminal state.
FailedThe OTP was incorrect or the maximum number of attempts was exceeded. Terminal state.
ExpiredThe session TTL elapsed before the property completed the verification. Terminal state.

📘

Use a callback instead of polling

We recommend supplying a callbackUrl when creating a verification. PCI Booking will POST the result to your endpoint the moment the session reaches a terminal state, so you do not need to repeatedly call Get Verification Status.

API Methods

MethodDescription
Create a VerificationInitiate a new verification session and send the verification email to the property.
Get Verification StatusPoll the current status of a verification session.
Get Verification ResultsRetrieve the full outcome once the session has reached a terminal state.
Receive Result NotificationReceive a callback POST when a session completes.