Loading...
Haven can require the primary guest on a booking to verify their identity before WiFi, lock codes, check-in instructions, and contact details unlock in the guest portal. This is an opt-in, per-property setting. Identity verification is a Haven feature backed by Stripe Identity — guests photograph a government ID in a Stripe-hosted flow. It is separate from Truvi guest screening.
You can also apply agreement and ID requirements to Airbnb, Vrbo, and other synced (OTA/PMS) stays. On those stays Haven bills you for the identity fee (there is no Haven guest checkout to add a line item to). Guests complete the check in the Haven guidebook; a Haven booking website is not required.
For the full set of guest-security tools (ID, Truvi screening, deposits, and agreements), see Guest security options.
You'll see Guest verification on each property under Edit Listing → Arrival guide, and on each Multi-Unit Site under Settings → Guest verification (opens the right-side editor). The two requirements are independent toggles — turn on one, both, or neither:
| Setting | What guests see |
|---|---|
| Require a signed rental agreement | Guests sign your rental agreement before WiFi, lock codes, check-in, and host contact unlock. |
| Require identity verification | A Stripe-hosted identity check before those same details unlock. |
When identity verification is on, two more controls appear:
Changes autosave. There is no separate Save button.
Haven uses Stripe Identity. When a guest opens their guide for a confirmed, paid booking that requires verification, they see a "Verify your identity" tile. The tile does not appear while the reservation is still awaiting host approval or payment. Tapping it launches a Stripe-hosted flow where they:
Once verified, the guest's check-in details unlock automatically in the guide. Most verifications come back in seconds; a small fraction get flagged for human review and are surfaced in the Haven admin queue.
Identity verification carries a flat $4.99 per-booking fee (charged once per reservation, not per night).
When you enable identity verification, you choose who pays on Haven checkout:
| Who pays | Guest checkout | Your payout |
|---|---|---|
| Guest pays (default) | Line item at $4.99 | No deduction — Haven retains the fee |
| You pay | No verification line item | $4.99 deducted from your payout |
The fee is not refundable once charged (Haven pays Stripe for the check).
On Airbnb, Vrbo, and other synced reservations, you always pay. Haven charges your saved payment method when the reservation syncs (if you opted the listing into "Also require agreement / ID on synced stays"). Guests complete the Stripe Identity step in the guidebook via a personal link — they are never charged by Haven for verification on OTA stays.
In Edit Listing → Arrival guide → Guest verification, or Multi-unit site editor → Settings → Guest verification, turn on:
Those stays only complete ID verification if they open the guidebook. Turn on Auto-send the guide under Edit Listing → Arrival guide → Guidebook access so Haven emails the guide at booking and again before check-in — including guests whose reservation came from Airbnb, Vrbo, or another channel. You can also paste the guide link into OTA messages or print a QR code. See Guest Portal.
Cancellation caveat: when the OTA/PMS sends a cancellation webhook, Haven cancels Truvi and refunds unused Screen & Protect nights (before check-in). Identity fees are never refunded. If a cancel does not sync (off-platform booking with no webhook), use Cancel add-ons on that reservation so Haven can refund Screen & Protect.
If a property belongs to a Multi-Unit Site, that site's Guest Verification setting (Settings → Guest verification) applies by default. Editing the level on a specific property pins an override and stops that property from inheriting future site-level changes — matching how rental agreement library inheritance already works.
If a guest's verification is rejected or expires, the guide shows a "Needs attention" state with a button to try again. A new attempt creates a fresh Stripe Identity session; the old attempt stays on the record for audit.
Admins can manually mark an attempt verified or rejected from the
Guest Verification admin queue at /admin/guest-identity. This is
intended for the small fraction of cases Stripe sends back as
requires_input — most attempts resolve automatically.
New to Haven?
Haven is the direct booking platform these guides are written for — a branded site, secure payments, and guest relationships you own. Build yours free.
Free to build · No credit card · Private until you publish
© 2026 Book With Haven, LLC.