Problem statement
- Security deposit settings currently apply at the property level across all channels
- Hosts cannot enable deposits for Direct bookings while disabling them for Airbnb bookings
- Different platforms have different guest vetting processes, but Hospitable treats them the same
Current workaround
Hosts must choose between:
- Enabling deposits for all channels (including Airbnb where guests are already vetted), or
- Disabling deposits entirely (leaving Direct bookings unprotected)
Impact
- Airbnb guests push back when asked for security deposits, as they don't expect this requirement on a platform that already vets them
- Creates friction and complications with experienced Airbnb guests who are unfamiliar with off-platform deposit requests
- Hosts assumed the security deposit feature was designed for Direct bookings only
- Forces hosts to either over-secure (annoying vetted guests) or under-secure (risking Direct booking properties)
Proposed solution
Add per-platform security deposit controls, similar to how pricing can be managed differently per channel. Hosts should be able to:
- Enable security deposits for Direct bookings only
- Disable security deposits for Airbnb (or other OTA channels)
- Set different deposit amounts per platform if needed
Unlock
- Hosts can protect Direct bookings (unknown guests) while maintaining a frictionless experience for vetted Airbnb guests
- Reduces guest confusion and pushback
- Aligns security deposit strategy with the actual risk level of each booking channel
- Provides the same flexibility for deposits that already exists for pricing