@adrianhopebailie Your comment above: "In this architecture a payment method is the protocol that is used between payment app and payee to exchange payment data. " Does not seem to align with the architecture document, which defines payment method as: "A way of paying. A system and set of rules for payments." I have understood payment method to be the things you say for X in the phrase "At this shop we accept X ". That would include things like "Visa" and "PayPal" and "Samsung Pay". I believe users, merchants, and payment system providers care a lot about visibility of those brands. (I think adding examples to the architecture document (as we've discussed) will help build shared understanding.) While I am reluctant to do this, here are some terms to consider: * Payment agent: A piece of software that enables a payer to make payments (usually provided by the payer's PSP). A payment agent is not required to have a user interface; one that does is called a Payment App. A payment agent may support multiple payment methods. * Payment method: A system and set of rules for payments. Examples: Visa, MasterCard, Bitcoin, Ripple, PayPal, Google Pay, Alipay, Yandex money. * Payment mediator: A software agent that coordinates the flow of messages between a payee’s application and the payer’s payment agents. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/31#issuecomment-163355064Received on Wednesday, 9 December 2015 18:50:32 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:12 UTC