📅 Original date posted:2014-01-28
📝 Original message:+1 to the idea of recurring payment requests.
Perhaps one way to realize this would be to add an optional URL to the
PaymentRequest object where the next PaymentRequest can be fetched and the
date at which the merchant expects the next payment.
On Mon, Jan 27, 2014 at 6:36 PM, Stephane Brossier
<stephane at kill-bill.org>wrote:
> 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
>
>
> ------------------------------------------------------------------------------
> WatchGuard Dimension instantly turns raw network data into actionable
> security intelligence. It gives you real-time visual feedback on key
> security issues and trends. Skip the complicated setup - simply import
> a virtual appliance and go from zero to informed in seconds.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140127/f154809e/attachment.html>;
Kevin Greene [ARCHIVE] /
npub1l3…hwq5p
2023-06-07 15:12:45
in reply to nevent1q…m54z
Author Public Key
npub1l3sj8amnurgf3cu3p2hhcaham90khafc4vgsmymqdnn0k3kanulsghwq5pPublished at
2023-06-07 15:12:45Event JSON
{
"id": "29905952deb5d9416651d9c9fc605b92a9d765d535434d0fffac05a73e18524b",
"pubkey": "fc6123f773e0d098e3910aaf7c76fdd95f6bf538ab110d93606ce6fb46dd9f3f",
"created_at": 1686150765,
"kind": 1,
"tags": [
[
"e",
"e2d6e2a2a3dfae2c36aa7e49566e9ceda976a4131ebc3d875c95d475f3663a3e",
"",
"root"
],
[
"e",
"d0b14b86703a75864e324d20c53ece78db4e2d5121921e359bab57f34d6c391a",
"",
"reply"
],
[
"p",
"6f1f1b1ffee15f66a6734f04cc50914703cdec55043d3a3e02d3d877ad4dc171"
]
],
"content": "📅 Original date posted:2014-01-28\n📝 Original message:+1 to the idea of recurring payment requests.\n\nPerhaps one way to realize this would be to add an optional URL to the\nPaymentRequest object where the next PaymentRequest can be fetched and the\ndate at which the merchant expects the next payment.\n\n\nOn Mon, Jan 27, 2014 at 6:36 PM, Stephane Brossier\n\u003cstephane at kill-bill.org\u003ewrote:\n\n\u003e Hi,\n\u003e\n\u003e [I sent this email 2 days ago prior my registration to the mailing list;\n\u003e please forgive me if this is a duplicate]\n\u003e\n\u003e I would like to propose an extension to the Payment Protocol (bip-0070) to\n\u003e address the case of recurring payments in Bitcoin -- new bip or\n\u003e modification of bip-0070.\n\u003e\n\u003e There has been a lot of growth in the last few years in the 'subscription\n\u003e economy' with many new companies embracing that model -- online video,\n\u003e gaming, groceries, newspapers,... In parallel, Bitcoin is growing into a\n\u003e mainstream currency (hence bip-0070), and so the next logical step would be\n\u003e to define a protocol to address that need.\n\u003e\n\u003e We have been working in the past few years on an open-source billing\n\u003e platform (http://kill-bill.org/), and recently came with a prototype to\n\u003e do recurring billing in Bitcoin (see\n\u003e http://thekillbillstory.wordpress.com/2014/01/20/bitcoin-plugin/ and\n\u003e http://thekillbillstory.wordpress.com/2014/01/11/coinbase-integration-experiment/\n\u003e ).\n\u003e\n\u003e\n\u003e The work flow would look similar to the one from bip-0070. There would\n\u003e need to be some additions; the flow could be summarized as follow:\n\u003e\n\u003e 0. Click: 'Subscribe Now'\n\u003e 1. Wallet would get a RecurringPaymentRequestAuth which describes the\n\u003e nature of the future recurring payments\n\u003e 2. The Customer would get prompted from the wallet to authorize it.\n\u003e 3. The wallet would then poll the Merchant server (startup time, and/or\n\u003e well defined frequency) and potentially merchant would start issuing a\n\u003e PaymentRequest); the role of the wallet is to ensure that PaymentRequest is\n\u003e within the bounds of what was accepted by the customer-- amount,\n\u003e frequency,.. If it is, then it would make the Payment the same way it works\n\u003e for bip-0070\n\u003e\n\u003e Is that something that the community would be interested in? We could\n\u003e provide more details about the protocol we have in mind (messages and\n\u003e flow), and also provide an implementation with bitcoinj as a wallet and\n\u003e Kill Bill as a merchant server.\n\u003e\n\u003e Le me know what you think.\n\u003e\n\u003e Stéphane\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e WatchGuard Dimension instantly turns raw network data into actionable\n\u003e security intelligence. It gives you real-time visual feedback on key\n\u003e security issues and trends. Skip the complicated setup - simply import\n\u003e a virtual appliance and go from zero to informed in seconds.\n\u003e\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=123612991\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140127/f154809e/attachment.html\u003e",
"sig": "e03fbf6fdc7a3ba5fdbd12aa10f8e6a0cb14833f3d441beddd2f27a82162f9efa09a02737f619f21ee712c6094b12c99e30ae5d270d79e1f162272feb49985cd"
}