#ziwengames

1 messages · Page 1 of 1 (latest)

dark siloBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

smoky nexus
#

It's recommended because it can complete authentication flows, but not strictly necessary

hard lodge
#

If there is an authentication flow necessary, where in the code would this be shown? Suppose I'm using stripe.confirmSetup()

smoky nexus
#

It would happen then, if required

hard lodge
#

To clarify, what would be returned (or where in the code would this be specified) so that the developer would know when to handle the extra flow?

#

Like suppose the action is that the user fills out the credit card details and clicks a button which triggers stripe.confirmSetup()

#

On the documentation, I see that they might be redirected to a different page, which is one case. Are there other cases that could happen that aren't redirects?

smoky nexus
#

Yes, 3DS for cards appears as a modal/overlay, automatically handle by Stripe.js

hard lodge
#

Ah I see, so then if I don't use a setupIntent, would this not pop up/would the card likely be declined?

smoky nexus
#

If you collected the card without authentication its likely to require that during a later payment

#

Which would require getting your customer back on session

hard lodge
#

Ok I see, i didnt account for the extra flows.

  1. What if I am confirming a paymentIntent on the backend and the 3DS is supposed to pop up? Does it return me a specific response telling me I need to do this client side?
  2. Is it suggested to confirm a paymentIntent on the frontend?
  3. Based on the documentation, setup/payment Intents on the frontend seems to have 2 different extra flows: 1 that redirects and 1 that pops up as a modal. What about these processes in the backend? I see that the Pi.confirm() function may return different next_action keys. Would I have to case on this to handle each separate case?
smoky nexus
#
  1. If 3ds is required, the payment will either move to requires_action for you to handle, or decline if you've indicated a off_session payment
#
  1. You should confirm via payment intent or setup intent the first time with the customer on session, later payments can be off-session/server-side
#

3/ is the same as 1/, mostly

#

you end up with requires_action that you need to handle client side

hard lodge
#

Ok I see

smoky nexus
#

That's the doc that explains how this works and what to do when needed