Re: [w3c/browser-payment-api] Identifiers or Locators (#150)

+1 for identifiers

I see no value in dereferencing these identifiers to anything other than a human readable specification therefor I'd consider their value to be primarily as identifiers.

The implementers of the payment method logic (payment apps and websites) are not going to be able to dynamically support new payment methods by merely fetching a machine readable payment method specification.

IF this was supported by some subset of payment methods I'd expect the developers of those specifications to define additional steps that must be taken after fetching the resource at the payment method identifier URL to interpret this resource and use that logic to actually process a payment request.

---
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/browser-payment-api/issues/150#issuecomment-213107889