#Joby - SetupIntent

1 messages · Page 1 of 1 (latest)

dire sonnet
#

Hi there!

#

Do you mean that the SetupIntent succeeded, but then later when you create a PaymentIntent it requires 3DS?

woeful saffron
#

Yes, the SetupIntent succeded but when trying to use the payment_method from from the SetupIntent in a PaymentIntent with confirm = "true", it complains "require_source_action"

#

Thanks for quick response.

#

Please note that this is in test mode with the fake 3-d secure during the setup

dire sonnet
#

Got it, then this can happen yes. It's complete up to the bank to require 3DS or not. So even if the 3DS is Successful, you might still need to go though 3DS for the PaymentIntent.

woeful saffron
#

Our intention is to charge the customer later (when the customer is not online)

dire sonnet
#

Yes I understand, but a 3DS may still be required.

woeful saffron
#

Do you mean by invoking a user action (via emal or something)?

dire sonnet
#

If 3DS is needed, you need to bring your customer back to your website/app and go though the 3DS flow.

woeful saffron
#

Thanks for the clarification. I am still a bit puzzled. I am using my personal 3d secure card for several online services which collects money without sub sequent action from my side. E.g. Office 365.

#

Or should I be creating a charge directly instead of paymentintent with confirm=true?

dire sonnet
#

I'm not saying that you will always need to go thought 3DS, I'm saying that it may happen, it's completely up to the bank to decide this.

#

Or should I be creating a charge directly instead of paymentintent with confirm=true?
No, charge is an old API, we recommend using paymentintent.

woeful saffron
#

I see. So it might fail randomly so we should always be prepared to bring the user in if the situation demands?

#

Which we are, but I just wanted to know if there is anything I should have done to eliminate this issue.

dire sonnet
#

I see. So it might fail randomly so we should always be prepared to bring the user in if the situation demands?
Yes, you need to take that scenario into account to handle it when it happens.

woeful saffron
#

Good to know, thanks for your help. We will try this in production with real cards.