#jcs_api
crimson gyroBOT
👋 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/1295476929784189001
📝 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.
- jcs_card-element-3ds, 2 hours ago, 48 messages
bitter shuttle
from my developer - we figured out 3ds but had some questions
do some 3DS card require confirmation every payment?
pallid basaltBOT
sharp ferry
Hi 👋 in practice no, but you should always be prepared to handle a 3DS challenge for any payment. It's up to the issuer to decide whether they will require customer authentication for a particular transaction, so you should be prepared for that being the case as neither you nor Stripe can prevent that.
bitter shuttle
I'm relaying between my developer but have another question
So we're doing a 7 day free trial, and then we're billing them if they dont cancel after day 7
is the 3ds a big issue with this kind of setup, are we supposed to charge like $0.01 to make sure the card is good? or the way we have it setup is kinda the best you can do
sharp ferry
I'm not really sure how you have it set up now.
Are you actually creating a Subscription object in Stripe with a 7-day trial?
bitter shuttle
Yes that's how we've built it
sharp ferry
Then using the pending_setup_intent that the Subscription generates to collect payment method details is the best approach.
https://docs.stripe.com/api/subscriptions/object#subscription_object-pending_setup_intent
You can use that Setup Intent with this flow to collect payment method details and prepare the Payment Method for future usage:
https://docs.stripe.com/payments/save-and-reuse?platform=web&ui=embedded-form
You should still be prepared for any recurring payment to require 3DS though, as that can still happen if the issuer decides additional customer authentication is required.
