Brand guidelines

If you’re developing for users in RU and JP, please use the “Save to phone” buttons as Google Wallet isn’t live in these countries. Please see the relevant assets and guidelines. If you are developing for users outside of RU and JP, please update your Add to Google Wallet button by downloading the assets below.

This section of the documentation is designed to help you create images and other user interface elements so that they look great in the Google Wallet app.

Add to Google Wallet button

The Add to Google Wallet button is used whenever you are directing users to save a pass or card from your app or website to their Wallet. The Add to Google Wallet button must call one of the Google Wallet API flows. These flows surface the Google Wallet app where users can follow the instructions to save event passes to their Android device and their Google Account. This button can be used in merchant apps, websites or emails.

Assets

Add to Google Wallet buttons are available in AXML, SVG, and PNG format.

Download assets - AXML Download assets - SVG Download assets - PNG

All Add to Google Wallet buttons displayed on your site, app, or email communications must adhere to our brand guidelines outlined on this page. Examples of these guidelines include but aren't limited to, the following:

  • Size relative to other similar buttons or elements of the page
  • Shape and color of buttons must not be altered
  • Clear space

Localized buttons

Localized Google Wallet buttons are provided for all markets where Wallet is available. If you’re developing for users in these markets, always use the buttons linked above. Do not create your own version of the Add to Google Wallet button. If a localized version of the button is not available in your market, use the English version of the button.

The Add to Google Wallet buttons are available in the Albanian, Arabic, Armenian, Azerbaijan, Bosnian, Bulgarian, Catalan, Chinese (Hong Kong), Chinese (Traditional), Croatian, Czech, Danish, Dutch, English (India, Singapore, South Africa, Australia, Canada, Great Britain, United States), Estonian, Filipino, Finnish, French (Canada), French (France), Georgian, German, Greek, Hebrew, Hungarian, Icelandic, Indonesian, Italian, Japanese, Kazakh, Kyrgyz, Latvian, Lithuanian, Macedonian, Malay, Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian (Belarus), Serbian, Slovak, Slovenian, Spanish (Latin America), Spanish (Spain), Swedish, Thai, Turkish, Ukrainian, Uzbek, Vietnamese languages.

Localized name

For user clarity, the Google Wallet product name is localized in select markets. If you’re developing for users in these countries, always use the localized name. For web, email, and print, use the localized name outlined below. Do not create your own localized version of “Google Wallet” If your market isn’t listed below, use “Google Wallet” in English.

Country Name
Belarus Google Кошелек
Brazil Carteira do Google
Chile Billetera de Google
Czechia Peněženka Google
Greece Πορτοφόλι Google
Hong Kong Google 錢包
Lithuania Google Piniginė
Poland Portfel Google
Portugal Carteira da Google
Romania Portofel Google
Slovakia Peňaženka Google
Taiwan Google 錢包
Turkey Google Cüzdan
UAE محفظة Google
Ukraine Google Гаманець
United States (Spanish)
*Use this name in the US if your UI is in Spanish
Billetera de Google

Size

Adjust the height and width of the Add to Google Wallet button to fit your layout. If there are other buttons on the page, the Add to Google Wallet button needs to be equal in size to or larger than these buttons. Don't make the Add to Google Wallet button smaller than other buttons.

Style

The Add to Google Wallet buttons are available in two variations: primary button and condensed buttons. The Add to Google Wallet button only comes in black. Localized versions of the button are provided. Do not create buttons with your own localized text.

Primary Add to Google Wallet button Condensed Add to Google Wallet button

Primary

Use the primary button on white and light backgrounds.

Condensed

Use the condensed button if there is not enough space for the primary or full-width.

Clear space

Always maintain the minimum clear space of 8 dp on all sides of the Add to Google Wallet button. Ensure that the clear space is never broken with graphics or text.
Add to Google Wallet buttons must have 8 dp of space on all sides.

Minimum height

All Add to Google Wallet buttons need to have a minimum height of 48 dp.

Add to Google Wallet buttons must have a minimum height of 48 dp.

Dos and don'ts

Dos Don'ts
Do: Use only the Add to Google Wallet buttons provided by Google. Don't: Create your own Add to Google Wallet buttons or alter the font, color, button radius, or padding within the button in any way.
Do: Use the same style of button throughout your site. Don't: Make the Add to Google Wallet buttons smaller than other buttons.
Do: Ensure that the size of the Add to Google Wallet buttons remain equal to or larger than other buttons. Don't: Alter the button color.
Do: Keep the button ratio the same when resizing the Add to Google Wallet buttons. Don’t: Free scale the button.
Do: Use the provided localized version of the buttons. Don’t: Create your own localized version of the button.

Best practices for button placement

To maximize the number of saved objects, display the Add to Google Wallet buttons prominently within your app, website, or email. Refer to the following best practices to guide your UI design.

Generic passes

Display the Add to Google Wallet button on confirmation app screens, web pages, or emails. We recommend that you place the Add to Google Wallet button where users access their generic passes in your app or website.

Use of the Google Wallet product name in text

You can use text to indicate to the user that their Generic pass is saved to their device.

Capitalize the letters "G" and "W"

Always use an uppercase "G" and an uppercase "W" followed by lowercase letters to refer to Google Wallet. Don't capitalize the full name "Google Wallet" unless it's to match the typographic style in your UI.

Don't abbreviate Google Wallet

Always write out the words "Google" and "Wallet."

Match the style in your UI

Set "Google Wallet" in the same font and typographic style as the rest of the text in your UI. Don't mimic Google's typographic style.

Always use the localized version of "Google Wallet"

Always write "Google Wallet" in the provided localized copy.

Design

Use the height and size fields of the g:savetoandroidpay HTML tag to modify the height and width of the Add to Google Wallet buttons. Use the textsize=large specification to dramatically increase text and button sizes for mobile implementations or cases with special UI requirements.

Use the theme to set the color of the buttons. The following table shows how these settings affect the Add to Google Wallet button.

Hero images

The class.heroImage field appears as a full-width banner across the body of the card.

Hero image guidelines

The following is a list of user interface recommendations for hero images:

Guideline Example
Preferred file type: PNG
Recommended size is 1032x336 px. Use wide, rectangular images. Use an image with a colored background for best results.
3:1 aspect ratio, or wider.
The display size is the full width of the card, and the height is proportional.

Full-width images

The *.imageModulesData.mainImage field in a class or object appears as a full-width image in a pass.

Full-width image guidelines

The following is a list of user interface recommendations for full-width images:

Guideline Example
Preferred file type: PNG
Minimum size is 1860 px wide, variable height. Use wide, rectangular images. Use an image with a colored background for best results.
Variable aspect ratio.
The display size is the full width of the template, and the height scales proportionally.
Use the same color scheme that you use for your logo.

Barcode images

Certain verticals allow for images above and below the barcode.

Images above the barcode

The following is a list of user interface recommendations for the images above the barcode:

Guideline Example
Preferred file type: PNG  
Maximum height is 20 dp (at maximum aspect ratio). Recommended size is 80 px tall and 80-780 px wide if two images are present. This lets them be side by side. If one image is a square and the other is a rectangle, then the images need to be 80x80 px and 780x80 px.
Unconstrained aspect ratio. For maximum 20 dp height and width of a single image, use a 20:1 aspect ratio. If you only want a single image above the barcode, take the full width (exclude padding). The image needs to be 1600x80 px.
Maximum display size for a single image is 20 dp high and 400 dp wide.  

Image below the barcode

The following is a list of user interface recommendations for the image below the barcode:

Guideline Example
Preferred file type: PNG  
Maximum height is 20 dp (at maximum aspect ratio). Recommended size is 80 px tall and 80-1600 px wide. If square, 80x80 px. If rectangular, 1600x80 px.
Unconstrained aspect ratio. For maximum 20 dp height and width, use a 20:1 aspect ratio. If you want a full width image (exclude padding), the image must be 1600x80 px.
Maximum display size is 20 dp high and 400 dp wide.  

Modules

A module represents a group of fields in a specific section of a template. The following table contains guidelines for the number of modules that you must include in your classes and objects to ensure that your cards display correctly in the Google Wallet app.

Guideline Example
Use only one imageModulesData either in your class or in the objects you create.
Use up to two infoModuleData, either in your class or in the objects you create. An infoModuleData might define user account-specific information such as "Member Name" and "Membership #".
Use up to four linksModuleData URIs total in either in your class or in the objects you create. You might have two linksModuleData URIs in your class; one to the URI for your website and one to a phone number for your help center. Two linksModuleData URIs in your object might define a user account-specific URI and nearby locations.
Use up to two textModulesData fields between the class and objects you create. You might have one textModuleData URIs in your class that defines program details and another textModulesData in the object that defines user account-specific details.

infoModuleData

InfoModuleData contains member and customizable information and appears in the expanded view. Use this module to store information such as expiration dates, second point balances, or stored value balances.

linksModuleData

The links module contains URIs to web pages, telephone numbers, and email addresses. The following is a list of user interface recommendations for the links module:

Guideline Example
Use the http: prefix when you assign a URI to a website or a location in Google maps. This prefix lets a consumer touch on the link and navigate to the website or view the location in Google Maps. This prefix also causes an icon of a link or map in front of the description in your Card. 'uri': 'http://maps.google.com/?q=google'

'uri': 'http://developer.google.com/wallet/'

Use the tel: prefix when you define a phone number. This prefix lets a consumer touch on the link to dial the number. This prefix also creates an icon of a telephone in front of the text description on the Card. 'uri': 'tel:6505555555'
Use the mailto: prefix when you define an email address. This prefix lets a consumer touch on the link to send an email to the address. This prefix also creates an icon of an email in front of the text description on the Card. 'uri': 'mailto:jonsmith@email.com'

Headings, labels, and names

Write headings, labels, and names in title case, so that each word starts with a capital letter.

Content policies

The contents of each field in a Pass must adhere to the Payments content policies. The contents of the websites that you reference in the class must also adhere to these policies.

Partner platform data placement

To make sure users can get to your feature-rich app or website about the Pass, make sure to incorporate your app deep link or website in the Pass's class or object linksModuleData.* property. This lets a user navigate to your platform from the Pass, which appears in Google Wallet. To see how it's rendered, go to the design sections of the Pass verticals.