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

Re: Updates to Payment Apps wiki page

From: Håvard Molland <haavardm@opera.com>
Date: Wed, 11 May 2016 13:46:46 +0200
Message-ID: <CACZ2MLiOZMbUy66vzXFP9cx+-tPdfMs-bAuLsgh-L2a5HB1FUA@mail.gmail.com>
To: Christopher Allen <ChristopherA@blockstream.com>
Cc: Adrian Hope-Bailie <adrian@hopebailie.com>, Ian Jacobs <ij@w3.org>, Payments WG <public-payments-wg@w3.org>
On Wed, May 11, 2016 at 12:59 PM, Christopher Allen <
ChristopherA@blockstream.com> wrote:

>
>
> On Wednesday, May 11, 2016, Håvard Molland <haavardm@opera.com> wrote:
>
>>
>> Can you give an example where a HTTP gateway answers to a payment request
>> POSTed from a browser, where the gateway doesn't have to produce
>> a JavaScript payment app as a response?
>>
>>
> Almost every mutisig Bitcoin wallet service, Circle, Coinbase, etc.
>

By examples, I mean that the full flow is described.

How is the payment request initiated (javascript API, the HTTP api?). How
does the payment app server respond to the POST (html, json)? How does the
user authenticate to the payment provider?


>
> -- Christopher Allen
>
Received on Wednesday, 11 May 2016 15:49:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 May 2016 15:49:21 UTC