--- title: "Migrate to V2 Custom Fields: Simple Yes/No Verification Results in Your PMS" description: Switch your Guesty, Hostaway, Lodgify, or OwnerRez templates and automations from retired V1 to V2 custom fields, with a Yes/No for each check. --- [Skip to content](https://info.authenticate.com/v2-custom-fields-migration#main-content) [🙋‍♂️ Raise a Support Ticket](https://info.authenticate.com/kb-tickets/new?hsLang=en) [![Authenticate](https://info.authenticate.com/hubfs/authenticate_logo_2023_tm_rgb.svg)](https://authenticate.com/) Open main navigation Close main navigation - [🙋‍♂️ Raise a Support Ticket](https://info.authenticate.com/kb-tickets/new) Looking for answers? Ask us anything. - There are no suggestions because the search field is empty. 1. [Knowledge Base](https://info.authenticate.com/?hsLang=en) 2. [Integrations](https://info.authenticate.com/integrations?hsLang=en) 3. [Manage Your PMS Integration](https://info.authenticate.com/integrations?hsLang=en#manage-your-pms-integration) # Migrate to V2 Custom Fields: Simple Yes/No Verification Results in Your PMS ## Six new custom fields give you a simple Yes or No for each verification check. Here's how to switch from V1. Authenticate sends verification results to your property management system as six V2 custom fields, each with a simple **Yes** or **No** value. They replace three V1 fields whose technical values, such as `valid_and_live_match_fail`, were hard to read at a glance and hard to build automations on. V2 custom fields work with Guesty, Hostaway, Lodgify, and OwnerRez. ### Who needs to migrate? If you activated your property management integration **before March 30, 2026** and haven't migrated yet, follow the steps below now. The deprecated V1 fields were retired on **October 1, 2026**, so any message templates or automations that still use them are no longer receiving results. ### What's changing - **One field per check.** Identity proof, face match, liveness, US authoritative database, US 7-year criminal records, and global watchlist each get their own field. - **Yes/No values.** No more technical status codes to decode. - **No separate pass criteria.** Your workflow configuration now acts as your pass criteria, so there's no extra setting to configure. This diagram shows where each V2 custom field sits in your verification workflow: ![Workflow diagram showing which V2 custom field each verification check sets, and which results need review](https://info.authenticate.com/hubfs/knowledge-base/manage-your-pms-integration/v2-custom-fields-in-pms.png) ### V2 custom fields | Custom field | What it tells you | Values | | --- | --- | --- | | `Authenticate_identity_proof_valid` | Whether the guest's identity proof is valid. | **Yes:** the identity proof checks in your workflow passed. With an AND workflow, every configured check must pass. With an OR workflow, any one check is enough. **No:** the identity proof checks failed. | | `Authenticate_face_match_passed` | Whether the guest's selfie matches their government ID. Only sent when your workflow includes Government ID + Selfie. | **Yes:** the selfie matches the ID. **No:** the selfie doesn't match the ID. **Review needed.** | | `Authenticate_liveness_confidence_score_high` | Whether the selfie was taken of a live person. Only sent when your workflow includes Government ID + Selfie. | **Yes:** the liveness confidence score is high. **No:** the liveness confidence score is low. **Review needed.** | | `Authenticate_us_only_authoritative_db_check_passed` | US guests only. Whether the guest was found in the US authoritative database. | **Yes:** the guest was found. **No:** the guest wasn't found. **Review needed.** Check the `Authenticate_error` field for details. | | `Authenticate_us_only_seven_year_criminal_record_found` | US guests only. Whether any criminal records were found from the last 7 years. | **Yes:** criminal records were found. **Review needed.** **No:** no criminal records were found. | | `Authenticate_global_watchlist_record_found` | Whether the guest appears on a global watchlist. | **Yes:** a watchlist record was found. **Review needed.** **No:** no watchlist record was found. | **Check the field name before you build a rule.** For fields ending in `_valid`, `_passed`, or `_high`, **Yes** is the good result. For fields ending in `_found`, **Yes** means a record was found and the guest needs review. ### Which V1 fields are changing? These V1 fields were retired on October 1, 2026. Authenticate no longer sends values to them: - `Authenticate_id_status` - `Authenticate_criminal_report_status` - `Authenticate_verification_passed` These V1 fields aren't changing, and you can keep using them: - `Authenticate_error` - `Authenticate_verification_link` - `Authenticate_guest_profile` ### Steps to Migrate to V2 Custom Fields 1. **Deactivate Your Integration** - Click **Integrations** in the sidebar and select your property management system. - Click **Active**, choose **Deactivate**, and confirm. Your settings are kept for when you reactivate. 2. **Reactivate Your Integration** - Reactivate the integration from the same page. 3. **Check a New Booking** - Open a booking created after you reactivated and confirm the V2 custom fields are filled in. 4. **Update Your Templates and Automations** - Replace V1 custom fields with their V2 equivalents in your message templates and automations, using the replacement guide below. ### V1 to V2 Replacement Guide | Deprecated V1 field | Replace with | | --- | --- | | `Authenticate_id_status` Values: `valid_and_verified`, `valid_and_not_verified`, `valid_and_live_match_fail`, `valid_and_not_us_id` | Any of these V2 fields, on their own or combined: `Authenticate_identity_proof_valid` `Authenticate_face_match_passed` `Authenticate_liveness_confidence_score_high` `Authenticate_us_only_authoritative_db_check_passed` See the value-by-value guide below. | | `Authenticate_criminal_report_status` Values: `clear`, `requires_review`, `insufficient_data` | `Authenticate_us_only_seven_year_criminal_record_found` | | `Authenticate_verification_passed` Values: `Yes`, `No` | No direct replacement. Use the individual V2 fields for the checks you care about. | ### Replacing Authenticate\_id\_status Values | V1 value | What it meant | V2 equivalent | | --- | --- | --- | | `valid_and_verified` | ID valid and found in the US authoritative database | `Authenticate_identity_proof_valid` = Yes AND `Authenticate_us_only_authoritative_db_check_passed` = Yes | | `valid_and_not_verified` | ID valid but not found in the US authoritative database | `Authenticate_identity_proof_valid` = Yes AND `Authenticate_us_only_authoritative_db_check_passed` = No | | `valid_and_live_match_fail` | ID valid but liveness check failed | `Authenticate_identity_proof_valid` = Yes AND `Authenticate_liveness_confidence_score_high` = No | | `valid_and_not_us_id` | ID valid but not a US ID | `Authenticate_identity_proof_valid` = Yes AND `Authenticate_us_only_authoritative_db_check_passed` = No | **Note:** in V2, `valid_and_not_verified` and `valid_and_not_us_id` produce the same result: identity proof is **Yes** and the US authoritative database check is **No**. Non-US guests always get **No** for the database check, so V2 doesn't tell these two cases apart. ### Example: Update an Automation Rule **V1 rule:** IF `Authenticate_id_status = "valid_and_verified"`, send check-in codes. **V2 rule:** IF `Authenticate_identity_proof_valid = "Yes"` AND `Authenticate_us_only_authoritative_db_check_passed = "Yes"`, send check-in codes. If you have questions or something isn't working as described here, [open a support ticket](https://info.authenticate.com/kb-tickets/new?hsLang=en) and our team will help you out. - [Before you begin](https://info.authenticate.com/before-you-begin?hsLang=en#main-content) - [About Authenticate®](https://info.authenticate.com/before-you-begin?hsLang=en#about-authenticate) - [Pricing: Pay-as-you-go](https://info.authenticate.com/before-you-begin?hsLang=en#pricing-pay-as-you-go) - [Solutions by Authenticate®](https://info.authenticate.com/before-you-begin?hsLang=en#solutions-by-authenticate) - [Account Activation](https://info.authenticate.com/before-you-begin?hsLang=en#account-activation) - [How to verify a user?](https://info.authenticate.com/before-you-begin?hsLang=en#how-to-verify-a-user) - [Data Coverage & Compliance](https://info.authenticate.com/before-you-begin?hsLang=en#data-coverage-compliance) - [Getting started](https://info.authenticate.com/getting-started?hsLang=en#main-content) - [General](https://info.authenticate.com/getting-started?hsLang=en#general) - [Medallion™](https://info.authenticate.com/getting-started?hsLang=en#medallion) - [No-Code Solutions](https://info.authenticate.com/getting-started?hsLang=en#no-code-solutions) - [API Solutions](https://info.authenticate.com/getting-started?hsLang=en#api-solutions) - [Products](https://info.authenticate.com/products?hsLang=en#main-content) - [User Insights](https://info.authenticate.com/products?hsLang=en#user-insights) - [Identity Verification](https://info.authenticate.com/products?hsLang=en#identity-verification) - [Criminal and Civil Records](https://info.authenticate.com/products?hsLang=en#criminal-and-civil-records) - [Background Checks](https://info.authenticate.com/products?hsLang=en#background-checks) - [Sandbox](https://info.authenticate.com/sandbox?hsLang=en) - [Pricing](https://info.authenticate.com/pricing?hsLang=en#main-content) - [Pricing Model](https://info.authenticate.com/pricing?hsLang=en#pricing-model) - [Integrations](https://info.authenticate.com/integrations?hsLang=en#main-content) - [Guesty](https://info.authenticate.com/integrations?hsLang=en#guesty) - [Hostaway](https://info.authenticate.com/integrations?hsLang=en#hostaway) - [Hostfully](https://info.authenticate.com/integrations?hsLang=en#hostfully) - [Lodgify](https://info.authenticate.com/integrations?hsLang=en#lodgify) - [OwnerRez](https://info.authenticate.com/integrations?hsLang=en#ownerrez) - [SuiteOp](https://info.authenticate.com/integrations?hsLang=en#suiteop) - [Manage Your PMS Integration](https://info.authenticate.com/integrations?hsLang=en#manage-your-pms-integration) - [FAQs](https://info.authenticate.com/faqs?hsLang=en#main-content) - [Introduction](https://info.authenticate.com/faqs?hsLang=en#introduction) - [Verification and Background Checks](https://info.authenticate.com/faqs?hsLang=en#verification-and-background-checks) - [Step-by-Step Hub](https://info.authenticate.com/faqs?hsLang=en#step-by-step-hub) - [Admin Profile](https://info.authenticate.com/faqs?hsLang=en#admin-profile) - [Compliance](https://info.authenticate.com/faqs?hsLang=en#compliance) - [Integrations](https://info.authenticate.com/faqs?hsLang=en#integrations) - [Pricing](https://info.authenticate.com/faqs?hsLang=en#pricing) - [Troubleshooting](https://info.authenticate.com/faqs?hsLang=en#troubleshooting) [![Chill listening crop-3](https://info.authenticate.com/hs-fs/hubfs/authenticate-logo-rgb-svg%20(3).png?width=195&height=24&name=authenticate-logo-rgb-svg%20(3).png "Chill listening crop-3")](https://authenticate.com/) 730 Arizona Avenue, Suite 230, Santa Monica, CA 90401 [mailto:support@authenticate.com](mailto:support@authenticate.com) Copyright © 2026, Authenticate