public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99•net>
To: Andreas Schildbach <andreas@schildbach•de>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
Date: Tue, 24 Jun 2014 17:59:27 +0200	[thread overview]
Message-ID: <CANEZrP3G0BxGh7PnN_czGnqLLzQZ-gbR=uPhOjO5_b_5dMQ1zA@mail.gmail.com> (raw)
In-Reply-To: <loc6bn$ck0$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

>
> I think it should be made more clear what's the reference price for the
> discount.
>

That might be useful for merchants that already provide a series of
price-differentiated payment methods, yes. Will think about it.


> Also, currently PR are created by the payment processors afaik. How can
> they know what other payment option the merchant provides and what's the
> conditions?
>

Currently Coinbase let merchants specify the size of their discount (I
guess in percentage terms, I should ask). So the merchants tell the payment
processor. I don't think this is a worry at the moment.

[-- Attachment #2: Type: text/html, Size: 991 bytes --]

  reply	other threads:[~2014-06-24 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 13:27 Mike Hearn
2014-06-24 14:21 ` Jeff Garzik
2014-06-24 14:24   ` Mike Hearn
2014-06-24 14:32     ` slush
2014-06-24 15:06       ` Mike Hearn
2014-06-24 15:15       ` Gmail
2014-06-24 15:48         ` Jeff Garzik
2014-06-24 19:00           ` Gmail
2014-06-24 19:34             ` Andy Alness
2014-06-24 20:12             ` Gavin Andresen
2014-06-24 20:28               ` Gmail
2014-06-25  8:25                 ` Mike Hearn
2014-06-25 13:33                   ` Jorge Timón
2014-06-25 18:10                     ` Jeff Garzik
2014-06-25 14:15                   ` slush
2014-06-25 16:03                     ` Gmail
2014-06-24 18:34   ` Roy Badami
2014-06-24 15:43 ` Andreas Schildbach
2014-06-24 15:59   ` Mike Hearn [this message]
2014-06-24 17:37 ` Drak

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='CANEZrP3G0BxGh7PnN_czGnqLLzQZ-gbR=uPhOjO5_b_5dMQ1zA@mail.gmail.com' \
    --to=mike@plan99$(echo .)net \
    --cc=andreas@schildbach$(echo .)de \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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