This page provides answers for frequently asked questions about Google Pay Card Metadata.
What are the business benefits of displaying card art and name in Google Pay?
Displaying card metadata (card art and name) will boost brand recognition of the issuer and its card products.
It also improves the user experience by helping to quickly and accurately identify a card at the point of purchase for a quicker check out experience.
We are already opted into Mastercard MDES and Visa VTS. What else do we need to do in order to implement the card art & name design enhancement?
There is no technical action required. However, we do suggest reviewing and verifying existing card (short) name and card art product mapping with network partners to ensure accuracy.
Within MDES or VTS card management systems, where will Google be pulling card name & card art metadata from?
For MDES, both cardName and artUri are present in the response of GET on /cards/{cardId} endpoint. In the response, cardName and artUri are present inside maskedCard -> digitalCardData -> artUri, descriptorName.
For VTS, both cardName and the digitalCardArtGuid are present in the response of GET on /vts/panEnrollments/{vPanEnrollmentId}. In the response, cardName and guid are present inside cardMetaData -> longDescription and cardMetaData -> cardData -> guid respectively.
How quickly will changes to MDES and VTS systems be updated in autofill?
User cards must have an ecommerce token to be eligible for this design enhancement.
Rollout of this design enhancement will occur in a phased manner over the course of a few months so all products may not roll out in the same phase.
Quality checks(QC) will be performed on all card names based on the following criteria: formatting, appropriate and useful. If a card name does not pass QC, we will revert to the existing experience displaying the network logo and name. Examples of issues that would cause a card name to fail QC include, but are not limited to: incorrect spelling, all capital letters or a non product name was returned in the field. Please note, card art won't be displayed if card product name fails QC.
| (1) Formatting | (2) Appropriate | (3) Useful |
|---|---|---|
| Card names should be formatted correctly for readability and presentation in the user's region. | The card name shouldn't have any obscene or inappropriate content. | The card name conveys more useful information than the status quo (network name + last four digits) |
If an issuer sees card name & art that is not correct in autofill what is the escalation path or procedure for them to correct this?
Given Google receives the card product name and art from the network spec, the first action an issuer should take is to confirm they have provided the correct card product name and card art information to the respective card network and the network has successfully notified Google.
However, if the card name and art are correct in VTS/MDES, but it is being incorrectly displayed in autofill, the issuer should alert their network POC who can escalate to their network global team and subsequently work with Google to investigate the issue.
In the interim period during support resolution, Google can revert to network art and name (which was displayed prior to the enhancement).
Will the card product name & card art in autofill be the same as what is shown in Google Wallet or will it be separate?
MDES and VTS provide card product name and art to Google with the originating source being the issuer. Autofill pulls the card art from ecommerce tokens, and Google Wallet pulls from DPANs, however a very high consistency is expected. There are also future plans to consolidate these to have identical coverage.
Will the nickname function remain in autofill (and will it synchronize from mobile to browser)?
Yes, user created nickname overrides network card name.
Will card products that are non-eligible for the Google Wallet App receive card art and card name?
Yes, all payment cards with an associated ecommerce token will leverage the corresponding card art and names available in MDES and VTS card management systems.