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
When trying to pay for a subscription with DCC using a credit card number that doesn't permit vaulting (for instance, any card from the CC generator), the order is not allowed to continue (which was fixed in #308) but for some reason the whole cart is cleared, which can result in a bunch of strange errors should the user attempt to re-submit the form.
Go to Checkout and enter the previously generated card details.
Click "Place Order".
Confirm that placing order fails because the method wasn't stored in the vault correctly.
Click "Place Order" again to see a weird error message.
Refresh the page and see the cart has been emptied, preventing users from re-attempting payment.
Screenshots
Screencast:
Expected behavior
Users should be allowed to use other CC details to complete payment. Card shouldn't be cleared.
The text was updated successfully, but these errors were encountered:
isabellainpsyde
changed the title
[RC] When paying for a subscrition and vaulting fails, cart is cleared
[RC] When paying for a subscrition and vaulting fails, cart is cleared (423)
Nov 17, 2021
jorgeatorres
changed the title
[RC] When paying for a subscrition and vaulting fails, cart is cleared (423)
[RC] When paying for a subscription and vaulting fails, cart is cleared (423)
Nov 17, 2021
Describe the bug
When trying to pay for a subscription with DCC using a credit card number that doesn't permit vaulting (for instance, any card from the CC generator), the order is not allowed to continue (which was fixed in #308) but for some reason the whole cart is cleared, which can result in a bunch of strange errors should the user attempt to re-submit the form.
To reproduce
Screenshots
Screencast:
Expected behavior
Users should be allowed to use other CC details to complete payment. Card shouldn't be cleared.
The text was updated successfully, but these errors were encountered: