BookingsUpdated 11/14/2026

Guest security options

Haven gives you several independent ways to know who is staying and to recover when something goes wrong. They are not one product. A background-style check, a government ID, a card hold, and a signed agreement each do a different job — and you can turn on as many as you want.

Use this page as the map. Each tool has its own setup, billing, and guest experience.

The four tools

ToolWhat it actually checks or coversWhere guests complete it
Guest ID verificationGovernment photo ID (and an optional matching selfie), via Stripe Identity inside HavenGuest portal tile — “Verify your identity”
Guest screening + damage protectionName, mobile, email, and prior damages in Truvi records, plus up to $50,000 protection on eligible staysNothing extra for the guest. Screening runs in the background at booking.
Security depositA refundable authorization hold on the guest’s cardCheckout shows a “Refundable hold”; the hold is placed a few days before check-in
Rental agreementA signed legal snapshot of your termsGuest portal — guests sign before gated details unlock

ID verification is Haven’s own flow, backed by Stripe. It is not Truvi, and it is not a credit check. Screening is the Truvi piece. Do not collapse the two.

Guest ID verification (Haven, backed by Stripe)

When you require identity verification, the primary guest opens their guest portal on a confirmed, paid stay, taps Verify your identity, and completes a Stripe-hosted session: they choose a passport, driver’s license, or national ID, photograph it, and (if you asked) take a selfie that matches the document. Stripe verifies the session and tells Haven the result. Most checks return in seconds. The tile is hidden while a reservation is still awaiting approval or payment.

Wi-Fi, lock codes, check-in instructions, and host contact stay locked until the attempt is verified. You see status only on the reservation — never the images. Identity verification keeps no ID photo in Haven; Stripe holds it and deletes it on their retention schedule.

A Photo ID question on an upsell or rental is a different thing: the buyer uploads a photo of their license for you to look at, nothing is verified, and Haven stores it privately for your account until 30 days after the rental. See Photo ID on an upsell is not verification.

The fee is a flat $4.99 per booking (not per night). On Haven checkout you choose whether the guest pays that line or you absorb it from your payout. It is not refunded once charged, because Haven has already paid Stripe for the check.

Enable it per listing in Edit Listing → Arrival → Guest verification, or as a Group Site default in Group site editor → Settings → Guest verification → Require identity verification. You can also require a matching selfie and choose who pays on Haven bookings.

Full walkthrough: Guest Identity Verification.

Silent screening and damage protection (Truvi)

Damage protection, powered by Truvi, is the background check people usually mean when they ask “does anyone get screened?” Truvi looks at the guest’s name, mobile number, email, and previous damages in Truvi records. Guests do not fill out a Truvi form and do not leave your booking flow.

Screenings are free. Eligible approved stays can carry up to $50,000 of damage protection. The protection fee is $8.00 per night, collected at checkout — guest-pays or host-pays, your choice. Setup is account-wide under Host Dashboard → Settings → Trust & Safety → Damage protection.

Full walkthrough: Damage protection and the Damage protection FAQ.

Security deposits

A security deposit is a refundable hold on the guest’s card, not a charge at booking and not insurance. Stripe authorizes the amount a few days before check-in and releases it after checkout unless you file a claim from the reservation. Use it for small incidentals; use Truvi for damage that exceeds the hold.

Enable it in Edit Listing → Pricing → Security deposit.

Full walkthrough: Security Deposits.

Signed rental agreement

The rental agreement is the legal artifact — a markdown snapshot, signed in the guest portal once the stay is confirmed and paid, stored as a PDF with name, IP, and timestamp. It can run on its own or together with ID verification. Sensitive arrival details stay gated until the guest signs (and, if you required it, until they verify). The sign tile is hidden while a reservation is still awaiting approval or payment. Choose Right after booking under When do guests sign? to have Haven-site guests sign at checkout, on the Rental agreement tab of the pop-up that also holds your house rules and Terms & Conditions. They cannot pay, or send a request to book, until they have; otherwise they sign any time before check-in.

Full walkthrough: Rental Agreement & Digital Signatures.

Both the signed agreement and the ID check result can be written onto the reservation in a connected PMS, so you see them where you work and your PMS automations can act on them. Switch on Add Haven details to … bookings on the PMS card under Integrations; the PMS's own help article says where the details land (custom fields, booking attributes, info items, a note, or the PMS's own agreement status). Hospitable has no place for them.

Names of everyone staying

Every Haven checkout with more than one guest asks Who's coming?: a name and an optional email for each guest besides the booker. Travelers with an email are invited onto the trip once the booking is confirmed — see Who's coming? (travel companions at checkout).

To make the names required before a stay is booked, turn on Require the names of everyone staying under Settings → Trust & Safety → Guest verification, in the All listings box (/host?tab=trust&trustSub=verification). It is off until you turn it on, and applies to every listing on your Haven checkout.

With it on, every row on the card needs a name (infants are not counted); emails stay optional. Guests cannot pay, or send a request to book, until every row is named. The names show as Also staying on the reservation. Questions to you (inquiries) never ask for names, and a stay that already has them — a request named at booking, now paying through your link — is not asked again.

The switch changes checkout only. To collect names, arrival time or anything else after booking, use a guest form with a Guest names question — see Guest forms and polls.

Airbnb, Vrbo, and other off-platform stays

You can require ID verification, the rental agreement, and Screen & Protect on guests who booked somewhere else — Airbnb, Vrbo, a connected PMS, or any other synced channel. They complete those steps in the Haven guest portal, not on the OTA. A Haven booking website is not required.

In Edit Listing → Arrival → Guest verification, or Group site editor → Settings → Guest verification:

  • Also require the rental agreement on OTA bookings — imported reservations sign your rental agreement in the guest portal, through a personal link. Free.
  • Also require the ID check on OTA bookings — imported reservations pass the Stripe identity check in the guest portal. You pay the identity fee (there is no Haven checkout to bill the guest), and only after the guest completes verification.
  • Also run Screen & Protect on OTA bookings — Truvi screens from the synced guest data when the reservation arrives. You are billed per night for damage protection when the stay starts.

Each switch works on its own, so you can require the agreement on OTA bookings without the ID check, or the ID check without the agreement.

Those toggles only help if the guest actually opens the guest portal. Turn on Auto-send the guest portal under Edit Listing → Arrival → Guest portal access. Haven then delivers the guest portal at booking and again as a pre-arrival reminder — including guests whose reservation synced from another platform — and you can rewrite those two messages on the same page. You can also paste the guest portal link into Airbnb/Vrbo messages or print a QR code for in-stay.

Without auto-send or a shared link, off-platform guests never reach the guest portal, so they never complete ID verification.

See Guest Portal for how the guest portal is delivered.

How they work together

None of these tools files a claim in another. A typical stack for a higher-risk stay:

  1. Truvi screens at booking (and, if you opted in, on OTA bookings too — billed when that stay starts).
  2. The guest signs the agreement and verifies ID in the guest portal before codes unlock.
  3. A security deposit hold is placed before check-in.
  4. If something is damaged: capture the deposit first, then file a Truvi claim for the remainder.

Use only the layers you want. Turning one on does not imply the others.

New to Haven?

Everything in this guide, done for you

Haven is the direct booking platform these guides are written for — a branded site, secure payments, and guest relationships you own. Build yours free.

See how Haven works

Free to build · No credit card · Private until you publish