#ashar_best-practices
uneven spadeBOT
👋 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/1404668958027812926
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
pure briar
Hi,
Following the mandates by the Japanese government, we implemented 3DS in our payment system. During implementation, we set "request_three_d_secure": "any" when creating new subscriptions, thinking it would be best to always request 3DS to avoid fraud.
After 2–3 months, we noticed a drop in subscriptions and revenue. Investigation showed this parameter caused 3DS to trigger for every renewal, even after it had been verified on the first payment. This led to high churn, as customers had to verify each month, and many missed it despite our reminder emails.
From the docs, I learned "automatic" (which is the default) is better since it only triggers when needed. We’ve updated our code for new subscriptions, but existing subscriptions still have "any" and this can’t be updated once created, due to the restricted param for subscription update api.
Is there any recommended way to handle this smoothly for existing subscribers so they don’t get 3DS requests every month?
old prism
So the request_three_d_secure parameter is tightly-coupled to the Payment Method, which is being used on your Subscription. You could consider collecting different Payment Method (but this time set request_three_d_secure = automatic ) and override it to the existing Subscriptions.
pure briar
So you mean we can prompt users to update their payment method for the current subscription, which would then set 3DS to automatic? Would this also work if the user re-adds the same payment method? (Asking in case the user only has one available payment method that’s already in use.)
old prism
Yes should work (please test the whole flow in Sandbox or Test mode)
pure briar
Got it, Thanks for your help, will test it out