Settings and activity
309 results found
-
6 votes
Keith
supported this idea
·
-
4 votes
An error occurred while saving the comment -
8 votes
An error occurred while saving the comment Keith
commented
I think this is supported already.
I have this enabled in my stripe.. I pay extra for radar and have the following radar rules:
Request 3DS if 3D Secure is recommended for card
Request 3DS if 3D Secure is supported for cardAllow if payment matches one or more values in default Stripe allow lists
Allow if payment is not high risk, is authenticated with 3D Secure and has a liability shiftI have deactivated ALL other rules including the risk_score ones.. Since doing so have had 0 chargebacks.
Only a couple times were legitimate bookers stopped and they used a different card which supported 3dsecureKeith
supported this idea
·
-
10 votes
This will be available in the v3 version of the page, coming soon.
Keith
supported this idea
·
-
37 votesKeith
supported this idea
·
-
3 votesKeith
supported this idea
·
-
4 votesKeith
supported this idea
·
-
5 votesKeith
supported this idea
·
-
2 votes
An error occurred while saving the comment Keith
commented
it seems easy enough to add a "lenght of stay" range in the "taxes and fees" creation.
Some municipalities it's even more complex. there are some taxes/fees for 14 days others for up to 30, others for HOA fees that only apply to stays less than 6 months, etc...
To make things more complex there are some fees that CANNOT be passed to guests but need to be accounted for in the host revenue report
(example, Berkeley, California has an additional 2% STR fee that hosts have to pay but CANNOT pass on to guests), but it needs to be presented as a fee in the owner statements. -
9 votes
An error occurred while saving the comment Keith
commented
i don't want this.. I may be deactivating a listing from a channel for various reasons but need to uphold the existing bookings and deal with them.
I'm not sure this makes sense in most cases. safer is to just manually delete the bookings that are left behind, no?
-
13 votesKeith
supported this idea
·
-
37 votesKeith
supported this idea
·
-
10 votesKeith
supported this idea
·
-
2 votes
An error occurred while saving the comment Keith
commented
can't you do this with your custom html header/footer area.. maybe this is only available for whitelabeled, but this is where we have a menu that hosts use to go wherevr they need.
-
4 votesKeith
supported this idea
·
-
21 votes
An error occurred while saving the comment Keith
commented
while it's not exactly the same, why not collect 1% at reservation.. the lost stripe fees will be minimal vs the lost time and money from having to deal with collections or no-pays.
Keith
supported this idea
·
-
25 votesKeith
supported this idea
·
An error occurred while saving the comment Keith
commented
YES.. and even now the "re-book" function is broken and we have to manually copy all the guest info to a new booking ourselves.
This is basic returning customer functionality that absolutely should work
-
6 votesKeith
supported this idea
·
-
30 votesKeith
supported this idea
·
An error occurred while saving the comment Keith
commented
This is a complaint airbnb has from non channel manager hosts. I thought they fixed it, but there didn't used to be an easy way to tie a resolution center transaction to a specific booking.
I think there is now, so hopefully it's available though the resolution center api, but we need this info for both debits and credits.
-
45 votesKeith
supported this idea
·
agree.. the commission rate should stick with the commission at the time the booking money was handled.
I can see some challenges here.. does the commission change on a given date? does it apply to existing future bookings or just new bookings?
I think this is a bit of a complex task.
We do our own owner billing so we handle this in our system, and once a booking is processed it's commission rate is computed then and not recomputed later.
not sure how hostfully would manage this for a wider variety of use cases.