W3C home > Mailing lists > Public > public-webpayments-ig@w3.org > May 2015

RE: [payment arch] Payment Agent communication channels

From: David Ezell <David_E3@VERIFONE.com>
Date: Sat, 2 May 2015 19:56:01 +0000
To: Manu Sporny <msporny@digitalbazaar.com>, Web Payments IG <public-webpayments-ig@w3.org>
Message-ID: <54C00E24834FCE47B11EC129A84E7F78CCB59728@VF2WDEXMB1.verifone.com>
Hi Manu et al:
I think the channels are quite useful - very nice work.  And this document is really starting to take shape.  It will be something we'll all be happy with soon I hope.

As one possible next step, I think it would be helpful to identify (for each channel) the "direction of origin" (i.e. is it an event out or a call in) for the various "features" listed on each channel.  This would bring us tantalizingly close (but not too close) to seeing interfaces in the design.

Thanks for all of this good work.

Best regards,

-----Original Message-----
From: Manu Sporny [mailto:msporny@digitalbazaar.com]
Sent: Thursday, April 30, 2015 12:58 PM
To: Web Payments IG
Subject: [payment arch] Payment Agent communication channels

On the call today, we resolved that the Payment Agent has 3 major communication channels. Attached is an updated Payment Agent image to reflect where consensus seemed to be today. The document has been updated w/ the new image (as a vector graphic, on page 6):


-- manu

Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc.
blog: High-Stakes Credentials and Web Login http://manu.sporny.org/2014/identity-credentials/
This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.
Received on Saturday, 2 May 2015 19:56:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:35 UTC