W3C

Web Payments Working Group

13 Dec 2018

Agenda

Attendees

Present
Danyao Wang (Google), David Ezell (NACS), Ian Jacobs (W3C), Jeff Williams (TCH), Luis Guzman (NACHA), Matt Detert (MAG/BAMS), Nick Telford-Reed, David Benoit (Reach), Tony England (Bank of America), Chris Michael (Open Banking UK), Rouslan Solomakhin (Google), Krystian Czesak (Shopify), Roy McElmurry (Facebook), Lawrence Cheng (Barclays), Dean Ezra (Barclays)
Regrets
Adrian Hope-Bailie (Coil)
Chair
Nick Telford-Reed
Scribe
Ian

Contents


<scribe> Scribe: Ian

present_

Add hasEnrolledInstrument to Payment Request API v1?

--> https://lists.w3.org/Archives/Public/public-payments-wg/2018Nov/0018.html Call for Feedback

<krystosterone> +1 on Ian's proposal

Proposed: Request the editors specify the feature and develop a pull request but not include the feature in Payment Request v1.

benoit: What is the expected timeline for that change in the formal specification?

<benoit> +1 on Ian's proposal

IJ: Is the expectation to converge on safari?

rouslan: Yes, i think the expectation is to converge on Safari behavior
... we already have canMakePayment() that does what hasEnrolledInstrument() will do ... so we need to do this carefully
... our plan would be to roll the new method out at the same time.
... we are going to recommend to web developers to detect the presence of hasEnrolledInstrument... if so, use it as specified; if not, assume older version and use canMakePayment

IJ: Definition "definition of canMakePayment"
... to include on the fly registration
... does that require a change in definition in the spec?

Rouslan: This does not require changes to the spec.
... spec says "is available' rather than "is registered"

IJ: How clear does "is available" have to be?
... what about offline, 404, etc.?

Rouslan: Good question; right now in Chrome they ping the manifest and "true" if no 404
... so "true" means server online and 200 ok

<nicktr> +1

IJ: Any objections?

[None articulated]

IJ: Action: Ian to reach out to the Editors to recommend beginning to spec out this feature and start work on implementation, but not for V1 of Payment Request API.

Upcoming (december, january) meeting schedule

10 Jan for this group

<matt_d> +1 on Ian's suggestion for a year-end summary and forward look

IJ: May work on end of year/looking forward blog post with Chairs

Face-to-face meeting schedule

Proposed: Two days during week of 11 March

https://www.ietf.org/how/meetings/104/

IETF 23-24 march

IJ: Any host volunteers?
... Any conflicts?
... I'd like to finalize dates by next Thursday

NickTR: +1

TPAC 2019 is 16-20 September in Japan

Tony: 6 March is EMVCo Board of Advisors meeting

Lawrence: 9 April AC meeting in Quebec

IJ: Would quebec be interesting (e.g., 10-11 April)?

[EMVCo meets week of 8 April in N.O.)

week of 1 April ?

Lawrence: Who is planning to go to the AC meeting from this call?

Chris: March suits me better for the WG meeting

Dezell: I plan to go to the AC meeting in Quebec

Nick: Let's create a doodle

<scribe> ACTION: NickTR to create a meeting doodle for FTF

<trackbot> Created ACTION-111 - Create a meeting doodle for ftf [on Nick Telford-Reed - due 2018-12-20].

IJ: AOB end of year?

NickTR: I really appreciate all the efforts that people put in over the course of the year and Ian who keeps plates spinning
... and to publishing in 2019!
... talk to you soon!

Summary of Action Items

[NEW] ACTION: NickTR to create a meeting doodle for FTF
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2018/12/13 15:54:39 $