#Max87

1 messages · Page 1 of 1 (latest)

blissful foxBOT
vague elm
#

Can you share an example seti_xxx?

vivid kite
#

just a moment

#

seti_1MWzuUHaE36FOhnywtr4bOxe

vague elm
#

Hmm, your integration flow is a little off-piste. Why attach a pm_xxx to the Setup Intent?

#

The idea is that you confirm the Setup Intent passing the collecting payment details from the front-end (Stripe.js) and then the successful Setup Intent created the pm_xxx

vivid kite
#

this flow works with dev env

vague elm
#

Well your flow can work, but it's not really the happy path. When you confirm it server-side like this, and the status returned is requires_action, 3DS was requested and requires customer input. You need to return the client_secret to the front-end and call confirmSetup

vivid kite
#

to be clear - our BE creates setup intent, FE creates payment method, then calls update_setup_intent and then calls confirm_setup_intent

vague elm
#

That way Stripe.js can handle the auth/3DS request with your customers

vivid kite
#

I can't use Stripe.js

#

Or Stripe SDK for mobile

vague elm
#

How do you plan on handling 3DS flows in these situations?

vivid kite
#

I thought that 3DS can be reason, there is three_ds_method_url but that url is not working

vague elm
vivid kite
#

we used all cards

vague elm
#

Then how did you handle the requires_action status?

vivid kite
#

I can show webview with 3d secure url to user

vague elm
#

Then do that. Details at the URL above

vivid kite
#

I'm missing 3d secure url to display

#

because next_action is not redirect_to_url but use_stripe_sdk

vague elm
vivid kite
#

okay, thank you. we need to make this changes on our BE, I'll let you know with updates