make fetching URL-PMI optional (closes #33)

marcoscaceres commented 7 years ago

ianbjacobs commented 7 years ago

Hi @marcoscaceres,

I am thinking we may want to be more explicit in cautionary statements to payment method owners. Here is the sort of flow I have in mind:

For user agents:

It is optional for user agents to fetch PMIs. (I think in your proposal you can drop " As URL-based payment method identifiers serve primarily as identifiers (and not a linked resource), ")

Note to payment method owners:

The Working Group is developing a payment method manifest specification that will give payment method owners greater control over the ecosystem of payment apps that implement their payment method.
- In the absence of a manifest or of broadly deployed implementations of one or more manifest specifications, there is no mechanism to limit which payment apps are able to claim to support a payment method.

[Hit "go" too soon before]

marcoscaceres commented 6 years ago

@ianbjacobs and @adrianhopebailie addressed your feedback. Please review.

adrianhopebailie commented 6 years ago

My concern was an incorrect statement about the location of a manifest in relation to the URL-based PMI. That has been removed so no further comments from me.

w3c / payment-method-id

make fetching URL-PMI optional (closes #33) #40