W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2017

HTTP Payments - draft-hope-bailie-http-payments-00

From: Adrian Hope-Bailie <adrian@ripple.com>
Date: Tue, 31 Oct 2017 01:57:21 +0200
Message-ID: <CAN1GQt362TT93hMyRkXbvZTd4QLmMCYrMO1R-JYn9ZaO9H3xCQ@mail.gmail.com>
To: ietf-http-wg@w3.org
Hi HTTPbis,

I'd like a few minutes of your time in Singapore to solicit interest in
pursuing something along the lines of what I have in
draft-hope-bailie-http-payments-00
[1]. As you may or may not be aware, all major browsers are shipping, or
close to shipping new payment APIs based on the specifications [2][3]
developed in the W3C Web Payments working group.

In the Interledger community group we have been experimenting with paid
HTTP requests for some time. We have defined some behaviours, primarily
through the use of some new headers, for clients and servers to exchange
the required information for the client to make a payment (in response to a
402 Payment Required HTTP response) and then retry the request with a
payment token.

This ID takes these ideas and merges them with the W3C Web Payments idea if
payment method identifiers to offer a more generic version of the system
that could support any payment method.

Adrian

[1] https://datatracker.ietf.org/doc/draft-hope-bailie-http-payments/
[2] https://www.w3.org/TR/payment-request/
[3] https://www.w3.org/TR/payment-method-id/
Received on Monday, 30 October 2017 23:57:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:11 UTC