Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) from Marcos Cáceres on 2017-01-25 (public-webpayments-specs@w3.org from January 2017)

From: Marcos Cáceres <notifications@github.com>
Date: Tue, 24 Jan 2017 21:18:00 -0800
To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments-payment-apps-api/issues/98/275021705@github.com>

Wish we could stop calling them "apps"... it's making this really confusing (because these things are inside *web apps*). 

Anyway, In the other bug I said:

![screenshot_2017-01-25_15_43_57](https://cloud.githubusercontent.com/assets/870154/22278699/97b03a70-e319-11e6-9c87-9c8bee5dc347.png)

## why we should not allow multiple payment handlers.

* Unnecessary complexity: it's a super edge case, and can be solved using a different origin. 
* Each requires its own name/icon(s): requires differentiating between different type of "apps" - adds more complexity; introduces yet more icons, names, etc. to the platform.  
* Confusing: revoking payment handling permission for "PayPal.com" disables multiple payment handlers. 



-- 
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-275021705

Received on Wednesday, 25 January 2017 05:18:34 UTC