Agenda 20160512

@@DRAFT

• July FTF meeting. Please register.

• Requesting user data (not just shipping address and options)

  • See start of discussion from last week's call
  • PR 174 - Adding support for phone and email
  • PR 65 - Change the way we request user data (PR withdrawn? - @zkoch)
  • Issue 1 - Requesting email and phone number
  • Issue 27 - Should API support billing address capture (for tax computation)?

• API design

  • Issue 16 - Use navigator.payments singleton, factory method, or PaymentRequest constructor.
    • See Proposal from Manu
  • Issue 122 - Format of complete()
  • 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 - Should it be possible to vary amounts depending on payment method ?

• Restricting to top-level browsing context

  • Issue 2 - Should the Payment Request API only be available in a top-level browsing context?

Postponed

• Issue 15 - Combine API parameters into a single request object + options. AdrianHB plans to write up a new proposal.
• Upcoming proposal on payment apps.