From: Tamas Blummer <tamas@bitsofproof.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72 (Gavin Andresen)
Date: Wed, 31 Jul 2013 14:31:08 +0200 [thread overview]
Message-ID: <A3B75B83-5DE2-4A1A-943D-AA529F3E1CC0@bitsofproof.com> (raw)
In-Reply-To: <mailman.133694.1375262729.12996.bitcoin-development@lists.sourceforge.net>
[-- Attachment #1.1: Type: text/plain, Size: 313 bytes --]
Since the payment request is available from a location defined in the URI,
I think it would be appropriate to attach the PaymentACK once payment
accepted by Merchant.
This would make the request and receipt available for later review.
Regards,
Tamás Blummer
Founder, CEO
http://bitsofproof.com
[-- Attachment #1.2.1: Type: text/html, Size: 4801 bytes --]
[-- Attachment #1.2.2: email.png --]
[-- Type: image/png, Size: 7120 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
parent reply other threads:[~2013-07-31 12:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.133694.1375262729.12996.bitcoin-development@lists.sourceforge.net>]
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=A3B75B83-5DE2-4A1A-943D-AA529F3E1CC0@bitsofproof.com \
--to=tamas@bitsofproof.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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