#zzking

1 messages ยท Page 1 of 1 (latest)

unborn flintBOT
granite siren
#

Hi there!

#

Once the SetupIntent is successful, you get a PaymentMethod you can reuse.
Every time you reuse the PaymentMethod, the payment may require 3DS (if the bank request it) or the payment may fail (because of insufficient fund).

#

If it requires 3DS, then you need to ask your user to come back to your website/app to go through the 3DS flow. If the payment failed for any other reason, you can retry later.

serene anvil
#

all right thanks, I take it as "customer just need to put more fund into the card, thus there is no need to re-authenticate the card" in the case of "insufficient fund".๐Ÿ‘

What about the situation when " the card expires , and later the customer get a new card with the same card number, but new expiration date , cvc code, etc" ? Would the payment method (card) require a new 3DS authentication ?

granite siren
#

all right thanks, I take it as "customer just need to put more fund into the card, thus there is no need to re-authenticate the card" in the case of "insufficient fund".๐Ÿ‘
Correct! But like I said, the bank can at any time request 3DS. So you still need to take that into account in all your scenarios.

#

the card expires , and later the customer get a new card with the same card number, but new expiration date , cvc code, etc" ? Would the payment method (card) require a new 3DS authentication ?
I think it depends on the banks. You could get a card expired decline, and need to re-collect a brand new card from the user. Or the payment may work. And again, 3DS may or may not be requested, it's up to the bank.

serene anvil
#

hmmm OK, another question ๐Ÿ™‚ : once the "status" of setupIntent is "succeeded", would it be possible for it to change back to "requires_action", "canceled" , or any other non-succeeded status ?

granite siren
#

No sorry if I wasn't clear. Once the SetupIntent is succeeded it stays succeeded and you get a PaymentMethod. From that point you can ignore completely the SetupIntent and only use the PaymentMethod that was generated. And that PaymentMethod, every time you reuse it, may or may not require 3DS.

serene anvil
#

Ok thanks, I understand the part that it may or may not trigger 3DS when i reuse the card that has been setup successfully .

I guess what I'm asking is: is there a way to tell wether if I should re-collect the card from the customer and thus re-create the setupIntent, based on the payment error that is received ? (e.g: "insufficient fund" is Ok, no need to re-collect the card, but "card expired" would need a re-collect )

granite siren
unborn flintBOT
serene anvil
#

no problem. Yeah that is indeed a tricky question ,

Do you know if it's possible to trigger situation such as "the card needs authentication/3DS to setup, and then get declined for later payment due to it's expired" ? I checked this list here: https://stripe.com/docs/testing#authentication-and-setup , seems can't find it.

Use test cards to validate your Stripe integration without moving real money. Test a variety of international scenarios, including successful and declined payments, card errors, disputes, and bank authentication. You can also test non-card payment methods.

granite siren
serene anvil
#

OK, np , thanks for the support