W3C home > Mailing lists > Public > public-payments-wg@w3.org > February 2016

Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66)

From: Laurent Castillo <notifications@github.com>
Date: Wed, 24 Feb 2016 15:35:00 -0800
To: WICG/paymentrequest <paymentrequest@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>
Message-ID: <WICG/paymentrequest/issues/66/188515465@github.com>

> How would this registration work? How, specifically, is it different from what I proposed?

I maybe wrongly reading between the lines, but 'The user picks the Payment App' suggests a model in which the user picks a payment app registered in the browser, then picks a payment instrument registered in the payment app. I suggest skipping a step by registering (a link to) payment instruments directly in the browser, so that users can pick an instrument directly and implicitely select the corresponding payment app.

> How do you recommend the browser become aware?

Good question, maybe an additional explicit call registerPaymentInstrument ?

Reply to this email directly or view it on GitHub:
Received on Wednesday, 24 February 2016 23:35:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:14 UTC