Join our new community forum for support & discussionJoin Now
Home › Support › Extensions › Bookings › Booking, turn off the unpaid option
Booking, turn off the unpaid option
In the booking extension, I realized that whenever someone books a listing, the dates get blocked, regardless if the customer paid it or not. This seems to be a security issue, as a malicious customer can book several bookings and block an entire calendar.
Of course, I set the limit day for a booking to get paid to 1 day, but I wish that every booking should get paid immediately, otherwise, they will be deleted. Is this request present with your system. If not, would you be able to implement it? Thanks in advance.
There’s no such feature yet, but thanks for your suggestion, seems like a useful option for the next update. At the moment, the unpaid bookings are reserved anyway in case if there was some issue with the transaction (e.g. if it’s declined, and the customer has 24 hours or more to resolve the issue – it works this way on Booking.com and Airbnb).
Hmm, I didn’t know that Airbnb uses this feature. Though for this case, wouldn’t that become a security issue? A malicious buyer can reserve all the days everyday and prevent a seller from getting customers. I think there should at least be a limit on how many times a buyer can make unpaid bookings. If you decide to implement this feature, is it possible if you can give me an estimate time?
Thanks a lot for your quick response btw.
I’ll update Bookings as soon as possible (there are many feature requests already) and this option will be added for sure, the current ETA is 1-2 weeks. Please try setting the minimum time period for now (1 day), and if there are spam bookings you can consider enabling reCaptcha for the registration & booking forms.
Thanks a lot man for the help. Though one last thing, Airbnb allows sellers to require an ID from the buyer. Can you enable the same functionality if that’s fine? When a buyer provides his ID, it will be held in my database. In case if there is a serious dispute, I can provide the buyer’s ID to the seller. Of course, I’ll be handling sensitive data in my wordpress, but I am willing to take the liability.
Sure, you can try using a custom Attachment attribute for this, and don’t assign it to any display areas so the attachment will be hidden on the booking page (as a site admin you’ll be able to check IDs in the media library). But storing IDs may require some extra steps for security and compliance with GDPR.
That sounds great, though instead of requiring an ID for every buyer, is it possible to require an ID only when the buyer books with a seller that require an ID? I don’t want people to think I’m the one requiring an ID, and the seller is the one to blame :). I think this system is the same in Airbnb.
Yes, but this would require custom implementation (showing/hiding the ID attachment field depending on the host’s choice in the booking settings). At the moment if you add a custom attachment field it’ll be added to all bookings.
Hmm, so will you be able to add this feature if it requires a custom implementation?
It may eventually be added to the future Bookings extension versions, but if it’s urgent or some extra functionality is required for your site you can send a request for customizations and we’ll try to estimate the time/budget https://hivepress.io/customization/
This forum has been archived and is no longer accepting new posts or replies. Please join our new community forum for support & discussion.