Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777)

Shopify would very much be interested in discussing such an approach; branded buttons and payment method branding is something we think Web Payments can potentially solve elegantly. It  does comes with some inherently interesting difficulties, mainly UX ones.

Some quick thoughts from a merchant perspective:

  - A single container approach is a good starting point, but comes with an interesting set of problems, mainly around not overloading the buyer with information and merchant control around displaying said container. For our merchants, we've not seen this to be the best approach possible.
  - Whatever the solution, some merchants will have legal bounding agreements with payment processors to show them in a specific order. Just something to keep in mind, as @ianbjacobs previously mentioned.

I'd like to clarify what the underlying need and goal of such a spec would be. Are we trying to:
  
  - Help set buyer expectations about their purchase journey?
  - Ensure that payment method branding is well represented upstream?
  - Help adoption of PaymentRequest?
  - All of the above?

I would have though that long term, PaymentRequest's value prop of streamlining the checkout process would trump branding requirements upstream, as their available in the payment sheet. 

I'm excited by this though as I can very well see this spec bridging the gap between currently available payment methods through SDKs and new arrivals present through Payment Request.

-- 
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-request/issues/777#issuecomment-423589004