- From: David Nicol <davidnicol@gmail.com>
- Date: Thu, 20 Nov 2014 10:17:03 -0600
- To: David Ezell <David_E3@verifone.com>
- Cc: "Joerg.Heuer@telekom.de" <Joerg.Heuer@telekom.de>, "public-webpayments-ig@w3.org" <public-webpayments-ig@w3.org>, "public-webpayments-comments@w3.org" <public-webpayments-comments@w3.org>
A system of specific jargon appears in the e-mail domain, with MUA Mail User Agent MTA Mail Transfer Agent OMTA Outbound MTA MDA Mail Delivery Agent and possibly others. Differentiating "Payment Agent" into various subclasses might follow that model. On Wed, Nov 19, 2014 at 8:05 AM, David Ezell <David_E3@verifone.com> wrote: > Joerg wrote: > Actually I would think it is important to differentiate the user's (payer's side) view from that of the services > (payee and processors, and all the others, the user usually doesn't need to know much about). I would, thus, > propose to use the term 'user payment agent', leaving open whether there might be a 'merchant payment agent' > or something similar, acting on the 'other side' of the user's payment experience.
Received on Thursday, 20 November 2014 16:17:33 UTC