Add UI to payment request credit card editor to offer updating existing card with same number. |
|||||
Issue descriptionWhen user creates a new credit card payment methop from payment request native UI, the UI identify an existing credit card number as invalid. Instead, the UI should offer to load / update the existing payment method. The attached mock could be used for this new UI.
,
Jun 19 2017
Trying to keep all bugs assigned to avoid losing track of tasks. The assigned owner is not necessarily the person who will perform the work, but it is the best person to ask questions about this issue.
,
Jun 19 2017
,
Jun 27 2017
,
Jan 4
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mad@chromium.org
, May 24 2017Workflow suggested over email: - When adding a new card - As soon as the editor finds an existing card (that is not the one currently being edited) with the same number - it shows the new section under the Credit Card number field - If user clicks on the button of this new UI (how about "Use existing card") then - all the fields content get replaced with the data on file - the title changes to "Edit Card" - the primary button changes to "Update" - If the user changes the card number to one that is not on file - The primary button text is set back to default (OK) - But the other fields are left as is (whether the user pulled them from the saved card or not). - When editing an existing card - As soon as the editor finds an existing card (that is not the one currently being edited) with the same number - it shows a warning saying that card number is already on file - the primary button gets grayed out