#nicolas
low bluff
hot swallow
Hey there
Threads get archived after they are inactive for some time
I believe you were chatting about a 3DS issue?
Do you have an example PaymentIntent or Charge I can look at?
magic spade
I'm not sure there is one. I'm taking back this project, and I'm browsing the code, + I don't much about the technical implementations of Stripe
Searching for PaymentIntent or Charge doesn't return anything
What is the best way to send you code ?
hot swallow
Do you have access to your Stripe Account?
You could filter your payments for "3ds" to provide an example
Otherwise you can post your code here between three backticks like this
hot swallow
Okay thanks
magic spade
Thank you
hot swallow
So looks like you are using stripe.createPaymentMethod or the PaymentRequestButton to create a PaymentMethod then pass it to your backend
So yeah that's why 3DS isn't handled
Are you using Trials at all for your Subs?
hot swallow
Yes it does
magic spade
But it works ? We have subscriptions
hot swallow
So with trial Subs the Subscription will have a pending_setup_intent (https://stripe.com/docs/api/subscriptions/object#subscription_object-pending_setup_intent). After you create the Subscription you want to pass the pending_setup_intent.client_secret to the frontend and use stripe.confirmCardSetup to confirm the SetupIntent. At that point we will run a check with the issuer and if they want 3DS it will be automatically handled.
magic spade
Could it convert more using 3DS ?
hot swallow
That said, the issuer can always not want 3DS at that point and force 3DS later on actual payment. So you will also want to have the ability for your customers to come back on session to complete 3DS if the actual payment requires 3DS.
hot swallow
Could it convert more using 3DS ?
Yep
Would definitely recommend updating your integration to support 3DS
magic spade
We may use Stripe Checkout to simplify the process and ease the checkout evolution
Would you agree on these arguments?
hot swallow
Yep Checkout is a great way to go and will handle all of this for you
You still will want to implement a way to bring your Customer back on-session to complete 3DS if necessary
As issuers can force 3dS at any point
But just having Checkout handle stuff up front will reduce most of these 3DS declines
magic spade
All the 3DS would be handled by Stripe Checkout ?
As we delegate personal and card information to that page ?
hot swallow
Yep 3DS will be handled up front if the issuer requests it initially.
As noted above, it is always possible that the issuer doesn't request 3DS when the card is set up to be used in the future, but then does request it on the actual payment after the trial, but that is not super common.
magic spade
Ok
Still it be managed by Checkout, but should be managed/catched on our side to cancel the subscription if needed ?
hot swallow
Not sure exactly what you mean by that?
magic spade
I was reacting to this phrase "You still will want to implement a way to bring your Customer back on-session to complete 3DS if necessary"
hot swallow
Gotcha, yeah Checkout doesn't handle that. It will only handle the initial set up of the Subscription/PaymentMethod. An easy way to accomplish what I'm noting above is to simply use your Subscription Settings to actually email your Customers if 3DS is required. You can find the Settings for that in your Dashboard here: https://dashboard.stripe.com/settings/billing/automatic
magic spade
Ok, thanks a lot. I’ll dive in all the links you have next week.
Thanks again for your time to help
hot swallow
Happy to help
magic spade
Will this thread be kept somewhere for me to get back to. Or will it be deleted ?
hot swallow
It will be archived but you can still refer back to it
magic spade
Ok thanks