Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95)

@marcoscaceres --
I think you're missing an important part of the overall flow here.

Imagine:

- I have installed an app from https://www.bankofamerica.com/payments/v1/cards.js, which supports the "basic-card" payment method.

- I also have installed an app from https://www.citibank.com/assets/cc-payment-app.js, which supports the "basic-card" payment method.

- I also have installed an app from https://www.paypal.org/eboxapps/js/0d/d056209362e0d90abada2b39c6846b5ddc8953.js which supports the "basic-card" payment method (among others).

- Finally, because I have two very different account types with paypal, I also have installed a different app from https://www.paypal.org/eboxapps/js/68/68102ba47925b528684486c62f26ca750df08ec1.js which supports the "basic-card" payment method (among others).

Now, I go to a merchant site and click the "Pay" button. I, as a user, need to decide, _at that moment_, which of these four payment apps I want to use to send a basic card number to the merchant.

Without a registered icon and name, all you have is the URL these payment apps came from. So you can either show the user:

1. www.bankofamerica.com
2. www.citibank.com
3. www.paypal.com
4. www.paypal.com

(Leaving the user no way to distinguish between the two different paypal apps), *or* you can show the user:

1. https://www.bankofamerica.com/payments/v1/cards.js
2. https://www.citibank.com/assets/cc-payment-app.js
3. https://www.paypal.org/eboxapps/js/0d/d056209362e0d90abada2b39c6846b5ddc8953.js
4. https://www.paypal.org/eboxapps/js/68/68102ba47925b528684486c62f26ca750df08ec1.js

(at which point the close their browser, hop in the car, and drive to the store, on the basis that the web has simply become too confusing for them to use any longer.)

The reason we need these names (and, ideally, icons) is to allow this app selection process to be rendered to the user in some sensible fashion. If you think this is a solved problem, please be explicit in describing precisely where the browser will get these names and icons from, if not provided by the payment app itself during its registration.

-- 
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/webpayments-payment-apps-api/issues/95#issuecomment-274854926