Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) from ianbjacobs on 2016-07-20 (public-payments-wg@w3.org from July 2016)

From: ianbjacobs <notifications@github.com>
Date: Wed, 20 Jul 2016 12:01:55 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>, Comment <comment@noreply.github.com>
Message-ID: <w3c/webpayments/issues/159/234048329@github.com>

It doesn't feel to me like a paymentRequest functionality. I see the flow working this way (potentially) from the merchant's perspective:

1) Does the user's browser support these APIs? If no, fail (which means traditional checkout page here and every time I write "fail" below).
2) Does the user have any apps? If no, fail.
3) Call payment request. Are there any matching apps? If no, fail.
    Otherwise, get payment data from app.

So it seems to me that question 2 is outside the scope of payment request API, or at least could be, and thus could be specified separately. I would argue that we should get agreement on the sort of 1-2-3 flow (which I hope to write up separately, btw) before deciding "this goes into payment request API".

Ian

---
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/159#issuecomment-234048329

Received on Wednesday, 20 July 2016 19:02:49 UTC