Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)

> "One or more pieces of software that act as a conduit between the payer and their various funding sources, enabling the payer to make payments from one or more of those funding sources."

I don't know if this is a thing that sits between the payer and their funding sources. That sounds like it's just a piece of software that helps you decide which funding source to use. That sounds like the Payment Mediator's job.

Instead, this thing sounds like it's a piece of software that *uses* a funding source (somehow) to initiate a payment. This also better matches the [wiki page description here of a Payment App](https://github.com/w3c/webpayments/wiki/Components#payment-app):

"The Payment App facilitates a payment on behalf of the payer using one or more payment methods..."

As an analogy, one simplistic definition of a User Agent could be: "A piece of software that acts as a conduit between the user and a website, enabling the user to view web pages."

It seems like a "Payment Agent" would be a piece of software that enables a payer to make payments using their payment instrument of choice.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/31#issuecomment-162971647