Web Payments Working Group FTF Meeting (July 2016)

Minutes

• 7 July
• 8 July

Agenda

Day 1

• 08.30-09:00 Agenda bash, administrivia
  • Firming up evening meal plans
  • Introductions
• 09:00-10:30 Payment App Specification. Introduction and primary issues. How do users interact with these when not doing a payment?
  
• 10.30-11.00 Break
  
• 11:00-13:00 Payment Request API implementation experience. What have implementers encountered as issues?
  
• 13:00-14:00 Lunch
  
• 14:00-15:00 Payment method specs. Review existing (basic card) and new (e.g., basic ct-dd payment, Alipay)
  
• 15:00-15:30 Testing Strategy. Reintroduce topic so plan can be developed after FTF meeting
  
• 15.30-16.00 Break
  
• 16.00-17:00 Security review (or PDF) based on TAG self-review checklist.
  
• 17:00-17:30 Payment App Spec (continued). Focus on communication and registration.
  
• 19.00 Dinner

Day 2

• 08.30-09.00 Agenda bash, administrivia, breakouts
• 09:00-09:20 "Explainer" text take-up
• 09:20-09:45 Payment Method Identifier Spec
  • Review PMI use cases
  • Bootstrapping the ecosystem
• 09:45-10:30 Web Payments Core Messages and Web Payments HTTP API
  • Presentation on Core Messages and HTTP API
  • Move to FPWD?
• 10:30-11:00 Break
• 11:00-11:30 Testing Strategy
• 11:30-12:00 Payment app specification - can we take up as a WG editors' draft?
• 12:00-13:00 Breakouts: Payment Apps, Payment Methods, Payment Method Identifiers)
• 13:00-14:00 Lunch
• 14:00-14:30 Breakout plenary
• 14:30-15:30 Reserved for emerging issues
  • What issues need to be addressed to get payment request API to CR?
• 15:30-16:00 Break
• 16:00-17:00 Actions and next steps

See the list of Non-postponed, non-low-priority, open issues

Introduction

The Web Payments Working Group will meet Face to Face in London 7-8 July 2016. This page describes the logistics of the meeting and lays out an agenda for both days.

Primer for new participants and guests

New participants to the group and guests for the face-to-face meeting might find it useful to have a summary of work-to-date and links to the working set of documents.

You can find a history of the group on the main page of our wiki and the scope of our activity laid out in our charter.

There is series of wiki articles outlining the proposed architecture of the specifications.

Published working drafts

We arrive at the face to face meeting with published working drafts of three specifications:

• Payment Request API: This specification describes a web API to allow merchants (i.e., web sites selling physical or digital goods) to easily accept payments from different payment methods with minimal integration. User agents (e.g. browsers) will facilitate the payment flow between merchant and user.
• Payment Method Identifiers: This document defines payment method identifier strings so that components in the payment ecosystem can determine which parties support which payment methods.
• Basic Card Payment: This specification describes the data formats used by the Payment Request API to support payment by payment cards such as credit or debit cards.

Editors' drafts

There are also documents which are editors' drafts (so more current) of specifications, but which have not gone through the W3C's publication process and so are less 'stable' but reflect the most up-to-date conversations in the group.

Specifications

• Payment Method Identifiers - https://github.com/w3c/webpayments-method-identifiers
• Payment Request API - https://github.com/w3c/browser-payment-api/
• HTTP API - https://github.com/w3c/webpayments-http-api
• Payments Core Messages - https://github.com/w3c/webpayments-core-messages

Payment Method Specifications

• Card - https://github.com/w3c/webpayments-methods-card
• Credit Transfer and Direct Debit - https://github.com/w3c/webpayments-methods-credit-transfer-direct-debit

Proposed Specifications

Ther are a further two specifications which remain proposals until being abandoned or adopted as editor's drafts by the WG.

• Payment Apps - https://w3c.github.io/webpayments/proposals/paymentapps/payment-apps.html
• Alipay Payment Method - https://w3c.github.io/webpayments/proposals/Alipay-payment-method.html

Proposed explainer text

There is also a helpful "explainer" text which is still a proposal at time of writing - nevertheless, new participants might find it instructive.

Admin

• Need name, email company of each participant 1 week in advance.

**Registration has now closed

• When: 7-8 July 2016, hosted by Visa Europe
• Where: 1 Sheldon Square, London W2 6TT
• Remote access information Password required to access. Participants who do not have access to that information should contact Ian Jacobs.

Related meetings:

• Blockchains and the Web W3C Workshop, 29-30 June 2016 at MIT in Cambridge, MA, USA
• WPIG FTF meeting, 1 July 2016 at MIT in Cambridge, MA, USA

Accommodations

• Novotel London Paddington - £190.00 (ask for Visa rate)
• Hilton London Metropole - £259 (no Visa rate available on these dates)
• Royal Park Hotel - £191 excl VAT (+20%) (ask for Visa rate)

Meeting Priorities

• Payment request API and PMIs
• Security review of those specifications
• Payment Apps
• Payment method specifications
• Testing
• HTTP API

Guests

• Lauren Jones (ISO TC 68)
• Sebastien Seguin-Gagnon (Google)
• Florian Dold (INRIA)
• Robleh Ali, Simon Scorer (Bank of England)
• Faraz Babar (Amex technologies)
• Charlie Craven, Huw Bailey, Ben Smith (Amex network)
• Suki Chana and Ajay Rambocus (GSMA)
• Dapeng and Jiajia (Alibaba)
• Andrea Feinberg (BlueSnap)
• Nicolas Ancot, Pirouz Habibi (replacing FM) (Canton Consulting)
• David Birch (Consult Hyperion)
• Fawad Nisar (Discover)
• Evan Schwartz (Ripple)