#jeffreyb

1 messages · Page 1 of 1 (latest)

weary ventureBOT
lone glen
#

hello! can you share the two PaymentIntent ids where you've tried these cards?

silk lance
#

successful: pi_3LurmbRgMrSW9s0a16mjXcvf
failed: pi_3LuroMRgMrSW9s0a0AXniN6g

weary ventureBOT
vestal bolt
#

Looking into the sample Payment Intent now

#

In pi_3LuroMRgMrSW9s0a0AXniN6g, the payment failed because you set off_session: "true" which means the customer was not in session to authenticate

#

4000002760003184 always requires the card to be authenticated during a payment

#

If off_session is removed, it'll allow the customer to perform 3DS authentication

silk lance
#

pi_3Lus9vRgMrSW9s0a0strWoJ4 this payment intent is with no off_session and the status is requires_action even though I authorized it in the 3ds window

#

@vestal bolt do we need to create a new setup intent if we receive requires_action?

vestal bolt
#

For 4000002760003184 test card, it will require 3DS every time when it's used

silk lance
#

The initial 3ds window when creating a payment method. If I approve it there, shouldn't the payment go through?

vestal bolt
#

Not for this 4000002760003184 test card

#

4000002760003184 will require 3DS every time when it's used

#

When you use pm_xxx on PaymentIntent, it will trigger another 3DS as it is considered as a different flow

#

Both SetupIntent and PaymentIntent can trigger 3DS