import { Aside } from '@astrojs/starlight/components';

Each integration connection has a verification timing setting. It decides when an applicant can start verification for a reservation, and when that verification is due. This page explains each setting, the link each reservation gets, and what the applicant, your team, and your connected system see at each step.

## The default timing

By default, verification opens as soon as a reservation reaches Checktiv, and it is due at the deadline of the first verification that starts for it. The connection's [default workflow](/guides/integrations#default-workflow) sets that deadline. So with the default timing, the verification starts as soon as the reservation qualifies, and lasts as long as the workflow allows.

A reservation "reaches Checktiv" when the integration first reads it. For a connection that receives each change as it happens, that is usually when the reservation is booked. For a reservation that existed before you connected, it is the first time the integration reads it.

## Choose a different timing

You set the timing in the **Verification timing** section of the connection, when you connect a system or when you **Edit** a connection under **Dashboard → Integrations**. The console uses the same words for every connected system, so it says **record** for the reservation and **start date** for the check-in.

**Verification opens** is one of:

- **When the record arrives**: as soon as the reservation reaches Checktiv.
- **Days before the start date**: 1 to 365 days before check-in.

**Verification due** is one of:

- **The first verification's deadline (default)**: the default timing above.
- **Days after the record arrives**: 1 to 365 days after the reservation reaches Checktiv.
- **Hours before the start date**: 0 to 720 hours before check-in. 0 hours is the same as at check-in.
- **At the start date**: at check-in.

While the due time is the default, verification opens when the reservation arrives. To open it later, choose a different due time first.

These rules apply to every timing:

- **At least 24 hours.** An applicant gets at least 24 hours after a reservation arrives, unless check-in is sooner. A due time never falls after a check-in that is still ahead. A reservation that arrives after its check-in gets 24 hours.
- **Verification always opens before it is due.** If a timing would open verification at or after its due time, verification opens 24 hours before the due time instead, or when the reservation arrives if that is later.
- **A reservation with no check-in uses the default timing.** The verification shows why in the console.
- **A strict timing can charge for later cancellations.** An early or strict timing verifies applicants whose reservations are canceled later, and each of those verifications is charged.
- **A change applies to reservations that are not finished.** Saving a new timing updates every reservation that is not finished. A reservation whose check-in has passed keeps its due time; [reopen it](#after-the-due-time) to give the applicant more time. A reservation you reopened keeps the due time you set, and a canceled one is not changed. A verification that has not started is canceled and replaced when the new timing opens verification later.

## How the check-in time is read

A timing measured from check-in uses the check-in time the connected system sends:

- **Track** and **Guesty** send an exact check-in time, so the integration uses it as sent.
- **Mews** sends the stay's scheduled start as an exact time in UTC, so the integration uses it as sent.
- **Hostaway** sends a check-in date without a time. The integration uses the start of that day in the listing's time zone, or in UTC when the listing has no time zone. A due time in hours before check-in can therefore fall up to a day early.
- **Streamline** sends stay dates without a time or a time zone. The integration uses the start of the check-in date in UTC, which is the evening before in the Americas.

For Hostaway and Streamline, which send only a date, a due time never falls after the end of the check-in date.

A day offset is a fixed span of 24 hours. Across a daylight saving time change, a due time set in days can fall an hour earlier or later on the local clock than the check-in.

## The reservation's verification link

Each reservation gets one verification link as soon as it qualifies, which is before any verification starts. The integration writes it to the reservation; each integration guide names the field or note. The link stays the same for the whole window:

- Before verification opens, the link shows the date it opens.
- While verification is open, the link starts the verification, or continues the one in progress.
- After the due time, the link says that the deadline has passed.

The link changes in three cases:

- **The reservation is canceled.** The link stops working. Canceling the reservation's verification through the API, or by an [AI assistant you connected](/guides/integrations/connect-ai-assistants), also cancels the reservation, and that is final.
- **A reservation canceled in the connected system is restored there.** The reservation gets a new link.
- **The reservation's guest changes.** The reservation gets a new link, and the previous guest's link stops working. What counts as a change of guest depends on the integration: a different contact in Track, a different guest in Guesty, a different guest name or email in Hostaway or Streamline, and a different owner of the reservation in Mews. In Hostaway and Streamline, correcting the spelling of the guest's name or email also counts as a change of guest; a change of capitalization or spacing alone does not. In Mews, a new name or email on the same owner is not a change of guest. If the previous guest has not started, their verification is canceled and the new guest starts a new one.

If a verification lapses before the applicant starts any paid check, the applicant can start again from the same link while verification is open. The link never reopens a finished verification.

## When the verification starts

When the verification starts depends on the timing and on the connection's **Send the verification invite** setting:

- **Verification opens when the reservation arrives, with invites on:** the verification starts as soon as the reservation qualifies, and the applicant receives the invite at once.
- **Verification opens when the reservation arrives, with invites off:** the verification starts at once when one verification can last until the due time. Otherwise it starts when the applicant opens the link.
- **Verification opens later, with invites on:** the verification starts on the day it opens, and the applicant receives the invite then.
- **Verification opens later, with invites off:** the verification starts when the applicant opens the link on or after the day it opens.

Turning **Send the verification invite** off does not hold invites for later: a reservation whose verification opens while the setting is off gets no invite when you turn it back on. Its applicant can still start from the link already written to the reservation.

When the applicant starts it from the link, the integration reads the reservation from the connected system first. This usually takes under a minute, and the page shows **Getting things ready** in the meantime. If the connected system cannot be reached, the page asks the applicant to try again in a few minutes, and the console lists the reservation as one that needs attention.

Routing rules are checked again when a verification is about to start. If a **Skip verification** rule matches the reservation then, for example a rule you added after the reservation got its link, no verification starts. The link then shows "You can't continue from this link". The connection lists the reservation under **Records that need attention**, with the reason "The record no longer matches this connection's routing rules or status filter. Update it there, then reopen." To verify the applicant, change the reservation or the rule, then select **Reopen verification**.

When your organization has [automatic reminders](/guides/verification/send-an-invite#automatic-reminders) turned on, an invited applicant from any connection also receives one extra reminder 24 hours before their verification's deadline, unless a message already reached them in that final day.

## What the applicant sees

The link shows your organization's name and branding, including before any verification exists for the reservation. Depending on the state of the reservation, the applicant sees one of these pages:

| State                   | The applicant sees                                                                                                                           |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Not open yet            | "Your onboarding with your organization opens soon", with the date they can start.                                                           |
| Open                    | "Your onboarding with your organization", with a **Get started** button.                                                                     |
| Starting                | "Getting things ready", while the integration reads the reservation. If it takes longer than usual, a request to try again in a few minutes. |
| Temporarily unavailable | "Onboarding is temporarily unavailable", with a request to try again in a few minutes.                                                       |
| Blocked                 | "You can't continue from this link", with a request to ask you to reopen their onboarding.                                                   |
| Past the due time       | "The deadline to complete onboarding has passed", with a request to ask you to reopen their onboarding.                                      |
| Finished                | Where their verification stands, as on the page they saw when they finished.                                                                 |

Once a verification is in progress, the link opens it, the same as any other verification link.

## What the connected system shows

The status the integration writes to the reservation includes three states that come before or after a verification:

- **Not yet open**: verification for the reservation has not opened.
- **Not started**: verification is open, and no verification is in progress for the current guest.
- **Not completed by deadline**: the due time passed before the applicant finished.

Each integration guide names the field, flag, tag, or note the status is written to.

## After the due time

At the due time, the link says that the deadline has passed, and the reservation shows **Not completed by deadline** in the connected system. The connection's page under **Dashboard → Integrations** lists the reservation under **Records that need attention**, together with reservations where verification could not start and reservations whose applicant changed after verification started.

Select **Reopen verification** to set a new due time, at least 1 hour from now and no more than 365 days ahead. The applicant can then verify until that time: with invites on, they receive a new invitation; otherwise they use the link they already have. Before the reservation reopens:

- If an earlier verification for the reservation already started paid checks, you confirm that the new verification is charged.
- If a verification for the reservation is still in progress, you confirm that it is canceled so a new one can start.
- A verification that is still waiting for the applicant, or that is being processed, must end first; the console shows when. One that ran out of time while waiting for the applicant is closed by the reopen, unless it still has a document out for signature; the console then shows what to do.
- A paused connection must be resumed first. If the connected system paused it from its own side, as Mews can, turn the integration back on there first.
- A connection that needs reconnecting must be reconnected first: select **Reconnect** on it, then reopen the reservation.

A reservation canceled in the connected system can be verified again once it is restored there. A reservation canceled through the API, or by an AI assistant you connected, cannot be reopened; create a new verification for the applicant from **Applicants** instead.

**Request new identity verification** on a verification from a reservation is refused once the due time has passed or is less than an hour away. It is also refused 180 days after the verification was created. The console then shows the next step for that reservation.

## Pausing and disconnecting

- **Pause:** while a connection is paused, an applicant who opens their link is asked to try again later, and no verification starts on its own. Verifications already in progress continue. When you resume, a reservation whose verification opened while the connection was paused is handled as described in [When the verification starts](#when-the-verification-starts), unless its due time has passed.
- **Disconnect:** disconnecting deletes what Checktiv holds for the connection's reservations, so the verification links already written to your reservations stop working. Verifications that already started continue. If you connect the system again, a reservation gets a new link the next time it changes in the connected system.

<Aside type="note" title="Things to know">

- When a due time moves earlier, a verification in progress for the reservation's current applicant gets a deadline no later than that due time.
- When a due time moves later, a verification already in progress keeps its own deadline. If it lapses before the applicant starts any paid check, the applicant can start again from the same link. Otherwise, reopen the reservation to give the applicant more time.
- Starting from the link needs the connected system to answer. If it does not, the applicant sees the temporarily unavailable page and the console lists the reservation.
- Checktiv keeps what it holds for a reservation for 30 days after the latest of its opening, its due time and its check-out, or 30 days after it is canceled. A reservation with no due time and no check-out date is deleted 30 days after verification opens, even if the stay is later. Its link then stops working until the reservation next changes in the connected system, which gives it a new link.

</Aside>