W3C

Web Payments Working Group

15 Jun 2017

Agenda

See also: IRC log

Attendees

Present
Ian, nicktr, Frank, AdrianHB, zkoch, cweiss, Andras, Ken, adrianba
Regrets
oyiptong
Chair
NickTR
Scribe
Ian

Contents


<scribe> Scribe: Ian

--> https://github.com/w3c/webpayments/wiki/Agenda-20170615 Agenda

Pull request 536

nicktr: AdrianHB, Ian and I spoke about this on Monday and there has been subsequent discussion online

straw poll last week was in support of the pull request

AdrianHB: The short version of my take - I think that we force browsers to do more work with this proposal. But I am ok to concede to the consensus of the group on the PR
... however, there are are some bits in the pull request that go beyond data validation that need attention.
... marcos has changed the algorithm so that it is less about matching payment methods
... I am ok to move forward with the data validation (though I am not supportive of it)
... but we need to fix the PR so that it doesn't break things that were previously there about payment method matching

<zkoch> ::looking at recent comments::

zkoch: The editors did not meet yesterday.
... what is the core piece that disregards the original algo

zkoch, see => https://github.com/w3c/browser-payment-api/pull/536#pullrequestreview-44284185

AdrianHB: One piece of the previous text that needs to stay is about matching PMIs
... that's been lost in Marcos' edits
... it's about data validation but no longer talks about matching
... my take is there are 2 steps:

1) Loop through things and validate data

2) Match payment methods and choose payment handlers

zkoch: I don't have strong views on the ordering of the steps

<li> Determine which <a>payment handlers</a> support any of the

- <a>payment method identifiers</a> given <var>identifiers</var>.

- For each resulting payment handler, if payment method specific

- capabilities supplied by the payment handler match those provided

- by <var>data</var>, the payment handler matches.

zkoch: I agree with AdrianHB and Ian that the text needs to address both topics. I will help coordinate the fix

Ian: +1

<adrianba> +1

nicktr: Are we in a position to say that we can move forward with the proposal from last week?

The proposal was: "For w3c-defined payment methods (i.e., those with short strings), PR API implementations MUST validate payment method request data that can be validated economically"

NickTR: Hearing no objections, SO RESOLVED

<nicktr> +1

<adrianba> yes, and we need to fix the pull request to reflect that

Testing

<Zakim> nicktr, you wanted to ask if Ian could point at the test repo in IRC

https://github.com/w3c/webpayments/wiki

https://w3c-test.org/payment-request/

NickTR: Let's also send email to the list to ask for more resources

<scribe> ACTION: NickTR to send a request for test resources to the WPWG list [recorded in http://www.w3.org/2017/06/15-wpwg-minutes.html#action01]

<trackbot> Created ACTION-60 - Send a request for test resources to the wpwg list [on Nick Telford-Reed - due 2017-06-22].

Adrian's Excellent Trip Report

AdrianHB: I mostly wanted to thank Andre and Shopify who attended the hackathon at our Berlin Interledger workshop
... they spent the day building a payment app (Android) that accepts payment requests and makes payments using Interledger payment method
... if you run your own inter ledger node, you can connect with others and build a network of nodes that have payment relationships with one another
... any one of them can pay any of the others even if they do not have a direct relationship.
... what the hackathon demonstrated was that if the merchant had a node and if the user had a payment app supporting interledger, they could pay
... the way it works is that there's a URL in the payment request..the payment app fetches data at that URL
... the payment app uses inter ledger to get a quote for how much it will cost to pay the merchant, and then it makes the payment

IJ: can you say more about the workshop?

AdrianHB: Interledger is being developed in a CG. The workshop was 2 days (first day presentations and demos, day 2 hackathons). We had 60 people day 1, 40 on day 2
... we did a demo of an inter ledger payment that passed through 7 systems...this demo got picked up by the press
... I also blogged about the event
... I expect to have a good demo at TPAC

nicktr: Thanks for the interesting news

TPAC 2017

IJ: WG will meet 6-7 Nov

<AdrianHB> Link to blog: https://adrian.hopebailie.com/making-history-in-berlin-78f1533787f0

---> https://lists.w3.org/Archives/Public/public-payments-wg/2017Jun/0016.html Announcement re: registration

<AdrianHB> Links to all demo stuff from Shopify are in there too

IJ: PLEASE book your hotel early
... We are likely to recharter the WP IG before then and there's a draft charter for a Commerce IG
... that group would meet Thurs and Fri

https://www.w3.org/2017/03/commerce-charter.html

NickTR: On Weds I am chairing an executive summit in conjunction with TPAC

8 November

Executive Forum

(13:15-18:00)

(No link available yet)

Other notes

Ian: Good progress on tokenization, credit transfer, payment handler (changes driven by implementation experience from Google and Samsung)

Next meeting

22 June

Summary of Action Items

[NEW] ACTION: NickTR to send a request for test resources to the WPWG list [recorded in http://www.w3.org/2017/06/15-wpwg-minutes.html#action01]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/06/15 14:32:40 $