[w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237)

Scenario:

 * User chooses a card to pay
 * Basic card data is sent to merchant,
 * Payment fails (e.g., card rejected after some validation)

Should there be a mechanism whereby the merchant can re-invoke the API with some data
about the failed instrument, and the browser can take it into account in a variety of ways, 
such as:

 * Excluding it from the list of available instruments, or
 * Highlighting it as "having failed previously"

The use case may be extensible to other pull methods, but I'll focus on cards for now.

My sense is that we should not add such a feature in v1. Merchants can display an
error message and ask the user to pick another card, and we can rely on the user
to do the right thing (or fail again). 

It does not seem to me that merchant-applied filtering (e.g., "this time around I don't take
cards of this type") using Zach's proposal is the right solution since that is not instrument-specific.

Ian


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/237