#II0071-setupattempt-thread

1 messages · Page 1 of 1 (latest)

hallow swan
#

Hi there! Go ahead and ask the question here and I would be happy to help.

dark lake
#

In my payment_intent I get the status: "requires_source" for a test 3D auth card. It is suppose to be "requires_action", right ?

hallow swan
#

Hmmm can you share the PaymentIntent ID where you are seeing that?

dark lake
#

when I check my api version, I have 2020-08-27

hallow swan
#

It should be requires_action if 3DS has been triggered, yes.

dark lake
#

pm_1LAgZzKZEpng7hVcPTzxJ3OI

#

oups wrong

#

pi_3LAyqDKZEpng7hVc0Gno0eRx

hallow swan
#

Thanks! Server is a bit busy so give me a moment, but taking a look.

#

Okay okay actually looking now 🙂

#

Okay so I see the confusion

#

You created that PaymentIntent with off_session: true

#

In this case, if 3DS is required, we decline with authentication_required since your customer is not on session to actually attempt 3DS.

#

When this happens, you would need to bring your customer back on session and either re-confirm the PaymentIntent using the same paymentmethod and use Stripe.JS to handle 3DS (or confirm server-side and not pass off_session: true), or you would collect new details and confirm.

dark lake
#

Yeah, off_session is always gonnna be true in our case. So I Could sent a email to the customer to bring him back to session and then use stripe.confirmPayment on the failed paymentIntent

hallow swan
#

Yep that is the best way to handle these cases.

#

How are you collecting cards initially?

#

Are you using setup_future_usage or a SetupIntent?

dark lake
#

SetupIntent

hallow swan
#

Okay good.

#

Then most times the card shouldn't require 3DS on these off_session charges

#

But it is definitely still possible so you should be prepared for it

dark lake
#

I see. Thank you! I might have more questions later but for now Im good.