FTF Sep2016

The Web Payments Working Group meets 19-20 September 2016 during TPAC 2016; see the TPAC meeting page for information about the venue, etc.

Registration is open until 2 September 2016. Member-visible list of who has registered.

See also:

• WPIG meeting page for 22-23 September.

Goals

Participants welcome to add their goals (please indicate your name).

• Ian Jacobs: Prepare for CFC to advance payment apps to FPWD.
• Ian Jacobs: Determine how to get Payment Request API, PMI, and Basic Card to CR.
• Zach: Leave TPAC with consensus on all the points we need to get payment request API, PMI/manifest, basic card, cash on delivery (new), invoice (new) to CR.

Agenda

DRAFT

Notes:

• Breakouts on day 2
• Avoid key issue discussion after 3pm on Tuesday due to overlap with AC meeting (both chairs will step away as well as others).
• For breakout sessions, there may not be available rooms but we should be able to find informal space.

19 September

• 09:00-09:15 Welcome, agenda review
• 09:15-09:45 Editor report on payment request API and payment method identifiers /manifest status (Zach)
• 09:45-10:30 Payment App Task Force Update (Ian)
  • Payment Apps API
• 10:30-11:00 Break
• 11:00-12:30 Payment request API implementation experience and demos. (Rouslan)
  • Demo of PaymentRequest in Chrome on Android: what's released to the public and what's planned. (Rouslan)
  • Includes from Chinese implementers (Max)
  • Samsung demo (Dongwoo)
  • Hold for other demos
  • Early testing feedback (Shane/Mike5)
  • What's necessary to converge with Apple API?
• 12:30-13:30 Lunch
• 13:30-15:00 Key payment request API issues (Zach)
• 15:00-15:30 Break
• 15:30-16:30 Payment methods (optionally: move push breakout here)
  • Payment method good practice draft (Max)
  • Updates to basic card
  • Cash on delivery (new)
  • Invoice (new)
  • 360Pay (new from Qihoo 360)
  • Tokenized payment specification (Facebook)
• 16:30-17:00 Web Payments HTTP API(Manu)
  • Web Payments HTTP API Next Steps
  • User interaction is expected to be different for automated payments. Why is there a mediator in this model?
• 17:00-17:30 WG process
  • Weekly call schedule
• 17:30-17:45 Recurring / micropayments.
  • AdrianHB: While at TPAC want to start conversation on this (e.g., extend WG meeting? Weds breakout session? Thursday IG session?)

20 September

• 09:00-09:15 Breakout planning
• 09:15-10:30 Breakout session 1
  • Candidate: Push payments, including SEPA spec, Alipay (Roy).
    • For background, see Failure handling from Roy.
    • See also a pull request from Roy for discussion
    • See also comments from AHB with some ideas for a standard way for merchants to track payment status.
  • Candidate: More on payment methods (e.g., tokenization)
• 10:30-11:00 Break
• 11:00-12:30 Breakout session 2 (which may include discussion of key issues)
  • Candidate: Browser vendor walk-through of implementation (Rouslan)
• 12:30-13:30 Lunch
• 13:30-13:45 Overview doc. Start a CFC?
• 13:45-15:00 Breakout reporting and key issue discussion
• 15:00-15:30 Break (also AC meeting starts)
• 15:30-16:30 Testing (Shane)
• 16:30-17:30 Open discussion

Candidate topics

• Status of Overview doc?
• Security considerations
• Implementation experience
  • China
• Testing (following discussion of plan in August)
• What would an "advanced card" spec look like? E.g., more security, more filtering options.

Breakout session ideas

• @@Please add your ideas here

Conflicts

• AC meeting: Tuesday, Thursday 3-6pm