|Initial release||May 26, 2011 (as Google Wallet)|
September 11, 2015 (as Android Pay)
January 8, 2018 (as Google Pay)
|Operating system||Android 5 or later|
Wear OS 2 or later
Google Pay (formerly Android Pay) is a mobile payment service developed by Google to power in-app, online, and in-person contactless purchases on mobile devices, enabling users to make payments with Android phones, tablets, or watches. Users can authenticate via a PIN, passcode, or biometrics such as 3D face scanning or fingerprint recognition.
As of 2022[update], it is currently available in 46 countries. In 2022, a companion app named Google Wallet was released.
Google Pay uses near-field communication (NFC) to transmit card information facilitating funds transfer to the retailer. It replaces the credit or debit card chip and PIN or magnetic stripe transaction at point-of-sale terminals by allowing the user to upload these in Google Wallet. It is similar to contactless payments already used in many countries, with the addition of two-factor authentication. The service lets Android devices wirelessly communicate with point of sale systems using a near field communication (NFC) antenna and host-based card emulation (HCE).
When the user makes a payment to a merchant, Google Pay does not send the actual payment card number. Instead, it generates a virtual account number representing the user's account information.
Google Pay requires that a screen lock be set on the phone or watch. It has no card limit.
Users can add payment cards to the service by taking a photo of the card, or by entering the card information manually. To pay at points of sale, users hold their authenticated device to the point of sale system. The service has smart-authentication, allowing the system to detect when the device is considered secure (for instance if unlocked in the last five minutes) and challenge if necessary for unlock information.
Google Pay uses the EMV Payment Tokenisation Specification.
The service keeps customer payment information private from the retailer by replacing the customer's credit or debit card Funding Primary Account Number (FPAN) with a tokenized Device Primary Account Number (DPAN) and creates a "dynamic security code [...] generated for each transaction". The "dynamic security code" is the cryptogram in an EMV-mode transaction, and the Dynamic Card Verification Value (dCVV) in a magnetic-stripe-data emulation-mode transaction. Users can also remotely halt the service on a lost phone via Google's Find My Device service.
To pay at points of sale, users hold their authenticated Android device to the point-of-sale system's NFC reader. Android users authenticate unlocking their phone by using biometrics, a pattern, or a passcode, whereas Wear OS users authenticate by opening the Google Wallet app prior to payment.
In EMV-mode transactions, Google Pay supports the use of the Consumer Device Cardholder Verification Method (CDCVM) using biometrics, pattern, or the phone's or watch's passcode. The use of CDCVM allows the device itself to provide verification for the transaction and may not require the cardholder to sign a receipt or enter their PIN. Additionally, in certain markets which have a "no verification contactless limit" using contactless cards (such as the £100 limit in the United Kingdom and the CA$100 limit in Canada), the use of CDCVM can enable merchants to accept transactions higher than these amounts using Google Pay, provided that their terminal software is updated to support the latest network contactless specifications.
There is no limit to the number of cards you can add to your device.
How many cards can the Android Pay app store? As many as you would like! There is no limit on the number of cards storable in the Android Pay app.
How many cards can I use with Google Pay? As many as you would like! There is no limit on the number of cards storable in the Google Pay app.