From: Stephane Brossier <stephane@kill-bill•org>
To: bitcoin-development@lists•sourceforge.net
Cc: "stephane@kill-bill•org" <stephane@kill-bill•org>,
Pierre-Alexandre Meyer <pierre@kill-bill•org>
Subject: [Bitcoin-development] Extension for BIP-0070 to support recurring payments
Date: Mon, 27 Jan 2014 18:36:34 -0800 [thread overview]
Message-ID: <E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]
Hi,
[I sent this email 2 days ago prior my registration to the mailing list; please forgive me if this is a duplicate]
I would like to propose an extension to the Payment Protocol (bip-0070) to address the case of recurring payments in Bitcoin -- new bip or modification of bip-0070.
There has been a lot of growth in the last few years in the 'subscription economy' with many new companies embracing that model -- online video, gaming, groceries, newspapers,... In parallel, Bitcoin is growing into a mainstream currency (hence bip-0070), and so the next logical step would be to define a protocol to address that need.
We have been working in the past few years on an open-source billing platform (http://kill-bill.org/), and recently came with a prototype to do recurring billing in Bitcoin (see http://thekillbillstory.wordpress.com/2014/01/20/bitcoin-plugin/ and http://thekillbillstory.wordpress.com/2014/01/11/coinbase-integration-experiment/).
The work flow would look similar to the one from bip-0070. There would need to be some additions; the flow could be summarized as follow:
0. Click: 'Subscribe Now'
1. Wallet would get a RecurringPaymentRequestAuth which describes the nature of the future recurring payments
2. The Customer would get prompted from the wallet to authorize it.
3. The wallet would then poll the Merchant server (startup time, and/or well defined frequency) and potentially merchant would start issuing a PaymentRequest); the role of the wallet is to ensure that PaymentRequest is within the bounds of what was accepted by the customer-- amount, frequency,.. If it is, then it would make the Payment the same way it works for bip-0070
Is that something that the community would be interested in? We could provide more details about the protocol we have in mind (messages and flow), and also provide an implementation with bitcoinj as a wallet and Kill Bill as a merchant server.
Le me know what you think.
Stéphane
[-- Attachment #2: Type: text/html, Size: 2687 bytes --]
next reply other threads:[~2014-01-28 2:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 2:36 Stephane Brossier [this message]
2014-01-28 3:58 ` Kevin Greene
2014-01-28 4:29 ` Jeff Garzik
2014-01-28 4:43 ` Jeff Garzik
2014-01-28 5:07 ` PikaPay
2014-01-28 6:08 ` Odinn Cyberguerrilla
2014-01-28 6:48 ` Jeff Garzik
2014-01-28 6:34 ` Mike Hearn
2014-01-29 2:47 ` Stephane Brossier
2014-01-31 18:13 ` Mike Hearn
2014-02-08 2:57 ` Stephane Brossier
2014-02-09 2:48 ` Stephane Brossier
2014-02-11 10:00 ` Kevin Greene
2014-02-11 18:01 ` Stephane Brossier
2014-02-12 6:32 ` Kevin Greene
2014-02-12 6:37 ` Kevin Greene
2014-02-14 20:28 ` Stephane Brossier
2014-02-24 18:04 ` Stephane Brossier
2014-02-25 16:29 ` Mike Hearn
2014-02-25 18:40 ` Drak
2014-02-25 19:03 ` Jeremy Spilman
2014-02-25 19:06 ` Christophe Biocca
2014-02-26 3:53 ` Stephane Brossier
2014-02-26 10:30 ` Mike Hearn
2014-02-11 16:24 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1FDB3F2-25ED-4B99-979E-12CE943CBD66@kill-bill.org \
--to=stephane@kill-bill$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pierre@kill-bill$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox