#camsav_error
spice cragBOT
👋 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/1268944365724635146
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
icy jackalBOT
last obsidian
Hi there 👋 can you share the ID of a payment where you saw this behavior?
orchid rune
Yes pi_3PjMdOIyPS3WEOq00cHYQ6RA
This even happens when in test mode using the test cards
It happened after stripe sent an email about closing my account for high risk. I did appeal and they reactivated my account
last obsidian
I'd have expected you to see it before that too. It doesn't look like your integration is designed to set up the Payment Methods you create for future usage, so a 3DS challenge isn't surfaced to your customer when they're providing their card details.
You need to build a recovery flow for when these recurring payments fail due to the issuer requiring customer authentication be completed. You'll need to bring your customer back on session so they can complete that authentication challenge.
You can also make adjustments to your integration to reduce how frequently this behavior is encountered.
Do you always create your customer's Subscriptions immediately after collecting payment method details from them?
orchid rune
It only happens on the initial payment so I charge the initial payment of $2.95 and then after that is paid it then creates a subscription. But now every single initial payment of $2.95 which is a one time payment is now needing more verification which has never happened before.
To answer the question yes the subscription trial starts immediately after collecting payment method.
Its just weird because even the test cards are needing additional verification
Nothing has changed or have been updated. Its been running smoothly for 3 months.
last obsidian
Hm, the payment that you shared was the first Payment Intent created by a Subscription, that was automatically processed against the Customer's default payment method. I didn't see a separate Payment Intent at first.
You create a Payment Method from the Card Element (which doesn't set up the Payment Method for future usage):
https://dashboard.stripe.com/logs/req_HbogypmCxZblgm
Then create a Subscription for that Customer:
https://dashboard.stripe.com/logs/req_e4QMlO0E6y3c58
The issuer required 3DS be completed before they approve this transaction, which is typical. Since this is the first Payment Intent for a Subscription using a Payment Method that wasn't previously set up, we automatically set setup_future_usage to off_session to prepare the Payment Method for future payments for the Subscription. That setting tends to trigger 3DS requirements, so that future off-session payments can typically be exempted from needing that.
I'd need more information and examples of the before behavior you're referring to in order to get context on why you may have seen a change in behavior, but based on the integration pattern I'm seeing for your account I'd expect 3DS would be triggered pretty regularly. You'd see it for all transactions in the EU, and increasing number of US ones as 3DS adoption increases.
last obsidian
Depends on the test card
orchid rune
Ive tried multiple. Ive done over 700 transactions and never encountered this until after they reactivated my account
pi_3PjN9IIyPS3WEOq01J1kTDx8
for the basic test card
last obsidian
Hm, yeah, that doesn't look expected to me.
Checking one more thing that is coming to mind, otherwise I think this is something that will need to be discussed with our support team.
Okay, I'm not seeing a rule set up that is trying to always request 3DS, so I'm not sure why you're seeing this.
Based on that behavior and the pattern you described, I'd recommend following up with our Support team about this:
https://support.stripe.com/?contact=true
I'm not exactly sure what is going on, but it feels like there may be some setting on your account that is causing it to request these more frequently now, and if that's the case it's something our Support team would be more familiar with than my teammates or I in this forum are.
orchid rune
Okay I will contact them. I figured it couldnt of been something developer related as nothing has changed to the payment process. Thank you for looking into it for me