public-webpayments-specs@w3.org from June 2016 by subject

[w3c/browser-payment-api] Add section on Extensibility (#44)

[w3c/browser-payment-api] Add section on internationalization (#53)

[w3c/browser-payment-api] Add shippingOption to response (#217)

[w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35)

[w3c/browser-payment-api] Combine API parameters into a single request object + options (#15)

[w3c/browser-payment-api] Currency Types and Rendering (#185)

[w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178)

[w3c/browser-payment-api] Fix a minor typo in PaymentRequest constructor description. (#221)

[w3c/browser-payment-api] Fix two minor typos. (#220)

[w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50)

[w3c/browser-payment-api] How are web-based payment apps supported? (#39)

[w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33)

[w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173)

[w3c/browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42)

[w3c/browser-payment-api] Move PMI and Card specs out of repo (#207)

[w3c/browser-payment-api] Payment Instrument clarification (#104)

[w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209)

[w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141)

[w3c/browser-payment-api] Remove special case handling for single shipping option. (#210)

[w3c/browser-payment-api] Remove totalAmount per telcon resolution. (#219)

[w3c/browser-payment-api] Remove unnecessary clause about validation. (#213)

[w3c/browser-payment-api] Removing notes for closed issues. (#214)

[w3c/browser-payment-api] Rename remaining types so that all begin Payment* (#208)

[w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3)

[w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4)

[w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8)

[w3c/browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45)

[w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215)

[w3c/browser-payment-api] Should show() be renamed? (#127)

[w3c/browser-payment-api] Should the browser pass user data it has collected (email etc) to the payment app? (#194)

[w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51)

[w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2)

[w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109)

[w3c/browser-payment-api] Should we support a delegated state for PaymentRequest? (#7)

[w3c/browser-payment-api] Simple editorial fixes. (#212)

[w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175)

[w3c/browser-payment-api] Specifying Mandatory Data (#97)

[w3c/browser-payment-api] Support different amounts per payment method. (#211)

[w3c/browser-payment-api] Support for gift cards and discount codes (#145)

[w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195)

[w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192)

[w3c/browser-payment-api] Update Introduction to describe actors better (#121)

[w3c/browser-payment-api] Update promise rejection (#187)

[w3c/browser-payment-api] Update references to "Payment Transaction Message Specification" (#218)

[w3c/browser-payment-api] What about billing address (#216)

[w3c/browser-payment-api] What component does the payment method intersection? (#103)

[w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146)

[w3c/browser-payment-api] Write-up initial proposal for payment app registration spec (#12)

[w3c/webpayments-method-identifiers] PROPOSAL: PMI identifies payment method specification, constraints for additional granularity (#5)

[w3c/webpayments-method-identifiers] PROPOSAL: PMI identifies payment method specification, use meta-data for additional granularity (#5)

[w3c/webpayments-method-identifiers] PROPOSAL: Use query string parameters for PMI matching (#2)

[w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1)

[w3c/webpayments-methods-card] Added BasicCardRequest dictionary supporting specification of RequiredFields (#4)

Last message date: Wednesday, 29 June 2016 12:03:56 UTC