Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98)

> To clarify, are you suggesting that the options may not be grouped together at all? I thought your mock-ups above were a good indicator of how things may be rendered. 

The more I experiment with different apps and ideas, the less appealing I find the idea of showing then all together outside an application (why I showed the Uber example). See also eBay + PayPal together (specially if you have multiple payment and shipping addresses etc. registered). I hear Stripe provides an even nicer experience - but haven't had the opportunity to use it. 

Would love for us to collect more screenshots of existing solutions - so to see if this problem is well solved or not. 

> Obviously this is up to browsers but if they want to group options under an origin/app then we need to make sure that is possible.

Agree - and working with Mozilla's UX/UI team on that... but it might turn out that beyond the details of the payment method (i.e., the credit card number), icons etc. might be best just left to the payment app itself ( I don't have a strong opinion - just a gut feeling). 

Consider, management of the payment methods is done in the app itself - not by the browser. The browser can tell the user about the permission to use the API, and how many methods are registered, but managing of those methods (add, update, delete, etc.) would need to happen inside the web app - this is because payment methods differ from one app to another (credit card VS bit coin VS magic token VS whatever). 


-- 
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/98#issuecomment-278339217