#Hellruba
1 messages ยท Page 1 of 1 (latest)
Hello ๐
What test card are you using?
Hello, i am using the following one: 4000002760003184
Can you share the SetupIntent ID?
also could you try a different 3DS card just to see if that triggers the same behavior?
4000002500003155
the setupintent id: seti_1LvL9U2SkO9a7OrGRDJ7WiVm and will try with that card ๐
had same behavior on that other card, but in the case i then update my payment method with that exact same card and goes through another confirmSetup with a setupIntent, the payment goes through and become succeed. It must come from my way to handle the first setupIntent when i then pass the payment to create a subscription?
Yeah that is possible. Taking a step back, what is your current flow?
Are you using SetupIntent API to save the payment method prior to creating a subscription?
Yes i am using the SetupIntent to save within stripe the payment method, i then pass the paymentMethodId to my flow in which i will create the related subscription to my customer
Gotcha. That might be the reason here.
Are you doing this because your subscription has a trial?
Doing this for the specific flow of how we handle the customers on our hands within our app mostly
Gotcha. Typically to avoid two 3DS auths with Subscriptions we recommend creating the subscription directly,
-
If the first invoice is of non-zero amount then you can use
subscription.latest_invoice.payment_intentclientSecret to render elements and allow customers to enter payment method details (as well as perform 3DS auth) -
If the first invoice is for zero amount (likely) due to trials then you can use
subscription.pending_setup_intentclientSecret to render elements and allow customers to enter payment method details (as well as perform 3DS auth)
https://stripe.com/docs/api/subscriptions/object#subscription_object-pending_setup_intent
The issue was the fact upon subscription creation, it ask again for an 3DS and the one made from the call confirmSetup wasn't considered so?
yeah I believe that's whats happening here
i see i will dig that up thanks ๐