#wentaozhou

1 messages · Page 1 of 1 (latest)

lament joltBOT
wise sequoia
#

Hello! Do you happen to be using two different accounts for your live and test requests?

slender tree
#

it's the same stripe account just in different modes

wise sequoia
#

Gotcha - do you have the livemode PaymentIntent ID that's not giving you back charges?

slender tree
#

pi_3NVjp3JoLuBft2Ab1I9wk2SJ

wise sequoia
#

That PaymentIntent hasn't actually succeeded - that's why it has no charges

#

It's current status is requires_action

slender tree
#

hmm okay thanks. do you know why is that? what did I miss?

wise sequoia
#

That PaymentIntent requires authentication/3DS to be completed - you need to bring your customer back on-session so they can complete the auth process

slender tree
#

sorry I don't quite get it. is it because the parameter I pass in are wrong or ?

wise sequoia
#

No, this is a normal thing that happens and it's somethign you need to be resilient towards in your integration. Based on the PIs you sent over it looks like you're confirming server-side, which is fine in cases where no additional action is required. But for cards that require authentication to complete payment you HAVE to bring your customer back on-session and handle the next actions

lament joltBOT
slender tree
#

so I need stripe.handleNextAction to handle the case is that right?

wise sequoia
#

yup

slender tree
#

thank you very much!

#

do you know when it would require additional action? as it does not happen each time

rugged mist
#

👋 taking over here. In real world it's totally depends on the issuer banks

slender tree
#

hello?

rugged mist
#

Yes

#

I meant it's up to the issuer banks, so you wouldn't know when it would require actions