nagenbgr-SCA-next-action | Stripe Developers | Page 1

hexed bobcat Mar 10, 2022, 5:17 PM

#

Hey there 👋
copying this here for full context

Can you please let me know if there are any guidelines available to get past this issue? PI: pi_3KbpBTKVpb0T87Xr0zW3jwAh. I also want to be able to test Refund after this. Thanks!!

#

Have you looked at this guide already? https://stripe.com/docs/payments/3d-secure#when-to-use-3d-secure

#

what is your integration currently doing?
I don't think you need to worry about next_action at all, if your integration just confirms a PaymentIntent client-side and that is it, Stripe.js will handle everything in that hash really so this isn’t an issue

quartz lantern Mar 10, 2022, 5:23 PM

#

Hi Hanzo - thanks so much: my integrations needs to do the full payment cycle: Create Payement/Refund/Return/Cancel for buyers in EU zone

hexed bobcat Mar 10, 2022, 5:29 PM

#

I see.
Like I mentioned earlier, Stripe.js really just handles it on its own so you shouldn't worry about the "next_action" object. All you need to do is just confirm the PaymentIntent client-side.

quartz lantern Mar 10, 2022, 5:34 PM

#

Got it - thanks. For refunds, is there any SCA enforced as well..?

hexed bobcat Mar 10, 2022, 5:42 PM

#

Refunds do not have SCA, no.

Ideally your flow would look something similar to the following;

Create a Payment Intent
Confirm it client-side
If/When 3DS is available, Stripe.js will automatically take care of redirecting the user to bank's website and bring them back to the return_url
That's it 🙂

#

You can read about it more here https://stripe.com/docs/payments/3d-secure

#

oops that's the wrong link
here you can read more about PaymentIntents https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements

#nagenbgr-SCA-next-action