Stay organized with collections
Save and categorize content based on your preferences.
Google Pay has certain features and behaviors that are important for
issuers to understand and incorporate into their TSP integration and pre-launch
testing.
Key Google Pay UX flows
Cards can be added to Google Pay either through Google Wallet surfaces or
an issuer's mobile banking app using the Push Provisioning
API. Google Wallet
app surfaces let users enter their card details in multiple ways, including
autofilling the details using a card already stored on file, OCR
scanning, and manual entry.
In the Netherlands, cards can also be added through Google Wallet using NFC,
by tapping and holding the card to the back of the device:
The UX flows below show common user flows for adding a card to Google Pay
on a phone, tablet, and watch.
Phone and tablet tokenization experience
Wear OS by Google tokenization experience
Phone helper screens:
Transaction screens
Google Pay can be used to make NFC transactions in stores, make in-app
payments, and make online payments.
Token deletion behavior
Tokens can be deleted for a variety of reasons other than a user deciding to
manually delete a token using the Google Wallet app. Notably, after 90 days of
device inactivity, Google Pay initiates token deletion for the given
device from our servers. To be considered active, a device needs to be turned on
and connect to Google's servers once every 90 days. In scenarios where a device
is active, Google does not proactively delete unused tokens or tokens that are
pending activation, unless the token meets one of the specific criteria listed
in the following table.
User Action
Device Tokens
TSP Tokens
Delete one or more tokens manually using the Google Wallet app or the Push Provisioning API
Deleted
Deleted
Remove device lock (PIN, pattern)
Deleted
Deleted (best effort)
Remove Google Account (via Settings/Accounts)
Deleted
Deleted after 90 days
Factory reset
Deleted
Deleted after 90 days
Powered off device (or broken device that fails to power on)
N/A
Deleted after 90 days
Remotely wipe device using Android Device Manager
Deleted
Deleted
Remotely lock device using Android Device Manager
Disabled
Deleted if phone unreachable
Clear all data from Play Services (via Settings)
Deleted
Deleted when user opens Google Wallet app
Clear all data from Google Wallet app (via Settings)
Unchanged
Deleted after 90 days
Supported OCR formats and countries
Google Pay supports OCR recognition of a variety of card formats to
capture a card's PAN and expiry date. Google Pay's OCR tool supports the
following card formats:
15 digits in a single line grouped 4-6-5
15 digits in a single line grouped 6-4-5
16 digits in a single line grouped 4-4-4-4
16 digits in a single line grouped 6-3-3-4
16 digits in a single line grouped 6-3-6-1
19 digits in a single line grouped 6-4-5-4
16 digits in a single line grouped 6-3-8
16 digits in a single line grouped 6-6-5
17 digits in a single line grouped 6-9-2
19 digits in a single line grouped 7-7-5
19 digits in a single line grouped 7-12
19 digits in a single line grouped without spaces
OCR for adding a card into Google Wallet is supported in all countries where
Google Wallet is live. Review the list of where you can use Google Wallet for
payments and storing passes
to see if OCR is available in your country.
Requesting new OCR formats
If you have been granted access to this content, make sure you are signed in with your
authorized Google account. If you are a partner who needs access, use the button below for
instructions on how to request access.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eGoogle Pay allows users to add cards via the Google Wallet app or an issuer's app using the Push Provisioning API.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Pay supports various card entry methods, including OCR scanning and manual entry, and NFC-based card addition in the Netherlands.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Pay can be used for in-store, in-app, and online payments.\u003c/p\u003e\n"],["\u003cp\u003eTokens can be deleted due to user actions, device inactivity, or security measures like removing device locks.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Pay's OCR technology supports a range of card formats and is available in numerous countries.\u003c/p\u003e\n"]]],["Google Pay allows card addition via Google Wallet or issuer apps, using methods like autofill, OCR scanning, or manual entry; in the Netherlands, cards can be added using NFC. Tokens can be deleted manually or automatically due to device inactivity (90 days), device lock removal, factory resets, or clearing data. OCR scanning supports various card number formats and is available in numerous countries. The OCR feature is for capturing card information, while token deletion is triggered by certain user actions or inactivity.\n"],null,["Google Pay has certain features and behaviors that are important for\nissuers to understand and incorporate into their TSP integration and pre-launch\ntesting.\n\nKey Google Pay UX flows\n\nCards can be added to Google Pay either through Google Wallet surfaces or\nan issuer's mobile banking app using the [Push Provisioning\nAPI](/pay/issuers/apis/push-provisioning). Google Wallet\napp surfaces let users enter their card details in multiple ways, including\nautofilling the details using a card already stored on file, [OCR\nscanning](/pay/issuers/tsp-integration/gpay-flows#supported_ocr_formats_and_countries), and manual entry.\n\nIn the **Netherlands**, cards can also be added through Google Wallet using NFC,\nby tapping and holding the card to the back of the device:\n\nThe UX flows below show common user flows for adding a card to Google Pay\non a phone, tablet, and watch.\n\nPhone and tablet tokenization experience\n\nWear OS by Google tokenization experience\n\nPhone helper screens:\n\nTransaction screens\n\nGoogle Pay can be used to make NFC transactions in stores, make in-app\npayments, and make online payments.\n\nToken deletion behavior\n\nTokens can be deleted for a variety of reasons other than a user deciding to\nmanually delete a token using the Google Wallet app. Notably, after 90 days of\ndevice inactivity, Google Pay initiates token deletion for the given\ndevice from our servers. To be considered active, a device needs to be turned on\nand connect to Google's servers once every 90 days. In scenarios where a device\nis active, Google does not proactively delete unused tokens or tokens that are\npending activation, unless the token meets one of the specific criteria listed\nin the following table.\n| **Key Point:** The most common questions around token deletions are the scenarios where a device has been offline for 90 days, typically because they were powered off, broken, or factory reset. This scenario can be especially confusing if the issuer sends servicing messages notifying the user of the deletion. Another common reason for a deletion is when a user removes their device lock.\n\n| User Action | Device Tokens | TSP Tokens |\n|---------------------------------------------------------------------------------------------|---------------|-------------------------------------------|\n| Delete one or more tokens manually using the Google Wallet app or the Push Provisioning API | Deleted | Deleted |\n| Remove device lock (PIN, pattern) | Deleted | Deleted (best effort) |\n| Remove Google Account (via Settings/Accounts) | Deleted | Deleted after 90 days |\n| Factory reset | Deleted | Deleted after 90 days |\n| Powered off device (or broken device that fails to power on) | N/A | Deleted after 90 days |\n| Remotely wipe device using Android Device Manager | Deleted | Deleted |\n| Remotely lock device using Android Device Manager | Disabled | Deleted if phone unreachable |\n| Clear all data from Play Services (via Settings) | Deleted | Deleted when user opens Google Wallet app |\n| Clear all data from Google Wallet app (via Settings) | Unchanged | Deleted after 90 days |\n\nSupported OCR formats and countries\n\nGoogle Pay supports OCR recognition of a variety of card formats to\ncapture a card's PAN and expiry date. Google Pay's OCR tool supports the\nfollowing card formats:\n\n- 15 digits in a single line grouped 4-6-5\n- 15 digits in a single line grouped 6-4-5\n- 16 digits in a single line grouped 4-4-4-4\n- 16 digits in a single line grouped 6-3-3-4\n- 16 digits in a single line grouped 6-3-6-1\n- 19 digits in a single line grouped 6-4-5-4\n- 16 digits in a single line grouped 6-3-8\n- 16 digits in a single line grouped 6-6-5\n- 17 digits in a single line grouped 6-9-2\n- 19 digits in a single line grouped 7-7-5\n- 19 digits in a single line grouped 7-12\n- 19 digits in a single line grouped without spaces\n\nOCR for adding a card into Google Wallet is supported in all countries where\nGoogle Wallet is live. Review the list of where you can [use Google Wallet for\npayments and storing passes](https://support.google.com/wallet/answer/12060037)\nto see if OCR is available in your country.\n\nRequesting new OCR formats \n| You must be logged in to see this section.\n\nIf you have been granted access to this content, make sure you are signed in with your\nauthorized Google account. If you are a partner who needs access, use the button below for\ninstructions on how to request access.\n[Sign in](https://accounts.google.com/AccountChooser?continue=https%3A%2F%2Fdevelopers.google.com/pay/issuers/tsp-integration/gpay-flows) [Request access](/pay/issuers/request-access)"]]
