#valdo99
1 messages · Page 1 of 1 (latest)
Hi there!
If you want to collect payment information and do a payment later, you have 2 options:
- Save the card with a SetupIntent, and charge it later. In this case the bank may require 3DS for the SetupIntent and the payment itself.
- Place a hold on the card. In this case the bank may only require 3DS when placing the hold, but not when actually making the payment. However note that this only works if you know in advance the amount the user will pay, and it will only work once.
how can subscriptions elaborate payments recurrently ?
Well a subscription may require 3DS at any time. So that's something that needs to be handled. For subscription we have many settings in the dashboard for this
so what do you advise for the implementation of the payment? to send the 3ds check url to the user via sms ?
If you have a saved payment method, try to do the payment method off session.
- If it works: great!
- If not, you have to tell the user to go back to your website/app and go though the 3DS flow by confirming the existing PaymentIntent with https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-token
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!