-
Notifications
You must be signed in to change notification settings - Fork 63
Brand
ianbjacobs edited this page Aug 16, 2018
·
31 revisions
Notes for discussion about visual identity associated with Web payments.
See:
Questions? Contact Ian Jacobs ij@w3.org.
- Create a trusted visual identity for the Payment Request API user experience.
- Examples: RSS logo, HTML5 logo
- Create a full-on "payments brand". We are focused instead on creating a recognized mark for a feature of the Web.
- Merchant sites look different. Does this, for example, mean we should avoid strong color choices?
- The user experience on each platform (Google, Samsung, Microsoft, Mozilla, Opera, etc.) will look slightly different. Contrast this with strongly and consistently branded proprietary payment experiences.
- Efficiency / Speed
- Simplicity / Convenience
- Payment / Money
- Security / Trust
- Flexible enough to work with a wide range of merchant site styles
- Flexible enough to work with different platform branding
- Identity should work on a checkout page where it is the only "buy" button, as well as on a checkout page with more than one brand.
- Needs to scale well to small sizes.
- A version should stand alone without words
- Global: not specific to any currency or payment method.
- Visual identity (to signify payment using the standard)
- Landing page
- Design guidelines
- Ready-made assets for common use cases (code, buttons)
- Do we want to choose a standard color but promote changes to colors for easier integration into merchant sites?
- Black and white version
- PNG, SVG, and EPS.
- Start by experimenting with visual identity alone. Determine later depth of usage guidance.
- Apparently there is a universal currency symbol
- Ian's previous blog post Idea for a Web Payments Visual Identity
The following FAQ questions are derived from the HTML5 logo FAQ
This logo communicates to the user that a particular user action (such as clicking on a button) will invoke a streamlined payment experience facilitated by the browser.
@TBD
This work is attributed to the W3C. Suggested markup: HTML5 Logo by W3C.
Yes, please, we encourage creative uses of the logo! Be creative, have fun, and show your support. (See the earlier question on how the logo is licensed.)
@@TBD
Yes. (See the earlier question on how the logo is licensed.)
Please send comments to site-comments@w3.org
Mailing list archives
Issues
- Secure Payment Confirmation
- Payment Request API
- Payment Method Identifiers
- Payment Handler API
- Payment Method Manifest
- General
- Tokenized Card
- 3DS
- SRC
Tests
Adoption
Previous Topics