Skip to content

/browser-payment-api

New issue

Should list of accepted payment methods be strings or objects? #48

Closed
msporny opened this Issue Mar 14, 2016 · 1 comment

Labels

Cat: Design/Technical Doc:BrowserAPI Priority: High

Milestone

  28 April

Assignee

@adrianba adrianba

4 participants

@msporny @adrianhopebailie @mattsaxon @adrianba
@msporny
msporny commented Mar 14, 2016

Migrated from w3c/webpayments#37:

The paymentRequest API asserts that the list of accepted payment methods that a payee exposes to the payer should be a list of strings:

http://wicg.github.io/paymentrequest/specs/paymentrequest.html#paymentrequest-interface

For example:

["visa", "bitcoin", "bobpay.com"]

The Web Payments CG Browser API asserts that the list should be composed of objects:

http://wicg.github.io/web-payments-browser-api/#processing-a-payment-request

For example:

acceptedScheme: [{
    scheme: [
      'https://w3id.org/payment-schemes#Visa',
      'https://w3id.org/payment-schemes#Mastercard',
      'https://w3id.org/payment-schemes#Discover'
    ],
    transfer: {
      amount: '4.35',
      currency: 'USD'
    },
    paymentRequestService: 'https://merchant-psp.example.com/services/getPaymentInfo'
  }, {
    scheme: 'https://w3id.org/payment-schemes#Bitcoin',
    transfer: {
      amount: '0.0177',
      currency: 'BTC'
    },
    destination: '3QJmV3qfvL9SuYo34YihAf3sRCW3qSinyC'
  },

Should list of accepted payment methods be strings or objects?

@msporny msporny referenced this issue in w3c/webpayments Mar 14, 2016
Closed

Should list of accepted payment methods be strings or objects? #37

@msporny msporny added a commit to msporny/browser-payment-api that referenced this issue Mar 16, 2016
@msporny msporny Add reference to issue #48. c006928
@msporny msporny referenced this issue Mar 16, 2016
Closed

Add reference to issue #48. #82

@mattsaxon mattsaxon added the Technical label Mar 21, 2016
@mattsaxon mattsaxon added this to the Priority: Medium milestone Mar 21, 2016
@msporny msporny added a commit to msporny/browser-payment-api that referenced this issue Mar 29, 2016
@msporny msporny Update reference to issue #48. 06a2444
@adrianba adrianba added a commit that referenced this issue Apr 1, 2016
@msporny msporny Add reference to issue #48. fcfe1d1
@adrianhopebailie
adrianhopebailie commented Apr 10, 2016

PR #133 proposes a solution to the issue.

@adrianhopebailie adrianhopebailie referenced this issue Apr 10, 2016
Closed

Merged PaymentRequest params and tweaked to address some issues #133

@adrianba adrianba added a commit to adrianba/browser-payment-api that referenced this issue Apr 28, 2016
@adrianba adrianba Remove issue #48 label. 
Fixes #48.

PR #162 refactored the supportedMethods and payment specific data
fields. Issue #3 discusses supporting multiple currencies and issue #4
discusses price per payment method and we should consider specific
proposals for those issues.

PR #162 replaces the `sequence<DOMString>` with
`sequence<PaymentMethodData>` so we now use objects.
 7bcb324
@adrianba adrianba referenced this issue Apr 28, 2016
Closed

Remove issue #48 label. #165

@adrianba adrianba added a commit that referenced this issue Apr 28, 2016
@adrianba adrianba Remove issue #48 label. 
Fixes #48.

PR #162 refactored the supportedMethods and payment specific data
fields. Issue #3 discusses supporting multiple currencies and issue #4
discusses price per payment method and we should consider specific
proposals for those issues.

PR #162 replaces the `sequence<DOMString>` with
`sequence<PaymentMethodData>` so we now use objects.
 63d1aa6
@adrianba adrianba added a commit that closed this issue Apr 28, 2016
@adrianba adrianba Remove issue #48 label. 
Fixes #48.

PR #162 refactored the supportedMethods and payment specific data
fields. Issue #3 discusses supporting multiple currencies and issue #4
discusses price per payment method and we should consider specific
proposals for those issues.

PR #162 replaces the `sequence<DOMString>` with
`sequence<PaymentMethodData>` so we now use objects.
 63d1aa6
@adrianba adrianba closed this in 63d1aa6 Apr 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.