Issue Summary

WORK IN PROGRESS

Under each issue one or more proposals are listed and following each are the:

• arguments in favor of the proposal, followed by one or more:
  • counter-arguments

Gathering shipping address data

• Discussion: 39,
• Proposals: 63 - January 21
• Consensus Reached: No

Proposal

The Web Payments browser API SHOULD NOT support the collection of shipping information through API calls

• There is work being done elsewhere at W3C to develop a system for gathering this kind of information. The Credentials Management API could be used to get shipping address credentials from the browser and is a more appropriate API for this function.

  • @mikewest (editor of the Credentials Management API) has stated that the API is not currently the right place to do this as the API is narrowly scoped to handle login credentials. He suggests that any group wishing to extend the API for other purposes should write a concrete proposal and get input on this proposal.

  • @nickjharper

• It is possible for websites to gather shipping address information without an API today so there is not a strong requirement for this feature.

• There are other pieces of data that may be important to a payment request (billing address, loyalty program details, subscriber number, etc.) and the group should not presume it can define an API for gathering all of these so there is a case against designing the API for this special case.

  • The reasoning for this comes from the fact that user agents already hold this data and re-using for a better checkout user experience aligns precisely with one of the primary goals of this group: reducing the number of users that drop off from a checkout.

  • No other pieces of data can be gathered directly from the browser. This feature would not require a direct channel of communication between the payment app and the website (feature that may be impossible to provide in some deployment scenarios such as mobile).

Proposal 2

Getting the shipping address via this API will enable the user experience to be implemented by browsers in a way that will improve the checkout experience and is an appropriate use of the browsers ability to provide this data.

• Physical good purchases are the majority of online transactions and part of that flow is the collection of shipping information.

• Shipping information is special because, unlike loyalty cards, etc, it is impossible to fulfill the transaction without it. It is both ubiquitous and critical across all physical good transactions.

Stateful vs stateless API

• Discussion: 41
• Proposals:
• Consensus Reached: No

ISSUE 2:

• Title: Expression of Monetary Amounts
• Issues Number: 40
• Consensus Reached: No

Difference 4:

• Title: Payment Details
• Issues Number: 38
• Consensus Reached: No

Difference 5:

• Title: Accepted Payment Methods format
• Issues Number: 37
• Consensus Reached: No

Difference 6:

• Title: Payment Request is Object or Data
• Issues Number: 36
• Consensus Reached: No

Difference 7:

• Title: Payment Request Status
• Issues Number: 35
• Consensus Reached: No