henryd

[gusty summit]

Hi 👋

So you are using the Stripe3dsConfig to set the Timeout to 5 minutes?

[lapis timber]

It's by default 5 minutes

According to the sdk docs

[gusty summit]

And what is the. behavior you expect but are not seeing?

[lapis timber]

I'd like to know what will be the status of the payment after the timeout is reached. Doc don't specify that, I'm guessing the payment intent will be marked as failed or something like that

[gusty summit]

Nope

It will remain in requires_action

[lapis timber]

So the timeout is only for a UI thing?

[gusty summit]

No wait, sorry the payment intent should fall back to requires_payment_method

We cover the lifecycle of the Payment Intent here:

https://stripe.com/docs/payments/intents

[lapis timber]

Got it, thanks for the info. So just for confirming, this expiration scenario for 3ds2 cannot be tested on sandbox, right?

[gusty summit]

What do you mean "on sandbox"?

[lapis timber]

I mean, testing environment with testing credentials

https://stripe.com/docs/payments/3d-secure#three-ds-cards

[gusty summit]

You should be able to. Are you not seeing the Payment Intent change state?

[lapis timber]

Nope, I don't see the authentication screen been auto dismissed either (android sdk)

[gusty summit]

Oh, I think this is due to the test integration using a mock page and not actually communicating with issuing banks

I do not think our mock page simulates timeouts: https://stripe.com/docs/payments/3d-secure#three-ds-cards

but I can raise this as a feature request