> Any branding logos should come from the payment method owner, not the merchant (for security reasons) Could someone explain what these security reasons are? This seems in conflict with allowing the merchant _"some control over the display of information, both due to branding requirements and the merchant's style requirements"_. The checkout page on the merchant website will never be, or contain, a browser-owned window as this is too easy to spoof. My understanding of the problem we are solving is: 1. A merchant wants to display various elements/buttons on their checkout page and style these and lay them out differently depending on which payment methods the user has available. 2. The browser should be able to facilitate this without revealing to the merchant the actual list of supported methods. So a declarative solution is, the merchant provides all elements for all payment methods they support and provides hints to the browser about how to arrange those elements using CSS based on which methods the user has. -- 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-430237691
Received on Tuesday, 16 October 2018 13:30:15 UTC