Guest Identity Verification

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 that builds on the existing Rental Agreement signature flow — you can pick how strict you want to be.

The three settings

You'll see one Guest Verification setting on each property (and on each Multi-Unit Site). Pick the level of friction that matches the booking:

Setting	What guests see
None	No pre-arrival gating. Check-in details unlock as soon as the booking is confirmed.
Rental agreement only	Guests sign your rental agreement before WiFi, lock codes, check-in, and host contact unlock. (This is the current behavior.)
Rental agreement + identity verification	Same as above, plus a quick Stripe-hosted identity check. We can also require a selfie that matches the ID.

The third option is gated behind a feature flag while it rolls out. If you don't see it yet, reach out — Haven admins can enable it on your account.

How identity verification works

Haven uses Stripe Identity. When a guest opens their guide for a booking that requires verification, they see a "Verify your identity" tile. Tapping it launches a Stripe-hosted flow where they:

Pick a document type (passport, driver's license, or national ID card).
Take a photo of the document (and a selfie, if the host required one).
Submit. Stripe verifies asynchronously and notifies Haven via webhook.

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.

Privacy & security

Haven never sees or stores the ID image. Stripe holds the documents on their side and auto-deletes them per their retention policy.
We persist only the verification status (verified / pending / rejected), the Stripe session ID for audit, and the rough document type.
Hosts see the status of each verification on the reservation drawer — never the underlying images.
Identity images and links are never included in any email.

Who pays for it

Identity verification carries a flat $4.99 per-booking fee (charged once per reservation, not per night). When you enable Rental agreement + identity verification, you choose who pays:

Who pays	Guest checkout	Your payout
Guest pays (default)	Line item "Identity verification (Fully refundable on cancellation)" at $4.99	No deduction — Haven retains the fee
You pay	No verification line item	$4.99 deducted from your payout

The fee is fully refunded if the booking is cancelled before check-in (returned to the guest in guest-pays mode, or back to your payout in host-pays mode). It is not refundable on or after check-in. You set who pays in the Guest verification card on each listing (or multi-unit site).

Multi-Unit Sites and inheritance

If a property belongs to a Multi-Unit Site, that site's Guest Verification setting 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.

Re-verification

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.

Admin override

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.

Rental Agreement & Digital Signatures — the signature half of pre-arrival gating, which Guest Verification extends.
Guest Portal — what guests see when all required steps are complete.