#ashar_best-practices
quasi karmaBOT
👋 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/1404693036855853060
📝 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.
- ashar_best-practices, 34 minutes ago, 8 messages
sacred osprey
hi there, give me a moment to take a look at your question 👋
storm ridge
Hi, The solution suggested in this thread #1404668958027812926 message seems isn't feasible, as the "request_three_d_secure" param is linked to subscription I think not the payment method
sacred osprey
Could you share with me the ID on an existing subscription that has "request_three_d_secure": "any" ?
storm ridge
sure sharing
cus_Sqr8alTDqxwsTt
sub_1Rv9aeJG0sbFhCDr9ZY0qy01
This is the test customer and subs I created, and tested the provided solution, but it didn't update the 3ds param, after re attaching the payment method
sacred osprey
I believe updating the subscription's payment_setting to "automatic" should work but I need to run a test first, give me some time 👍
storm ridge
I think this is restricted in update subscription params
https://docs.stripe.com/api/subscriptions/update
sacred osprey
What do you mean by restricted?
thank for waiting ; I finished my test and found that updating the existing subscription's payment_settings.payment_method_options.card.request_three_d_secure to "automatic" [0] does work.
And what I mean by "it works" is if your subscription is created with request_three_d_secure: "any" , updating it to request_three_d_secure: "automatic" will not trigger 3DS on future invoices after you make the change
storm ridge
What do you mean by restricted?
I mean't api wasn't allowing to update this param, when I last tested, but it seems you verified and it seems working, and you were able to update this param
sacred osprey
Hmm it does allow me to update it.
Could you try again and let me know if you run into errors
storm ridge
sure let me test it, and will update you here
sacred osprey
You can try updating sub_1Rv9aeJG0sbFhCDr9ZY0qy01 and I will be able to see it from our logs
let me know when you're done
storm ridge
sure
sacred osprey
looks like you managed to update it: https://dashboard.stripe.com/test/logs/req_Fnv9qrk2SxCP0D
storm ridge
yes I was able to update it without any error, I think there was some issue in the object structure I was passing maybe, as it seems while updating it we have to provide the nested obj, I'm not sure exactly what was the error I was getting at that time, but yeah it seems to be working now, and I'll investigate if I could reproduce that
Thanks for your help!