React-stripe-elements: Using card 4000000000003220 doesn't trigger 3d secure modal after page refreshing.

[vvitto]

I have weird behaviors using card with 3d secure 2 . When i invoke handleCardAction, not clicking any buttons in the modal, then do page refresh and invoke handleCardAction again, it doesn't show me any modal window with 3d secure again. It works properly with other kinds of cards.

I mentioned that these two cases have different next_actions object structures in returned paymentIntent.

1 Case with reloading:
"next_action": { "type": "use_stripe_sdk", "use_stripe_sdk": { "type": "stripe_3ds2_challenge", "stripe_js": { "three_d_secure_2_source": "...", "directory_server_name": "visa", "server_transaction_id": "...", "acs_transaction_id": "...", "acs_url": "https://hooks.stripe.com/3d_secure_2_test/challenge", "three_ds_optimizations": "" } } },

2 Case without reloading:
"next_action": { "type": "use_stripe_sdk", "use_stripe_sdk": { "type": "stripe_3ds2_fingerprint", "three_d_secure_2_source": "...", "directory_server_name": "visa", "server_transaction_id": "...", "three_ds_method_url": "", "three_ds_optimizations": "", "directory_server_encryption": { "directory_server_id": "...", "algorithm": "RSA", "certificate": "-----BEGIN CERTIFICATE-----...-----END CERTIFICATE-----\n", "root_certificate_authorities": [ "-----BEGIN CERTIFICATE-----...-----END CERTIFICATE-----\n" ] } } },

[asolove-stripe]

Hi @vvitto: thanks for filing, we definitely understand this is a painful problem. We are working on a fix. Note that this problem only occurs in testmode, so live payments aren't having this problem!

[CarlosTrapet]

I've had this scenario too, where the structure of next_action changes (apparently randomly) like @vvitto mentioned. Not sure if this is intended behaviour, but I fail to see what would be the trigger for the different responses.

[dweedon-stripe]

Hi @CarlosTrapet @vvitto,

We just rolled out a fix for this bug.

@CarlosTrapet: This is the intended behavior, but you should not base any business logic off of what is in the use_stripe_sdk hash. This is considered private data and we make no guarantees that it we won't change its shape.

[DaniSido]

Hi, any updates?

[dweedon-stripe]

Hi @DaniSido are you seeing this today? This was fixed months ago.

[Nek-]

What is actually fixed ? I also just saw it. Still only in test mode?

[naliva]

the issue remains in live mode. (no popup for 3ds authentication after calling handleCardAction()).
"use_stripe_sdk": { "type": "stripe_3ds2_fingerprint",
this was payment intend param when no-popup. the payment itself has been marked as 3dsecure authorised.

[robz-stripe]

Reopening this since we have a couple of reports of it still occurring.

[dweedon-stripe]

the issue remains in live mode. (no popup for 3ds authentication after calling handleCardAction()).
"use_stripe_sdk": { "type": "stripe_3ds2_fingerprint",
this was payment intend param when no-popup. the payment itself has been marked as 3dsecure authorised.

@naliva this is expected to happen sometimes in livemode. Sometimes the bank approves the payment after the "fingerprint" step without requiring us to present a 3DS challenge. This is why the payment is marked as 3dsecure authorized.

@Nek- did you see this happen in testmode?

[sashko-stripe]

Closing this as this project has migrated to React Stripe.js. If you believe this is still important, please re-open it there.