You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the Authentication step is refused, after the customer is prompted to authorize a payment, then any other Stripe payment using SCA cards (x-3184 card) will fail, if these are coming from backoffice orders.
A payment is only possible with the x-4242 card (or other payment method).
Expected Behavior
After a failed Stripe-SCA backoffice payment, a second attempt with a different card should be possible.
Actual Behaviour
After a failed Stripe-SCA backoffice payment, a second attempt with a different card is not possible.
Steps to Reproduce
As an admin: Place an order in the BO selecting Stripe and introducing the card x-3184 card, with data 01/23 - 123.
As customer: receive the email and follow the link to grant authorization. Click "Fail Authentication"
As an admin: Notice the failed payment.
Repeat steps 1 with a different card, like card x-3184 card, with data 03/25 - 321; notice the same outcome.
Repeat steps 2 but click "Complete Authentication."
As an admin: Notice the failed payment. -> should be successful.
Repeat steps 1 with a non-SCA card, like card x-4242 card, with data 03/25 - 321; notice payment is successful.
Animated Gif/Screenshot
Workaround
Use a different payment method or a non-3D card.
Severity
bug-s3: a feature is broken but there is a workaround
Your Environment
Version used: v4.2.21
Browser name and version: Firefox
Operating System and version (desktop or mobile): Ubuntu 20.04
Possible Fix
The text was updated successfully, but these errors were encountered:
filipefurtad0
added
the
bug-s3
The bug is stopping a critical or non-critical feature but there is a usable workaround.
label
Nov 11, 2022
filipefurtad0
changed the title
[BO] Failed SCA payments after bank authorization refusal
[BO] Failed SCA payments after failing user authentication
Nov 11, 2022
Hi @filipefurtad0, I'm still learning how things work, and wondering does anyone need to be notified of this (eg #instance-managers)?
filipefurtad0
changed the title
[BO] Failed SCA payments after failing user authentication
[Stripe SCA] Failed SCA payments after failing user authentication
Nov 15, 2022
Hey @dacook,
Sure - please feel free to ask any time 👍 Also, do shout if you have any thoughts on how we could improve any of these processes.
does anyone need to be notified of this
Yeah, good point. I think the correct process would be to post this on #bugs channel. This one felt a little like an edge case, reason which I was not too loud about it. But still a good idea to post there. I've added it to a pre-existing epic too #8846 .
Description
If the Authentication step is refused, after the customer is prompted to authorize a payment, then any other Stripe payment using SCA cards (x-3184 card) will fail, if these are coming from backoffice orders.
A payment is only possible with the x-4242 card (or other payment method).
Expected Behavior
After a failed Stripe-SCA backoffice payment, a second attempt with a different card should be possible.
Actual Behaviour
After a failed Stripe-SCA backoffice payment, a second attempt with a different card is not possible.
Steps to Reproduce
As an admin: Place an order in the BO selecting Stripe and introducing the card x-3184 card, with data 01/23 - 123.
As customer: receive the email and follow the link to grant authorization. Click "Fail Authentication"
As an admin: Notice the failed payment.
Repeat steps 1 with a different card, like card x-3184 card, with data 03/25 - 321; notice the same outcome.
Repeat steps 2 but click "Complete Authentication."
As an admin: Notice the failed payment. -> should be successful.
Repeat steps 1 with a non-SCA card, like card x-4242 card, with data 03/25 - 321; notice payment is successful.
Animated Gif/Screenshot
Workaround
Use a different payment method or a non-3D card.
Severity
bug-s3: a feature is broken but there is a workaround
Your Environment
Possible Fix
The text was updated successfully, but these errors were encountered: