#cece_51221

1 messages · Page 1 of 1 (latest)

drifting vigilBOT
silver flume
#

Not as far as I know, though I would reccommend talking to our support team about your usecase to understand how you will be charged https://support.stripe.com/?contact=true

drifting vigilBOT
lime kite
lusty cobalt
#

HI 👋

#

I"m stepping in as @silver flume needs to go

#

If the card requires authentication for an off-session payment it will enter a state of requires_action and you will need to bring the customer on-session to complete the authentication. You can see a lifecycle of the Payment Intent here: https://stripe.com/docs/payments/paymentintents/lifecycle

lime kite
#

what do you mean by "bring the customer on-session"

#

for example, we notify customer the payment failed and ask them to retry checkout? Or do we send them an invoice?

lusty cobalt
#

The payment intent doesn't fail, they just need to be interacting with your GUI to complete the process.

lime kite
#

complete do you mean pop up authentication dialog so they can confirm? "enter code, etc"

lusty cobalt
#

It could be that but it depends on the issuing bank and what protocl they are using

#

Do you have an example Payment Intent ID I could look at?

lime kite
#

I see. I don't right now. We are still scoping our project. And I wonder if I need to scope in card authentication flow. Is card authentication only requiredt outside US? Do you know any card issuer requires auth for payment in US?

lusty cobalt
#

If by card authentication you mean 3DS, then it is entirely up to the issuing bank. We have seen some US cards require 3DS. However, if you follow either of our canonical examples for charging customers on-session https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements or saving payment methods for charging later https://stripe.com/docs/payments/save-and-reuse you will be in pretty good shape. Stripe Elements using Stripe.js will automatically handle authentication for you.