From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Instant / contactless payments
Date: Thu, 6 Mar 2014 17:52:20 +0100 [thread overview]
Message-ID: <CANEZrP0HXEOMg3Q_eaTz05T82JwH39sGq3Gu2gkc7A+PPUh=4w@mail.gmail.com> (raw)
In-Reply-To: <lfa8pf$ckc$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
>
> I wonder about the receipt step -- are you generating a PDF on device
> and sending it via NFC? This is something that could be supported by the
> BIP70 payment protocol. We should try to avoid the second tap, its not
> intuitive.
>
Together, the signed PaymentRequest and the transactions in the block chain
should act like a receipt: it's proof you requested payment in a certain
way, and I satisfied that payment. So it's proof of payment and the memo
field can describe what I bought.
> Contactless cards? Last I was to London, the Oyster card was already
> contactless. Have there ever been magnet-strip-based Oyster cards?
>
He means, contactless credit cards can be used too. No need to enroll for
Oyster specifically. I guess in the long run Oyster and its equivalents in
other cities (octopus etc) will be phased out.
[-- Attachment #2: Type: text/html, Size: 1253 bytes --]
next prev parent reply other threads:[~2014-03-06 16:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:45 [Bitcoin-development] Instant / contactless payments Mike Hearn
2014-03-06 11:26 ` Andreas Schildbach
2014-03-06 13:44 ` Mike Hearn
2014-03-06 14:51 ` Andreas Schildbach
2014-03-06 16:55 ` [Bitcoin-development] Instant / contactless payments, IsoDep Andreas Schildbach
2014-03-06 17:00 ` Mike Hearn
2014-03-07 8:45 ` Andreas Schildbach
2014-03-07 9:26 ` [Bitcoin-development] Instant / contactless payments Johannes Zweng
2014-03-07 10:00 ` Mike Hearn
2014-03-07 10:23 ` Andreas Schildbach
2014-03-07 11:01 ` Mike Hearn
2014-03-07 12:00 ` Johannes Zweng
2014-03-06 14:20 ` Brooks Boyd
2014-03-06 17:07 ` Mike Hearn
2014-03-06 18:08 ` Brooks Boyd
2014-03-06 18:12 ` Mike Hearn
2014-03-06 18:20 ` Brooks Boyd
2014-03-06 18:24 ` Mike Hearn
2014-03-07 18:07 ` Joel Kaartinen
2014-03-06 14:39 ` Alex Kotenko
2014-03-06 16:46 ` Andreas Schildbach
2014-03-06 16:52 ` Mike Hearn [this message]
2014-03-06 18:03 ` Alex Kotenko
2014-03-07 8:59 ` Andreas Schildbach
2014-03-06 17:03 ` Mike Hearn
2014-03-06 18:49 ` Alex Kotenko
2014-03-08 8:52 ` Jan Vornberger
2014-03-10 15:09 ` Alex Kotenko
2014-03-10 19:28 ` Andreas Schildbach
2014-03-10 19:47 ` Alex Kotenko
2014-03-07 19:08 ` Troy Benjegerdes
2014-03-10 16:04 ` Mike Hearn
2014-03-10 16:14 ` Jean-Paul Kogelman
2014-03-10 16:27 ` Alex Kotenko
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='CANEZrP0HXEOMg3Q_eaTz05T82JwH39sGq3Gu2gkc7A+PPUh=4w@mail.gmail.com' \
--to=mike@plan99.net \
--cc=andreas@schildbach.de \
--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