#nicolas-jardillier-kixell_api

1 messages ¡ Page 1 of 1 (latest)

abstract dockBOT
#

👋 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/1364869076740210770

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

static tiger
#

I don't see this paymentIntent in requies_action status, as you haven't confirmed it with a payment method.

#

Can you share with me the ID of the paymentIntent that's in requires_action status (e.g., 3DS was requested) ?

trim current
#

here the right payment intent ID : pi_3RHIkrBUEr7dv4pL0tjH7DKM

#

and log ID : req_K1fPIrBb7tb8iG

static tiger
#

Thanks. let me take a look

#

Yes, this payment intent is in requires_aciton status.

#

The card issuer determines whether a particular transaction needs to go through 3DS authentication, and there's no way to bypass it.

#

Your integration should handle this probably by sending your user to your webpage, and start the 3DS flow by calling stripe.confirmPayment().

trim current
#

ok, but the user has to go through the payment process again, is there a way to simply trigger the 3DS for the user without them going through the order funnel again ?

static tiger
#

What do you mean by "going through the order funnel again" ?

trim current
#

it's an annual renewal, I would like to avoid my users going back into a complete process in the order tunnel

static tiger
#

You mean complete the checkout again?

trim current
#

Last year the user successfully passed the 3DS confirmation, but this year's auto-renewal required the 3DS again, hence this discussion.

static tiger
#

I see. As I explained earlier, your integration should shoudl always handle the situation when a 3DS is requested.

trim current
#

yes but it happens in the background through API calls

static tiger
#

You can also consier using Stripe subscriptions for recurring payments, and let Stripe sends an email with the link to complete the 3DS authentication.

trim current
#

ok, is there any way to generate the link to complete the 3DS authentication

#

?

#

I mean in first step, without using Stripe subscriptions

static tiger
#

Pass a return_url to the PaymentIntent when confirming on the server, and redirect your customer to next_action.redirect_to_url.url. This is the link for them to complete the 3ds.

abstract dockBOT
trim current
#

ok thanks, I will check

formal pulsar
#

Hey, taking over here. Let me know if there's any follow-up Qs I can answer!

trim current
#

ok, Since everything is happening in the background, is it possible to generate this URL from my server to send it to the client by email?

formal pulsar
#

What URL exactly ?

#

You mean reading the url from the response next_action.redirect_to_url.url and send it to your client by email ?

trim current
#

yes

formal pulsar
#

Yes you can

trim current
#

ok I ll check, thks