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

The Mews integration verifies the applicant of each qualifying reservation in your Mews property automatically. You connect once with the property's access token, choose the workflow the verification runs and the [verification timing](/guides/integrations/verification-timing), and each qualifying reservation starts a verification for the applicant when its verification opens (by default, as soon as the integration reads it), without any manual step. The verification's status is kept in one note on the reservation, and the applicant's verification link and an internal review link are written on as two more notes, so your team sees them where they already work.

<Aside type="note" title="Where Mews is offered">
  Mews is offered region by region. The Mews tile on the **Integrations** page shows whether your
  region offers it. Where it does not, select the tile to see the other ways to start a
  verification: **Add an applicant**, **Create a shared link**, or the API.
</Aside>

This page covers the Mews integration specifically. For the full list of available integrations and how connections work in general, see the [Integrations overview](/guides/integrations).

## When to use

Connect Mews when you want reservations to trigger identity verification on their own, instead of adding each applicant by hand or through the API. It suits teams that:

- Take reservations in Mews and want every confirmed guest verified before arrival.
- Want the verification status and links visible on the reservation, so reviewers and front-desk staff do not switch tools.
- Want to control which reservations get verified (for example, skip company bookings, or run some on a different workflow) with routing rules rather than code.

If you only verify applicants occasionally, or you drive verification from your own system, the [API](/reference) or a [bulk CSV import](/guides/verification/bulk-import-csv) may fit better. You can use the integration alongside either.

## How it works

Once connected, Checktiv checks Mews for new and changed reservations about every 5 minutes. A reservation is read on the first check after it is created or changed in Mews:

1. **The integration checks Mews.** Each check reads the reservations that changed since the previous one, together with the guest, the rate, and the travel agency each one names. A reservation whose departure date is more than a day in the past is left out, so a change to a stay that is over never starts a verification.
2. **The reservation status decides the action.** The integration acts on the reservation's state (see the table below). A confirmed, checked-in, or checked-out reservation gets its verification link, and starts a verification when its verification opens if it does not already have one; an inquiry or an unconfirmed booking is skipped; a canceled reservation withdraws a verification still waiting on the guest or on your account's funds, and one already being checked or decided keeps its result.
3. **A verification is started.** For a reservation that should be verified, the integration starts a verification bound to the default workflow you chose when connecting, or to the workflow a routing rule selects for it. It starts when the reservation's verification opens. Before then, the applicant's link shows when they can start. The guest's contact details are carried onto the applicant so reviewers can identify them in the console, and the reservation's Mews identifier is stored as the applicant's external reference. Each room of a booking with several rooms is its own reservation in Mews, so each one starts its own verification.
4. **The applicant is invited, if the invite is on.** A new connection, including one you connect again after a disconnect, starts with **Send the verification invite** off. Turn it on to have the platform email the applicant their verification link; leave it off if you would rather send the link yourself from Mews using the note described below. A property that is connected for you, or that you approve, copies the setting of your chain's most recent connection instead; see [Later properties of a chain](#later-properties-of-a-chain). A connection that already exists keeps its setting, which the connection's **Edit** drawer shows.
5. **The status and links are written back.** The verification's status is kept in step in one note on the reservation. The verification link is written as a note as soon as the reservation qualifies, before any verification starts, and an internal review link is written as a note when the verification starts.

A verification takes the guest's details as they were when it started. A guest detail changed in Mews after a verification was created does not change that verification.

### What each reservation status does

The integration decides what to do from the reservation's state in Mews. This is the default behavior for a new connection:

| Mews state              | Console record status | What happens                                                                                                                                                        |
| ----------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Inquired                | Inquiry               | Skipped by default. Neither the guest nor the property has confirmed the booking.                                                                                   |
| Requested               | Pending               | Skipped by default. The guest has confirmed and the property has not.                                                                                               |
| Optional                | Pending               | Skipped by default. The property holds the space and the guest has not confirmed.                                                                                   |
| Confirmed               | Confirmed             | Starts a verification if the reservation does not already have one.                                                                                                 |
| Started (checked in)    | Confirmed             | Starts a verification if the reservation does not already have one; leaves an existing verification as is.                                                          |
| Processed (checked out) | Confirmed             | Starts a verification if the reservation does not already have one; leaves an existing verification as is, never withdrawing it.                                    |
| Canceled                | Canceled              | Starts no verification. A verification still waiting on the guest, or on your account's funds, is withdrawn; one already being checked or decided keeps its result. |
| Any other state         | None                  | Skipped. A state the integration does not recognize never starts a verification.                                                                                    |

A reservation that starts a verification gets its verification link as soon as it qualifies. The verification itself starts when the reservation's verification opens, which with the default timing is at once. Mews sends the stay's scheduled start as an exact time, so a timing measured from check-in uses that time as sent.

<Aside type="note" title="Which reservations create a verification">
  Two routing rules are added for you when you connect. The first skips inquiries and unconfirmed
  bookings by matching **Record status** against Inquiry and Pending. The second skips company
  bookings by matching **Record type** against `Company`: a company owns the reservation, so there
  is no guest to verify. You own both rules: you can edit or remove them, and you can add rules of
  your own (for example, to skip a particular travel agency). Confirmed, checked-in, and checked-out
  reservations share the one console record status, **Confirmed**, so a routing rule cannot target
  just one of them. Canceled reservations are handled without a rule: a cancellation withdraws a
  matching verification that is still waiting on the guest or on your account's funds, rather than
  starting a new one; one already being checked or decided keeps its result.
</Aside>

<Aside type="note" title="The integration is forward-only">
  The integration only reads a reservation that is created or changes after you connect. A
  reservation that has not changed since you connected is never read, no matter how old it is. A
  reservation whose departure date is more than a day in the past is not read either. An old
  reservation that changes for the first time after you connect, for example because it is
  confirmed, is read and treated like a new one: if it does not already have a verification, one
  starts, and you are billed for it. To keep a specific old reservation from starting a verification
  this way, add a routing rule that matches its **Confirmation code** (its Mews number) before it
  next changes.
</Aside>

The status note and the two link notes carry no applicant personal data. The applicant's verified details are sent to Mews only when you turn on **Send verified guest details to Mews** for the connection, and only for an approved verification.

### Reservation fields you can use in routing rules

Routing rules match on the fields the integration reads from each Mews reservation. On a Mews connection, the rule builder names two of these fields the way Mews does. The first column below is the name that you look for in the rule builder. The table lists the rows in alphabetical order, the same order as the rule builder. The other columns show where the value comes from, and how **is one of** compares it:

| Rule field        | Taken from the Mews reservation                                                                   | How **is one of** compares it                                 |
| ----------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
| Channel           | The name of the travel agency the booking came through. Empty on a booking with no travel agency. | Ignoring capitalization.                                      |
| Confirmation code | The reservation's Mews number, the one your staff search by.                                      | Ignoring capitalization.                                      |
| Email             | The email address of the guest who owns the reservation.                                          | Ignoring capitalization.                                      |
| End date          | The stay's scheduled end, as a UTC time, for example `2025-11-14T17:00:00Z`.                      | Exactly, so enter the full value Mews stores, not just a day. |
| First name        | The first name of the guest who owns the reservation.                                             | Ignoring capitalization.                                      |
| Full name         | The guest's first and last name together.                                                         | Ignoring capitalization.                                      |
| Last name         | The last name of the guest who owns the reservation.                                              | Ignoring capitalization.                                      |
| Lead time (days)  | The whole days between the day the reservation was created and the day the stay starts.           | As a whole number of days, so +03 matches 3.                  |
| Phone             | The phone number of the guest who owns the reservation.                                           | Digits only, so any punctuation you use is fine.              |
| Property ID       | The identifier of your Mews property.                                                             | Exactly, including capitalization.                            |
| Rate code         | The short name of the reservation's rate.                                                         | Ignoring capitalization.                                      |
| Rate name         | The name of the reservation's rate, in your property's default language.                          | Ignoring capitalization.                                      |
| Record status     | The reservation's state, normalized to the values in the table above.                             | Exactly, from the fixed list above.                           |
| Record type       | Who owns the reservation: `Customer` for a guest, `Company` for a company.                        | Ignoring capitalization.                                      |
| Reference ID      | The reservation's Mews identifier, a long code. The value every write-back is addressed to.       | Exactly, including capitalization.                            |
| Source            | How the reservation was created, as Mews records it, for example `Commander` or `ChannelManager`. | Ignoring capitalization.                                      |
| Space category ID | The identifier of the space category the guest booked, which is what Mews calls a room type.      | Exactly, including capitalization.                            |
| Start date        | The stay's scheduled start, as a UTC time, for example `2025-11-13T20:00:00Z`.                    | Exactly, so enter the full value Mews stores, not just a day. |
| Time zone         | Your property's time zone, for example `America/New_York`.                                        | Ignoring capitalization.                                      |

**is not one of** and **is not one of, or empty** ignore invisible characters and treat different forms of the same character as equal, such as a full-width `Ａ` and `A`. On the fields marked Exactly, they also ignore capitalization and spaces at the start and end.

A few rows are worth a second look:

- **Record status is ours, not Mews's.** It is the reservation's Mews state put through the table above, so a rule on it picks from Confirmed, Inquiry, Pending, and Canceled, never from Inquired, Requested, Optional, Started, or Processed. The rule builder also lists Excluded, but no Mews state becomes Excluded, so **is one of** with Excluded never matches a Mews reservation, and **is not one of** with Excluded leaves nothing out.
- **A rule that reads a guest detail sees a change to that detail when the reservation itself next changes.** The names, the email, and the phone come from the guest who owns the reservation. The integration reads them each time it reads the reservation, so an edit to the guest alone reaches your rules the next time the reservation changes in Mews.
- **A company booking has no guest details.** A reservation owned by a company carries no names, email, or phone, so those fields are empty on it. A condition on one of them that uses **is one of** or **is not one of** never matches it, and one that uses **is not one of, or empty** does. The routing rule added for you skips these bookings by their **Record type**.
- **Space category ID and Property ID are identifiers, not names.** Copy them from Mews rather than typing a room type or property name.
- **Start date and End date are UTC times.** A rule compares the full value, so copy it as Mews stores it rather than typing a calendar date.
- **Lead time (days) is worked out from two moments, on your property's calendar.** It counts the calendar days from the day the reservation was created in Mews to the day the stay starts, both read in your property's time zone, so a reservation created at 9:30 PM the evening before its start has a lead time of `1`, not `0`. `0` is the same day, and a reservation created after its start has a negative lead time. A reservation that Mews returns without a creation time has no lead time, and no condition on it matches that reservation, whatever the operator. The rule builder also offers **is less than**, **is at most**, **is greater than**, and **is at least** for this field. The [Integrations overview](/guides/integrations#routing-rules) describes them.

A field that is empty on the reservation is empty to the rule as well. A condition that uses **is one of** or **is not one of** never matches an empty field. A condition that uses **is not one of, or empty** matches it. If a rule has no effect, first make sure that its fields are not empty on the reservation.

A field that the integration could not read is not empty: it is unknown. The guest details, the two rate fields, and Channel come from three more reads, one for the guest, one for the rate, and one for the travel agency. Sometimes Mews does not return one of them, for example for a merged guest profile or a deleted travel agency. Then the fields from that read are unknown on that reservation, and a rule that uses one of them works like this:

- A **Skip verification** rule does not skip the reservation, so the guest is verified.
- A **Select workflow** rule does not select its workflow, and no rule below it applies. The reservation gets your default workflow.

A rule with no condition on an unknown field works as usual.

A rule can have more than one condition, and it matches a reservation only when all of them match. For example, a rule can have two conditions: Rate code **is one of** `WEB`, and Channel **is not one of, or empty** `Example Travel`. That rule matches each reservation on rate `WEB` that did not come through the travel agency `Example Travel`, in any capitalization. Channel is empty on a booking with no travel agency, so with **is not one of** the rule would not match those bookings. A **Skip verification** rule with these two conditions also skips the reservations on rate `WEB` with no travel agency. The rule builder shows no warning for this rule, because Rate code uses **is one of**. The [Integrations overview](/guides/integrations#routing-rules) describes each operator.

## Status note and links on the reservation

The integration writes back to Mews as notes on the reservation: one status note, and two notes that carry links.

### Status note

The integration keeps exactly one note on each reservation it screens, from the first time it reads the reservation. The note starts with **Checktiv verification status:**, followed by the reservation's screening status. The integration edits that note in place as the screening moves on, so the reservation always shows one current status. The status says **Guest screening** rather than naming one kind of check, because a workflow may run an ID check, a background check, or neither.

| Note text                                                                | When it is written                                                                                       |
| ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- |
| Checktiv verification status: Guest screening: Pending                   | The screening has started and has not yet reached review.                                                |
| Checktiv verification status: Guest screening: In review                 | The screening is awaiting your team's review, or finished with no outcome recorded yet.                  |
| Checktiv verification status: Guest screening: Approved                  | The screening was approved.                                                                              |
| Checktiv verification status: Guest screening: Declined                  | The screening was declined.                                                                              |
| Checktiv verification status: Guest screening: Not completed             | The screening expired, or was canceled without reaching an outcome.                                      |
| Checktiv verification status: Guest screening: Not yet open              | Screening for the reservation has not opened yet.                                                        |
| Checktiv verification status: Guest screening: Not started               | Screening for the reservation is open, and no screening is in progress for the guest.                    |
| Checktiv verification status: Guest screening: Not completed by deadline | The screening deadline passed before the guest finished, or too little time was left to start screening. |

The integration finds its note by the words it starts with, so do not start a note of your own with **Checktiv verification status:**. It treats every note that starts with those words as its own: it edits the first one, and removes any others, or rewrites them to the same status when they cannot be removed. Every other note on the reservation, yours and your staff's, is left exactly as it is.

### Applicant link and review link

The integration adds two notes to the reservation:

- **Screening link for the guest** carries the reservation's verification link. It is added as soon as the reservation qualifies, before any verification starts. Share this with the applicant if you send invites yourself.
- **Screening review link** carries an internal link your team uses to open the verification in the console. It is added when the verification starts. Not for the applicant.

Before it writes a link, the integration reads the reservation's notes, so it does not write the same link twice. The reservation's verification link stays the same for the whole verification window. It changes in two cases: a reservation canceled in Mews is no longer canceled when the integration next reads it, or the reservation gets a different owner in Mews, the guest or company that owns it. The integration then adds a new **Screening link for the guest** note, and the link in the earlier note stops working. A new name or email on the same owner does not change the link. A canceled reservation's link stops working, and no new note is added. You can always find both links by opening the verification directly in your Applicants list, whether or not the note is still there.

An applicant can open their verification link again after finishing. They then see where their verification stands (for example, submitted and under review) instead of an error. The link never reopens a finished verification. An applicant whose earlier verification lapsed before any paid check can start again from the same link while verification is open.

## Connecting Mews with an access token

You need the **Owner** or **Admin** role, an active organization, and at least one [workflow template](/guides/workflows/workflow-templates-create) to bind the connection to. Create a workflow first if you do not have one; the connect form links you to the workflow editor when none exist.

You connect with your property's **access token**, which Mews issues for this integration when your property subscribes to it.

<Steps>

1. In Mews, open **Marketplace**, then **My subscriptions**, and choose **Edit** on this integration's subscription to see its access token.

2. In the console, open **Integrations** and choose **Mews**.

3. Enter the **Access token**.

4. Choose the **default workflow** the integration runs for each reservation. This is required. Every verification the connection creates uses this workflow unless a routing rule skips it or selects another workflow. The list shows your active workflows, with your organization default marked.

5. (Optional) Add **routing rules** to change which reservations are verified. The connection starts with the two rules described above; you can keep them, edit them, or remove them, and add rules of your own. Each rule has one or more conditions, and each condition compares a field (such as Record status or Channel) with one or more values. When all of its conditions match, the rule either skips the reservation or selects the workflow it runs.

6. (Optional) Turn on the **Send the verification invite** toggle to have the platform email each applicant their verification link. It is off for a new connection. Leave it off if you plan to send the link yourself from Mews using the note described above.

7. (Optional) Set the **Verification timing**. By default, verification opens when a reservation reaches Checktiv and is due at the first verification's own deadline. To open it later or make it due at another time, see [Verification timing](/guides/integrations/verification-timing).

8. Select **Connect**. The button stays disabled until a workflow is chosen and the access token is filled.

</Steps>

When you select Connect, the platform checks the access token with Mews and reads the property it belongs to; once that check passes, the connection appears in your Integrations list. Each Mews property connects once: a property that is already connected in your organization, or in another one, is refused with a message that names the next step. An access token that covers several properties at once is refused too, so connect each property with its own access token.

A Mews property is connected in one data region only. A property that is already connected to an organization in the other data region is refused here, with a message that names the next step (see [Troubleshooting](#troubleshooting)).

## Installing from Mews Marketplace

A property can also start the integration from Mews: in Mews, open **Marketplace**, find Checktiv, and add it. What happens next depends on whether an organization already connects another property of the same Mews chain:

- **No organization connects the chain yet.** We email a link to the person who added Checktiv in Mews, or to the property's own email address in Mews when Mews names nobody. That person connects the property from the link. See [Connecting a property from the email](#connecting-a-property-from-the-email).
- **Your organization connects the chain, and the property's data belongs in your organization's data region.** The property is connected for you, with no step from anyone. See [Later properties of a chain](#later-properties-of-a-chain).
- **Your organization connects the chain, but the property's data normally belongs in the other data region, or its country is not known.** The property waits for an owner or admin of your organization to approve it. See [Waiting for approval](#waiting-for-approval).

When more than one organization connects the chain, or one organization connects it in both test and live mode, a new property is not connected for anyone: we email the link, the same as for a first property.

### Connecting a property from the email

The email's subject starts with **Finish connecting**, and its link opens the property in the console.

<Steps>

1. Open the link in the email.

2. Sign in, or create an account, with the email address the link was sent to, and verify that address. Only an owner or admin of an organization, signed in with that verified email address, can connect the property.

3. Review the property. The page shows its name and country, the data region its data will be stored in, and whether you are in test or live mode. The integration is created in the mode you are in; to create it in the other mode, switch modes at the top of the page.

4. Choose the **default workflow** the integration runs for each reservation. If you have no active workflow yet, the page links to the workflow editor, which brings you back to this page when you save your first workflow.

5. Select **Connect**. The connection appears in your Integrations list, and from then on it works exactly like a connection made with an access token.

6. (Optional) Set the **Verification timing**. The property page has no timing section, so the connection starts with the default timing: verification opens when a reservation reaches Checktiv and is due at the first verification's own deadline. To open it later or make it due at another time, choose **Edit** on the connection in your Integrations list, and see [Verification timing](/guides/integrations/verification-timing). Do this right after you connect, because a reservation read before then may already have started its verification.

7. (Optional) Turn on **Send the verification invite**. The property page has no invite setting, so a connection created from the page starts with the verification invite off. A notice on the page says so. To have the platform email each applicant their link, choose **Edit** on the connection in your Integrations list, and turn on **Send the verification invite**. Do this right after you connect, because a reservation whose verification opens while the setting is off gets no invite when you turn it on later.

</Steps>

The link stays valid for 14 days. If you created your account from the email, the page does not open the property again by itself after you sign up: open the link in the email again, or open **Integrations**, where **Waiting to be connected** lists every property that named your verified email address, and select **Review and connect**.

### Choosing the data region

The property page says which data region the property's data will be stored in: the region where your organization's data is stored. If the organization that should hold the property is in the other data region, select the option to use that region instead, for example **Use the European Union data region instead**. A property can be moved once. Your browser then opens the property in the other region's console, where you sign in and finish connecting it, and we email the new link too. The link in the first email stops working, and the new link expires when the first one would have: moving a property does not add time.

If a move does not finish, the page shows **Finish moving to** the other region, and the property can no longer be connected in the first region. Select it to try the move again.

### Later properties of a chain

When your organization connects a property of a Mews chain, a later property of the same chain that adds Checktiv in Mews is connected for you, as long as its data belongs in your organization's data region and your organization connects the chain in one mode only:

- The new connection uses the default workflow, the routing rules, and the verification invite setting of your organization's most recent Mews connection of that chain. It starts with the default verification timing. To change any of these, choose **Edit** on the new connection.
- If your organization already connected that property with an access token, the existing connection is kept, with its workflow, routing rules, and other settings, and it switches to the access token of the new subscription.
- The property's contact receives an email that names your organization and says how to stop sharing in Mews. When the property gets a new connection, your organization's owners and admins receive an email too.

To stop a property that should not be part of your organization, cancel Checktiv for it in Mews, under **Marketplace**, then **My subscriptions**. That disconnects the connection, the same as described in [When Mews pauses, removes, or renews the subscription](#when-mews-pauses-removes-or-renews-the-subscription).

### Waiting for approval

A later property of your chain is not connected automatically when its country's data normally belongs in the other data region, or when its country is not known. It waits on your **Integrations** page, under **Waiting for approval**, and your organization's owners and admins receive an email.

- Each property says where it is and that, if you approve it, its data will be stored in your organization's data region.
- **Approve and connect** connects it, with the workflow, routing rules, and verification invite setting of your organization's most recent Mews connection of the chain. It starts with the default verification timing. To change any of these, choose **Edit** on the new connection.
- A property waits in the mode your organization connects the chain in. To approve or decline one that waits in the other mode, switch modes at the top of the page.
- **Decline** leaves it unconnected, and we tell the property's contact by email. Declining does not remove Checktiv from Mews: to stop it there too, also cancel Checktiv for that property in Mews, under **Marketplace**, then **My subscriptions**.
- If nobody decides within 14 days, the property expires and is not connected, and we tell its contact. Each property shows the date it expires (UTC).

Only owners and admins see these properties. A member's Integrations page shows instead: "Only organization owners and admins can manage integrations or approve an installation from the marketplace. Ask an owner or admin to do it for you."

## While Mews needs reconnecting

If Mews no longer accepts the stored access token, for example because the subscription was removed or its token was replaced, the connection shows **Reconnect needed** and stops reaching Mews: it stops checking for new and changed reservations, and any status note or link note that would be written back is held instead. Nothing already written to Mews is undone.

Once you reconnect with a working access token, the integration picks up where it left off: it resumes checking Mews from before the interruption, so reservations that changed while it needed reconnecting are still read. It also rebuilds the status note and both link notes for every verification that was waiting, as long as it had been waiting less than 14 days; reconnect promptly, since one waiting longer is not rebuilt automatically. For a reservation that has a screening window, the 14-day limit does not apply to the reservation's status note and its **Screening link for the guest** note. They are rebuilt until 30 days after the latest of these dates: the day screening opens, the screening deadline, and the check-out date. For a canceled reservation, they are rebuilt until 30 days after the cancellation. You do not need to do anything else beyond reconnecting.

<Aside type="tip" title="Reconnecting">
  Open the integration and choose to reconnect, then enter a fresh **Access token** for the same
  property. Your workflow choice, routing rules, and invite setting are preserved through a
  reconnect. To connect a different Mews property, add a new connection instead.
</Aside>

## When Mews pauses, removes, or renews the subscription

A connection your property set up from Mews Marketplace follows what happens to that subscription in Mews:

- **Turned off in Mews.** When the subscription is disabled or canceled in Mews, the connection is paused and shows "Mews has paused this integration. Turn Checktiv back on in Mews Marketplace > My subscriptions." While it is paused, the integration stops checking Mews for new and changed reservations, and the status note and link notes are held instead of being sent. An applicant who opens their link is asked to try again later, and **Reopen verification** on a reservation is refused until Checktiv is back on. You cannot resume it from the console while Mews holds it paused.
- **Turned back on in Mews.** The pause lifts on its own, and the connection returns to active unless you also paused it yourself, in which case resume it from the console. The held status note and link notes are sent within about 15 minutes, for verifications that waited less than 14 days. A reservation's status note and its **Screening link for the guest** note are sent for as long as they would be rebuilt after a reconnect (see [While Mews needs reconnecting](#while-mews-needs-reconnecting)). If the connection showed **Reconnect needed** while it was paused, the integration checks the saved access token again; when Mews accepts it, the connection returns to active with no step from you.
- **Removed from Mews.** Deleting the subscription in Mews disconnects the connection, the same as disconnecting it yourself: verifications that already started continue, and the verification links on your reservations stop working. A property that had not finished connecting yet can no longer be claimed or approved. To connect the property again, add Checktiv again from Mews Marketplace, or connect it with an access token.
- **A new access token in Mews.** When the property generates a new access token for the subscription, the connection switches to it on its own. If Mews does not accept the new token, the connection keeps the previous one; if that one stops working too, the connection shows **Reconnect needed**, and you reconnect with the new access token.

## Troubleshooting

**The connection did not go through.**
Check, in order:

- The access token was not accepted. Copy it again from the subscription in Mews, in full. The console shows: "These credentials were not accepted. Check the values you entered and try again."
- The integration is waiting on an update on our side. The console shows instead: "This integration cannot connect yet because some of the actions it needs are waiting on an update on our side. We have been notified, and nothing in your connected system needs to change. Try connecting again later." Nothing in Mews needs to change; try connecting again later.
- The property is already connected, in your organization or in another one. Follow the next step the message names.
- We could not get an answer. The console says "The connected system is not responding. Try again in a few minutes." This is temporary, and nothing in Mews needs to change. Your access token was not refused and the form keeps what you entered, so wait a few minutes and press **Connect** again. If it keeps happening, check **Waiting to be connected** on the **Integrations** page, and select **Review and connect** if it lists the property. That list holds a property only when an installation from Mews Marketplace reached us for it, so it is often empty: then all you can do is press **Connect** again later.

**This Mews property is already connected in another data region.**
Connecting shows: "This account is connected to an organization in another data region. If you manage that organization, disconnect it there, then connect it here. Otherwise, ask that organization's owner or an admin to disconnect it." A Mews property is connected in one data region only. Once it is disconnected in the other region, connect it here. On a property page opened from the email, the installation is kept, and the page points to the option to use the other data region instead, where the property can be connected. If the page offers no such option (for example, the property was already moved once), this message ends that installation, so connect the property with its access token instead. A property disconnected in the other region a few minutes ago can still show this message for up to about an hour; try again later.

**A property page opened from the email shows "This installation is not waiting for you."**
The page says: "We could not find an installation waiting for your email address at this link. It may have expired after 14 days, been connected already, been moved to another data region, or been sent to a different email address. Sign in with the verified email address it was sent to, or connect with an integration token instead." Check that you are signed in with the verified email address the link was sent to. If the link expired, add Checktiv again in Mews, or connect the property with its access token: **Connect with an integration token** opens the connect form described in [Connecting Mews with an access token](#connecting-mews-with-an-access-token).

**A property page opened from the email says only an owner or admin can connect it.**
The page says: "Only an organization owner or admin can connect this installation, and it must be the person it was sent to. Ask your organization's owner to make you an admin, or create an organization of your own and open this link again."

**You added Checktiv in Mews, and no email arrived.**
Check, in order:

- **Who it went to.** The email goes to the person who added Checktiv in Mews, or to the property's own email address in Mews when Mews names nobody. Check that mailbox's spam folder too.
- **Whether your organization already connects the chain.** Then no email is sent: the property is connected for you, or waits under **Waiting for approval** on the **Integrations** page.
- **The Integrations page.** Sign in with the verified email address the link would go to, and open **Integrations**: **Waiting to be connected** lists the property.
- **An email saying the property was not connected.** When the property's country is missing or not recognized in Mews, we cannot tell which data region should store its data, so we send that email instead of the link. Set the country in Mews and add Checktiv again, or create an account in the data region you choose and connect the property with its access token. The email gives both steps.
- **Several properties at once.** An installation whose access covers several properties at once cannot be connected from Mews Marketplace, and the email says so. Connect each property with its own access token.

If none of these finds the property, connect it with its access token, as described in [Connecting Mews with an access token](#connecting-mews-with-an-access-token).

**The Mews tile says "Not available in this region."**
Mews is offered region by region, and your region does not offer it. Select the tile to see the other ways to start a verification: **Add an applicant** adds one person as an applicant, and **Create a shared link** makes a link that applicants open to verify themselves. You can also start verifications through the API.

**The connection shows "Reconnect needed."**
Mews no longer accepts the stored access token. Open the integration, choose to reconnect, and enter a fresh access token. If the connection also shows "Mews has paused this integration," it offers no **Reconnect**: turn Checktiv back on in Mews first, as the entry for that message below describes. The integration then checks the saved access token again, and offers **Reconnect** only if Mews still refuses it. See [While Mews needs reconnecting](#while-mews-needs-reconnecting) above for what happens to reservations and write-backs in the meantime.

**The connection shows "Some actions this integration needs are waiting on an update on our side, and we have been notified. Nothing is needed from you: the rest of the integration is not affected, and updates from the last 14 days that were held back are sent automatically once this clears."**
Mews does not yet let the integration perform some of its actions, such as writing the status note or the link notes. This is ours to resolve with Mews, and nothing in your property needs to change. Reservations are still read and verifications still start; the notice clears on its own.

**The connection shows "Mews has paused this integration. Turn Checktiv back on in Mews Marketplace > My subscriptions."**
The subscription is turned off in Mews, so the integration is not checking Mews and is holding its write-backs. In Mews, open **Marketplace**, then **My subscriptions**, and turn Checktiv back on. The connection resumes on its own, and the held write-backs are sent within about 15 minutes. See [When Mews pauses, removes, or renews the subscription](#when-mews-pauses-removes-or-renews-the-subscription).

**Resuming the connection shows "Mews has paused this integration, so it cannot be resumed here. Turn Checktiv back on in Mews Marketplace > My subscriptions."**
Mews holds the connection paused, and only turning Checktiv back on in Mews lifts that. In Mews, open **Marketplace**, then **My subscriptions**, and turn Checktiv back on; the connection resumes on its own.

**Reopening a reservation shows "Mews has paused this integration. Turn Checktiv back on in Mews Marketplace > My subscriptions, then reopen the record."**
No verification can start while Mews holds the connection paused, so the reservation is not reopened. Turn Checktiv back on as described in the entry above, then select **Reopen verification** on the reservation again.

**The connection was removed after the subscription was deleted in Mews.**
Deleting the subscription in Mews disconnects the connection. To connect the property again, add Checktiv again from Mews Marketplace, or open **Integrations**, choose **Mews**, and connect it with an access token.

**The connection shows "Not responding. We will keep retrying automatically."**
Mews has been unreachable or timing out for a while. This clears on its own once Mews responds normally again; you do not need to do anything.

**The connection is paused and shows "The saved credentials are no longer accepted. Use Edit to enter working credentials to resume."**
Edit the connection and enter a working access token. Saving a working access token returns the connection to active on its own; there is no separate step after that. Trying to resume the connection before that is done shows: "Enter working credentials for this integration to resume."

**A reservation did not create a verification.**
Check, in order:

- **The verification timing.** A reservation whose verification has not opened yet already has its link note, and its status note reads **Checktiv verification status: Guest screening: Not yet open**. Its verification starts when verification opens. See [Verification timing](/guides/integrations/verification-timing).
- **The reservation state.** Only Confirmed, Started (checked in), and Processed (checked out) reservations start a verification, and only when the reservation does not already have one. An Inquired, Requested, or Optional reservation is skipped until it is confirmed, and a Canceled reservation never starts one. See the [status table](#what-each-reservation-status-does) above.
- **The departure date.** A reservation whose departure date is more than a day in the past is not read, whatever its state.
- **Routing rules.** A reservation that matches a Skip rule is intentionally not verified, and one that matches a Select workflow rule runs that rule's workflow instead of the default. Review the connection's rules, including the two added for you, against the reservation's fields.
- **The check schedule.** Checktiv checks Mews for new and changed reservations about every 5 minutes, so a very recently changed reservation may not have been picked up yet.
- **Whether the reservation has changed since you connected.** The integration only reads a reservation that changes after you connect; one that has not changed is never read, however old it is.
- **The workflow.** The connection must be bound to an active workflow. The connection's form flags an inactive default workflow; edit the connection and choose an active one.

**A guest's details changed in Mews, and the verification still shows the old ones.**
A verification takes the guest's details as they were when it started, and a later change in Mews does not change it. Review the applicant's details on the verification in your Applicants list before you make a decision.

**An applicant did not receive their invite.**
Confirm the **Send the verification invite** toggle is on for the connection. A new connection starts with it off, and while it is off the platform does not email the applicant; you are expected to send the link yourself using the note the integration wrote onto the reservation. Turning it on invites each applicant whose verification opens after the change. To invite an applicant whose verification already started, open it in your **Applicants** list and select **Send invite** (see [Resend or revoke](/guides/verification/send-an-invite#resend-or-revoke)). If their verification has not started yet, share the link in the note the integration wrote onto the reservation. Also confirm the guest who owns the reservation has an email address in Mews, since there is no address to send to otherwise. If that email address reached the [per-recipient invite limit](/developers/rate-limits#per-recipient-invite-limit) of three invite emails in an hour, the verification starts but Checktiv sends no invite. Open that verification in your **Applicants** list and select **Send invite**.

**The status note is missing or looks wrong.**
The integration writes the status note the next time the screening status changes. If the verification has already reached its final status and will not change again, the note stays as it is; this does not affect the verification itself. If you see more than one note starting with **Checktiv verification status:**, the next status change keeps the first and removes the others.

**You want to stop the integration.**
Pausing the connection in the console is separate from turning the subscription off in Mews: a pause you set is lifted only by resuming it in the console. Pausing stops the integration from checking Mews for new and changed reservations, but it does not stop a write-back already under way: a verification that was already in progress keeps updating its status note as it moves through review. Reservations that change while paused are not read once you resume, unless they change again afterward; resuming does not catch up the way reconnecting does. While a connection is paused, an applicant who opens their link is asked to try again later.

Disconnecting removes the connection entirely and stops all future write-backs. Verifications that already started continue either way, but disconnecting also makes the verification links on your reservations stop working. To start again later, resume a paused connection, or connect again if you disconnected it; after you connect again, a reservation gets a new link the next time it changes in Mews.

## Related

- [Integrations overview](/guides/integrations)
- [Create a verification workflow template](/guides/workflows/workflow-templates-create)
- [Glossary](/glossary)