Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) from Krystian Czesak on 2017-10-11 (public-webpayments-specs@w3.org from October 2017)

From: Krystian Czesak <notifications@github.com>
Date: Wed, 11 Oct 2017 18:54:57 +0000 (UTC)
To: w3c/payment-handler <payment-handler@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-handler/issues/218/335912010@github.com>

> I think there are some UI challenges that would need to be figured out here because many existing implementations capture this information in parallel with payment handler selection. [...] That said, if those options changed each time I selected a payment handler that would suck.

Totally agree, the biggest concern here is less about the API but more about the UI. What if the payment method was presented upstream as a first step to the `PaymentRequest` sheet? Something like this:

![img_5716](https://user-images.githubusercontent.com/1095896/31460068-2161c0be-ae93-11e7-81ca-4c6025ee702b.JPG)
(I suck at drawing stuff)

This way, the requested user data becomes a function of the payment method, not a hard requirement of the `PaymentRequest` UI.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-handler/issues/218#issuecomment-335912010

Received on Wednesday, 11 October 2017 18:55:43 UTC