Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248)

I've not thought about this much yet but there are some nuances. For instance: if a payment app supports N payment methods and is "not authorized" for one of them, should the entire registration be scrapped, or should the payment app still be able to register for the other payment methods (either open or authorized)? 

Suppose the FooApp supports basic card and Alipay but is not authorized to support Alipay.
The merchant accepts both payment methods, so FooApp matches. FooApp controls the
user experience of selection within the handler, so the browser can't prevent the user
from *selecting* Alipay. The browser can only complain once Payment Handler API returns.

What does the browser do then? Does the browser pop up a warning to the user and relaunch
Payment Handler API?

(Also, this question seems to be relevant for "validation against payment method manifest during the transaction" as well.)


-- 
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/payment-handler/issues/248#issuecomment-363612905