- From: ianbjacobs <notifications@github.com>
- Date: Wed, 12 Sep 2018 15:39:10 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 September 2018 22:39:32 UTC
Hi @asolove-stripe, It seems to me that payment method owners own the branding requirements. If automatic selection based on the payment method manifest does not suffice, we could enhance (and complicate) this approach by enabling the merchant to express a preference for size and color, from among the logos authorized by the payment method owner. So the merchant does not provide the logo (which would raise security issues) but instead expresses a preference (e.g., for a specific icon) that is verified by the browser against the options offered by the payment method owner. Errors could be managed by the browser showing something authorized by the payment method owner. There are other approaches as well, such as the merchant specifying a target height (for example) and letting the browser try to optimize logos for that height. I hear the point and, if there's interest overall, we can get suggestions from the group. Perhaps a tougher point would be ordering of the logos. However, there may be a way to leverage existing data from Payment Request API for that. -- 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-420821573
Received on Wednesday, 12 September 2018 22:39:32 UTC