Code A Thon 2020

The Web Payments WG had to cancel its 1-2 April 2020 code-a-thon in Dublin. The WPWG held a virtual code-a-thon on 26-28 May 2020.

Minutes:

• 26 May
• 27 May
• 28 May

Goal

Our goal is for participants to demonstrate through code that Payment Request, Payment Handler, and related APIs may be used to create compelling checkout experiences for a variety of payment method and authentication flows.

Participation

• People from the Web Payments and Web Authentication Working Groups are invited to participate
• The WPWG co-Chairs and Team Contact may invite additional guests

Agenda

All times below are US Pacific (UTC).

• 26 May: 9am (4pm) - 11am (6pm) : Ideation and Tools
  • As a way to help participants self-organize into topics of interest, participants will suggest topics via short lightning talks (3-5 minutes).
  • Introduction to tools for building experiments
• 27 May: 9am (4pm) - 11am (6pm) : Progress, challenges, questions
• 28 May: 9am (4pm) - 11am (6pm) : Reporting

Logistics

• Calendar invitation (requires Member access).
• We expect to use video conferencing for the scheduled agenda sessions.
• We will use IRC for synchronous sessions (irc.w3.org in #wpwg-code). We encourage all participants to hang out there and use it.
• Participants may use any channels they want (e.g., Slack or IRC) for their projects, but public logs of technical discussion are expected.

Initial Topic Ideas for Ideation

• Airbnb: integrate card on file into PR API UX
• Airbnb: use PR API for account creation
• Chrome: payment app selector user interface in the browser. In other words, the sheet is reduced to a selector.
• Chrome: Preferred payment handler.
• Chrome: Minimal UX payment handler
• Chrome: How to store authentication results for future reference from a payment handler (and/or embedded iframe). For example, some identity information stored in indexDB.
• Ian: ShowCheckoutButtons. Addresses privacy issues; let's user select a payment handler first, before merchant calls PR API. Merchants could control color palette of the selector (or other customizations such as the name of the primary action button).
• Chrome: Show UX when the merchant calls PR API (like microphone icon used to show that mic is active). Click on the icon to set the default payment handler for the site.
• Chrome: New consent / awareness behaviors based on privacy analysis.
• Chrome: Clarify for user status when payment handler window is open (e.g., things a web page cannot do such as blur the browser top nav bar).
• STET: Open banking API flow (cf diagrams)
• Payment handler updates instrument information in the background.
• Payment handler unregisters itself once payment instrument is no longer available.
• Secure Remote Commerce
• Bill Pay
• Making donations easier
• Mobile money
• Creating a good-looking demo to show off the APIs.
• Entersekt: Fast Checkout”: E-commerce Push Provisioning (mobile)
• Entersekt: “Pay using QR”: QR Inside a Payment Handler

Resources

• Web-based Payment Handler Starter Kit
• How to FIDO