From: Alex Kotenko <alexykot@gmail•com>
To: Jean-Paul Kogelman <jeanpaulkogelman@me•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Instant / contactless payments
Date: Mon, 10 Mar 2014 16:27:12 +0000 [thread overview]
Message-ID: <CALDj+BbhydEyQUWu+qo=tcu6K10Tosb=rvXnZ+SPmPJRQXuAHQ@mail.gmail.com> (raw)
In-Reply-To: <EFDD07B8-F2C3-4676-B038-469E7BC08802@me.com>
[-- Attachment #1: Type: text/plain, Size: 3425 bytes --]
It heavily depends on where you use it. Here in UK any card payments are
often limited to minimum of £5 in small shops that have heavy transaction
fees burden and low margins. Big networks with more resources often let you
pay as little as you want by card, and they more often have NFC enabled POS
devices.
So it's not an NFC or POS limit, but a business decision for these small
merchants. Bitcoin can address this issue for sure, but this doesn't
concern NFC.
2014-03-10 16:14 GMT+00:00 Jean-Paul Kogelman <jeanpaulkogelman@me•com>:
>
> Just to add some more numbers, in Canada, the maximum is $50 and I've used
> it for transactions of $5, even less.
>
> I use it every day to pay for breakfast and it works through my wallet,
> even with multiple NFC enabled cards in there (though not overlapping). The
> experience is quite smooth; simply tap my wallet on the POS and a few
> seconds later it's approved.
>
> jp
>
> On Mar 10, 2014, at 9:04 AM, Mike Hearn <mike@plan99•net> wrote:
>
> I just did my first contactless nfc payment with a MasterCard. It worked
>> very well and was quite delightful - definitely want to be doing more of
>> these in future.
>>
>
> A bit more competitive intelligence - turns out that the experience isn't
> quite so good after all. After trying a few more times to use contactless
> payments, I found it has a ~75% failure rate based on my usage.
>
> By far the biggest problem is also the most predictable - it's very common
> here for merchants to require minimum payment sizes before they'll accept
> credit cards, often quite high, like 20 CHF or more. But the PIN-less mode
> only works for payments below a certain threshold, I haven't quite figured
> out what it is yet, but in the UK it's 20 GBP so maybe it's about 30 CHF.
> So there turns out to be an incredibly thin price range in which the simple
> touch-to-pay system actually works. Most of the time, either they:
>
> a) Reject cards entirely because the payment is too small
> b) Don't have the right hardware, or the hardware just mysteriously fails
> to work.
> c) Require a PIN because the payment is too large
>
> I'm sure Bitcoin can do better than this.
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 5378 bytes --]
prev parent reply other threads:[~2014-03-10 16:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:45 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
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 [this message]
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='CALDj+BbhydEyQUWu+qo=tcu6K10Tosb=rvXnZ+SPmPJRQXuAHQ@mail.gmail.com' \
--to=alexykot@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jeanpaulkogelman@me$(echo .)com \
/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