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

@Krystosterone, thanks for sharing these ideas. Of your goals, I like "Help set buyer expectations about their purchase journey?" and "Help adoption of PaymentRequest?" I would reframe "Ensure that payment method branding is well represented upstream?" as "Ensure that PaymentRequest supports the realities of requirements related to payment method branding."

I need to think more about your Idea 2.

I am hearing the desirable properties:

 * The merchant wants some control over the display of information, both due to branding requirements and the merchant's style requirements. 

* Any branding logos should come from the payment method owner, not the merchant (for security
reasons). E.g., if the payment method owner specifies icons in a Web App Manifest, perhaps the merchant could just refer to entries in that manifest. I don't know whether this would offer merchants sufficient flexibility.

* We want to leak as little information about the merchant environment as possible with the merchant prior to payment handler selection.



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