Skip to content

Agenda 20160512

ianbjacobs edited this page May 12, 2016 · 18 revisions
  • July FTF meeting. Please register.

  • TPAC 2016. Please register for TPAC.

  • Payment Method Identifiers

    • PR 183 - Update to method identifiers spec to use absolute URLs (significant changes in the PR, please review before call)
    • Issue 10 - Should well-known identifiers be used for ubiquitous payment methods
    • Issue 11 - What is the format for payment method identifiers for distributed extensibility
    • Quick discussion to enable group to go and work on proposals to define other details (@adrianhopebailie, @mattsaxon, @ianbjacobs)
  • Filtering out unsupported payment methods (No proposals - time-boxed discussion)

    • Issue 157 - Should the payment mediator pass all payment method data to the payment app or just relevant data?
  • Requesting user data (No proposals - time-boxed discussion)

  • API design issues

    • Issue 16 - Use navigator.payments singleton, factory method, or PaymentRequest constructor.
    • Issue 122 - Format of complete()
      • See PR 191 - Explain how to treat unrecognised complete values
    • PR 179 - Add support for ShippingOption.selected
  • Multi-currency

    • Issue 3 - Provide amounts in more than one currency?
    • Issue 178 - Dynamic Currency Conversion (DCC) Support
  • Different amounts per payment method

    • Issue 4 - Vary amounts depending on payment method ?
  • Restricting to top-level browsing context

    • Issue 2 - Payment Request API only available in a top-level browsing context?
  • Flow diagram for browser spec

Postponed

  • Issue 15 - Combine API parameters into a single request object + options. (Proposal required)
  • Upcoming proposal on payment app integration with UA (registration and interfacing for request and response messaging).
Clone this wiki locally