Country under test: Spain Tested against Bango production steps to reproduce: 1. Tester has previously saved a credit card 2. Start the purchase flow for a paid app 3. Choose the option to pay with a different card (other than the one saved) expected behavior: There are links for users to change their mind and return to carrier billing or reuse the saved credit card observed behavior: The new designs based on mocks are missing these links. Please add them back.
I think changing the payment method is an edge case (not many people have credit cards, some markets will only be able to use credit cards, etc.) so I'm willing from a UX point of view to require the user to cancel and start the process again. See more comments here: https://bugzilla.mozilla.org/show_bug.cgi?id=865201#c2
(In reply to Maureen Hanratty from comment #1) > I think changing the payment method is an edge case (not many people have > credit cards, some markets will only be able to use credit cards, etc.) so > I'm willing from a UX point of view to require the user to cancel and start > the process again. > > See more comments here: > https://bugzilla.mozilla.org/show_bug.cgi?id=865201#c2 Maureen, your new mocks already has this link (http://cl.ly/image/1V2t38340y3C). We can have the link with less text if that makes things easier (A Back link like you mentioned) I think we should keep it. A person may click the link by accident. Having to start over can be tedious. I understand the need to keep the form clean but it is more important to make it easy for people to purchase apps.
Created attachment 744275 [details] Credit Card payment screen with "Go Back" button Proposing that the "Cancel" button be changed to a "Go Back" button on the credit card page. The "Go Back" button will take user back to the confirm payment screen where the user can use their saved credit card or switch to carrier building.
ETA ~ tomorrow(05/03) on test
Keir believes fixes in Test & live
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.