Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34)

I think I'm also generally in favor of URLs. I want to clarify what is being proposed in option 1. Would the idea be that *every* payment method should live at tobedetermined.com? Or just the ones that we standardize up front? For example, let's say my support payment methods were: Visa, Mastercard, and BobPay.xyz (a proprietary, closed-loop system). Would the final array look like:

```js
['https://www.bobpay.xyz', 'https://www.tobedetermined.com/visa', 'https://www.tobedetermined.com/mastercard']
```

Which could then be made shorter with:

```js
['bobpay.xyz', 'Visa', 'Mastercard']
```

Or is the idea that even Bobpay would have to live behind tobedetermined.com, such as:

```js
[`https://www.tobedetermined.com/bobpay.xyz', '...', '...']
```js

Seems like it's the former, but I want to clarify.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/34#issuecomment-195440736