#ndbtss_unexpected
safe palmBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1319252674994241599
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- ndbtss_api, 16 minutes ago, 43 messages
- ndbtss_api, 2 days ago, 10 messages
grand copper
Just to clarify, we are not using Stripe’s subscription system. Instead, we have developed our own internal system for monthly renewals of licenses, and we use Stripe solely for processing the payments. Since we are not utilizing Stripe’s subscription feature, there is no Subscription ID to share.
Could you please advise on how to address the issue of 3DS validation being requested every month for the automatic payments, even though the card was configured to prevent this?
dark ginkgo
How are you collecting the PaymentMethod then?
grand copper
We are collecting the PaymentMethod by using a visual payment module provided by Stripe. The customer makes an initial payment via this module, and the card details are stored both with us and with Stripe for future payments.
like in the picture
dark ginkgo
Are you using SetupIntents, or PaymentIntents with setup_future_usage parameter? Otherwise, the resulting PaymentMethod is single-use.
grand copper
of course
dark ginkgo
Could you please share an example PaymentIntent ID that failed pi_xxx?
Is it happening for all customers?
grand copper
pi_3QXau5HagJ8u1cfk0sMn2oFm
yes, for all customers having a payment method that requires 3DS
dark ginkgo
Oh, it seems like you're missing off_session=true when charging the saved PaymentMethod again: https://docs.stripe.com/api/payment_intents/create#create_payment_intent-off_session
grand copper
Thank you for your suggestion.
Just to confirm, if we add the off_session=true parameter when charging the saved PaymentMethod, will the automatic payments work without requiring the customer to go through the 3DS validation process again, even though the card has already been saved?
I appreciate your help in clarifying this!
dark ginkgo
Yes.