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

> Both of these use cases ultimately relate to permissions, and for both of these I have understood
that origin information suffices. Thus, there is no need here for a new kind of "payment app
identifier"; we can just use origins.

This is the key IMO. Well put.

It seems that what many of us are calling "apps" only ever have to identified explicitly as "user choices". If I re-write my set of choice from before it would look like this:

```
Origin 1: https://wallet.com
      |- Option 1:  Wallet.com
                          |-  Option 1.1: Acard ****1234
                          |-  Option 1.2: Bcard ****3456
                          |-  Option 1.3: Bitcoin
Origin 2: https://banka.com
      |- Option 1:  Bank A Business
                          |-  Option 1.1: Credit Transfer
                          |-  Option 1.2: Bank Cheque
                          |-  Option 1.3: Corp Card ****4567
      |- Option 2:  Bank A Personal 
                          |-  Option 1.1: Acard ****1234
                          |-  Option 1.2: Loyalty Points
```

What is not clear to me yet is what combination of Service Worker registration code and calls to `PaymentManager.addOption(...)` or similar would result in this set of options being presented to a user (assuming the browser wanted to present the full depth of options).

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