W3C home > Mailing lists > Public > public-payments-wg@w3.org > June 2016

RE: Review ready Core Messages and HTTP API specs

From: Telford-Reed, Nick <Nick.Telford-Reed@worldpay.com>
Date: Wed, 29 Jun 2016 10:48:28 +0000
To: 'Manu Sporny' <msporny@digitalbazaar.com>, Payments WG <public-payments-wg@w3.org>
Message-ID: <F83606EEAA40AC4EA2919143B15B74C18A131DFC@UKDC2-PC-MBX03.worldpay.local>
Thanks Manu - looking forward to talking about this at the F2F. 


Nick Telford-Reed
e: nick.telford-reed@worldpay.com | m: +447799473854 | t: +44 203 664 5069

> -----Original Message-----
> From: Manu Sporny [mailto:msporny@digitalbazaar.com]
> Sent: 29 June 2016 03:15
> To: Payments WG <public-payments-wg@w3.org>
> Subject: Review ready Core Messages and HTTP API specs
> Hi all,
> Just a quick update to note that the Core Messages and HTTP API specs have
> been aligned a bit more with the latest Web Payments Architecture
> Summary document and the Browser API. They are ready to review:
> Web Payments Core Messages:
> https://w3c.github.io/webpayments-core-messages/

> Web Payments HTTP API:
> https://w3c.github.io/webpayments-http-api/

> If you've done a review in the past two months, not a whole lot has changed
> from a conceptual standpoint. We don't have complete alignment with the
> Browser API yet for at least the following reasons:
> * There is no type inferencing in HTTP messages (like there is in
>    Javascript), and so you need to be explicit about the type.
> * The key/value pair names don't quite match up with the WebIDL
>    in the Browser API due to the possibility of the generic names in
>    the Browser API clashing with other payment/object vocabularies
>    in JSON-LD (for example).
> * The Browser API takes 3 arguments to construct the PaymentRequest
>    while the HTTP API uses a single argument due to the
>    "strangeness" of passing arrays to HTTP APIs.
> * The HTTP API supports digital signatures on the entire payment
>    request, we're not quite sure if/how the Browser API is going
>    to do this.
> The request at the Web Payments WG F2F will be to publish both of these
> documents as FPWDs. Please review them before the face to face and be
> ready to weigh in on that question.
> -- manu

This e-mail and any attachments are confidential, intended only for the addressee and may be privileged. If you have received this e-mail in error, please notify the sender immediately and delete it. Any content that does not relate to the business of Worldpay is personal to the sender and not authorised or endorsed by Worldpay. Worldpay does not accept responsibility for viruses or any loss or damage arising from transmission or access.

Worldpay (UK) Limited (Company No: 07316500/ Financial Conduct Authority No: 530923), Worldpay Limited (Company No:03424752 / Financial Conduct Authority No: 504504), Worldpay AP Limited (Company No: 05593466 / Financial Conduct Authority No: 502597). Registered Office: The Walbrook Building, 25 Walbrook, London EC4N 8AF and authorised by the Financial Conduct Authority under the Payment Service Regulations 2009 for the provision of payment services. Worldpay (UK) Limited is authorised and regulated by the Financial Conduct Authority for consumer credit activities. Worldpay B.V. (WPBV) has its registered office in Amsterdam, the Netherlands (Handelsregister KvK no. 60494344). WPBV holds a licence from and is included in the register kept by De Nederlandsche Bank, which registration can be consulted through www.dnb.nl. Worldpay, the logo and any associated brand names are trade marks of the Worldpay group.
Received on Wednesday, 29 June 2016 10:48:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:17 UTC