Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35)

Here is my model:

* Payment apps and payment methods are different animals. Apps are software, methods are rules, etc.
* In many cases, the entity responsible for the payment method will also create the payment app for that method. The responsible entity could also authorize other parties to distribute apps that support the payment method. We are calling these "proprietary" payment methods.
* After discussion with Zach, I am comfortable with payment method identifiers designating manifest files that explain "how to use the payment method in the ecosystem". We have not yet specified what can go in those manifest files, but I am comfortable with "a variety of information" including, for example, information about which origins are authorized to distribute payment apps for a given proprietary payment method, where to download those apps, etc. I imagine we will want to
discuss how much flexibility to support in manifest files between "inline data" and "data available by reference."

Thus, I would say "Payment methods are not the same things as payment apps." Payment method identifiers will point at manifest files that allow different parties the flexibility to say what they want about BOTH the payment method and the apps that support it.

Ian




-- 
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/35#issuecomment-245480665