I think there's a similar request elsewhere, but the problem here is that the credit cards that get passed-through from channels aren't eligible for 3d secure because the checkout workflow loses the guest.

You'd have to not automatically process the pass-thru credit cards and then separately invoice each guest.

This would make the 3ds workflow present to the guest - you may also want to enable radar and create a rule to only allow transactions with liability_shift.

This may solve your problem as the pass-thru cards should get rejected by stripe. .

I want 3DS2 to be applicable for all Stripe transactions.

Here's how to setup payment methods for vebo

I've yet to figure out how to turn off the “pay now” option but I think there is a way to do that

For now we check each payment on stripe to see if it has 3d secure. If not we verify the is provided by the guest and do some investigating. Not ideal but so far effective in avoiding chargeback

https://help.hostfully.com/en/articles/4446365-vrbo-invoice-payment-methods

I had the same issue. I did a lot of investigating .

The only way to do this in a way that's compliant is to disable passthrough payments and collect the payment directly from the guest

As it is, when VRBO or booking passes a reservation they send along the credit card data which gets sent to stripe

Because the authenticity of the customer entered data is lost (entered on vrbo but processed by Hostfully) it no longer carries the liability shift.

In order to be compliant the guest has to enter their card info onnhostgully so that the merchant bank can do their verification (sometimes requiring the cardholder to log in or provide two-factor authentication or something else that assures the card information is being used by the authorized cardholder)

I don't believe any form of passthrough processing would ever comply

This does add friction to the booking process as guests would have to know to watch for an email from us with a payment link and have to enter their card data yet again

Ultimately, though, this protects both the card holder and the pm. So it's a workflow we are implementing.

We won't accept any payments that do not have liability shift.