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

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

From: mattsaxon <notifications@github.com>
Date: Fri, 04 Mar 2016 10:05:37 -0800
To: WICG/paymentrequest <paymentrequest@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>
Message-ID: <WICG/paymentrequest/issues/66/192386021@github.com>
@LaurentCastillo 

>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.

Whilst that may work in simple cases and provide a better user experience in those, how might this work when multiple payment application have the same payment instrument registered? For example a single card may be registered with MasterPass and Google Payments. This could get quite confusing, particularly if a Website support payments from both of those and say Visa, there could be 3 different apps that could present the Visa card information.

@adrianba 

In the demo http://github.adrianba.net/paymentrequest-demo/ when the users selects a card, are they selecting a payment instrument or a payment application?

---
Reply to this email directly or view it on GitHub:
https://github.com/WICG/paymentrequest/issues/66#issuecomment-192386021
Received on Friday, 4 March 2016 18:06:10 UTC

This archive was generated by hypermail 2.3.1 : Friday, 4 March 2016 18:06:11 UTC