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

Re: sketching out HTTP 402 workflow

From: Michael Bumann <hello@michaelbumann.com>
Date: Mon, 27 Jul 2015 12:53:27 +0200
Cc: Web Payments <public-webpayments@w3.org>
Message-Id: <8358655B-1784-4CFB-B7D4-F9851B945BA0@michaelbumann.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>

I'm pretty new to the list and still researching all the valuable content that is published here.

Actually I am currently also experimenting with a Bitcoin based/Cryptocurrency based payment flow in the browser -  built around a browser extension that integrates with the user's wallet. As far as I remember a solution that is using Bitcoin as a mechanism of value transfer from the client to the server has been discussed here a while ago. 

From what you are describing I was wondering how the "Payment would be subtracted from the [user's] wallet"? Which party is in charge of that? 
Does this mean there is necessarily a third-party involved that handles the payment from the client to the server? 


On 26 Jul 2015, at 01:22, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> I'd like to sketch out a design and workflow for HTTP 402 that I think would be possible to implement as a proof of concept
> im trying to design a payment system using SoLiD and HTTP 402 ... I wonder how it would go?
> 1    Alice wishes to view resource X costing 1 bit from wallet W
> 2    resource X is ACL protected
> 3    Alice visits controller website and indicates wish to view protected resource
> 3    Controller website sends back HTTP 402 saying payment required and gives a protected location Y for Alice to send a payment
> 4    Controller website subscribes to location Y
> 5    If Alice is verified as sending a payment she is added to ACL of X
> 6    Payment is subtracted from wallet W
> 7    Alice can view resource X
> I'll be using the SoLiD framework for this.  
> Anyone see any obvious flaws in the workflow?
> [1] https://linkeddata.github.io/SoLiD/
Received on Wednesday, 29 July 2015 22:31:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:41 UTC