Conditional security deposits based on guest count

Problem statement

• Hosts cannot set different security deposit requirements based on the number of guests in a booking
• Currently, deposit settings apply uniformly regardless of booking size or guest count

Current workaround

• Hosts must either require deposits for all guests (creating friction for smaller groups) or forgo deposits entirely (increasing risk for larger groups)

Impact

• Larger groups inherently carry more risk (more wear and tear, higher chance of issues), but hosts cannot adjust deposit requirements accordingly
• Hosts lose flexibility to balance guest experience with property protection

Proposed solution

• Allow hosts to set conditional security deposit rules based on guest count (e.g., require a deposit only for bookings above a specified number of guests, with a customisable threshold and deposit amount)

Unlock

• Hosts could tailor deposit requirements to the risk level of each booking
• Better protection for larger groups while maintaining a frictionless experience for smaller bookings