neildt_42592

[tame knoll]

hi! well a SetupIntent is not for a specific amount.

You can do auth-and-capture to hold a specific amount and capture within 7 days(like hotels holding an amount for damages). https://stripe.com/docs/payments/place-a-hold-on-a-payment-method

If you save a card now and charge it a year from now, that may or may not require 3D Secure, it's up to the bank. The happy path is that you use a SetupIntent now and the future off-session, merchant-initiated transaction you do next year is exempted. https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements#charge-saved-payment-method

[clear venture]

Yes, the website we are developing is for hotels. For example a guest makes a booking today, checking in on 22nd Nov 2024. We need to take full payment two days before the arrival on 20th Nov 2024.

The issue we have with merchant-initiated transaction is that the hotel is open to charge back, but at least if the transaction is 3d secure we have better case to answer

[tame knoll]

don't you mean the customer would chargeback?

but yes, if you do an off-session payment on the saved card, that does not have the liability shift of 3D Secure. If you want that, then you can contact the customer and bring them back on-session, and force a 3D Secure transaction on the saved card for the payment. https://stripe.com/docs/payments/3d-secure#manual-three-ds

[clear venture]

Yes, in some cases we have seen customers be successful in chargeback, which is why we'd want 3d secure transaction where possible

So as it stands, we'd need the customer to come back to our platform and make the payment