Re: [paymentrequest] Combine API parameters into a single request object + options (#41)

> Maybe a naive question, but: isn't bitcoin a "currency" rather than a "payment method"?

You could say it's both but that's not really the point of this issue. The "payment method" is a concept we have defined in our component architecture as: a way that the payer and payee agree to complete the payment. By agreeing on a payment method they agree on what data is expected to be in the request, what (if any) operations the payment app must perform and what data is expected to be in the response.

See the architecture defined here: https://github.com/w3c/webpayments/wiki/A-Payments-Initiation-Architecture-for-the-Web

"Bitcoin" is an example of a possible payment method. i.e. Some people get together (maybe the Bitcoin community) and define how a payer and payee would do a Bitcoin payment and what data needs to be in the payment request and what data needs to be in the response. (It would probably be based on BIP70).

You do raise an important question though. Should payment requests support multiple pricing options? There a number of reasons why they might:
 1. The payee wants to explicitly accept payment in multiple currencies (USD and XBT for example)
 1. The payee wants to offer different prices depending on which payment method is used.
 1. The payee wants to offer multi-tender payments

I am going to create a new issue to discuss this specifically.

---
Reply to this email directly or view it on GitHub:
https://github.com/WICG/paymentrequest/issues/41#issuecomment-178492134