#agu-setupintent-3ds
sharp ether
@empty minnow even if SetupIntent succeeded, it's always possible for the bank to still require 3DS on the next payment. You are likely using a test card that always needs 3DS. Look at the test card in https://stripe.com/docs/testing#regulatory-cards instead
golden verge
Yes, if you are planning to collect a payment right away you should not use a setup intent, you should use a payment intent with setup_future_usage instead
Like detailed by this guide: https://stripe.com/docs/payments/save-during-payment
empty minnow
Ok Thanks for the answer!! But.. I have one more question.. @sharp ether said that "it's always possible for the bank to still require 3DS on the next payment." And I was wondering if the recurring payments will be affected by that rule. 👀
golden verge
Yes, recurring payments are also subject to that. Every payment is. A bank/issuer can choose to decline or require authentication for any payment at their discretion.
The docs for that and how to handle it are here:
https://stripe.com/docs/billing/subscriptions/webhooks#action-required
https://stripe.com/docs/billing/subscriptions/overview#requiring-3ds-payment
By far the simplest option is to allow Stripe to manage this for you automatically:
https://stripe.com/docs/invoicing/automatic-collection#secure-payments
empty minnow
Thanks! I will read it 🙂