-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should list of accepted payment methods be strings or objects? #48
Comments
msporny
added a commit
to msporny/browser-payment-api
that referenced
this issue
Mar 16, 2016
msporny
added a commit
to msporny/browser-payment-api
that referenced
this issue
Mar 29, 2016
PR #133 proposes a solution to the issue. |
adrianba
added a commit
to adrianba/browser-payment-api
that referenced
this issue
Apr 28, 2016
Fixes w3c#48. PR w3c#162 refactored the supportedMethods and payment specific data fields. Issue w3c#3 discusses supporting multiple currencies and issue w3c#4 discusses price per payment method and we should consider specific proposals for those issues. PR w3c#162 replaces the `sequence<DOMString>` with `sequence<PaymentMethodData>` so we now use objects.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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:
Should list of accepted payment methods be strings or objects?
The text was updated successfully, but these errors were encountered: