> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/cmp/payment-credentials/google-pay.md).

# Google Pay

### Overview

CMP supports storing Google Pay wallet cards, including Device Primary Account Numbers (DPANs) and Funding Primary Account Numbers (FPANs). CMP securely stores the decrypted DPAN or FPAN and provides a PAN alias for future card retrieval and use.

For subsequent payments, merchants must follow their payment processor's stored credential requirements and applicable card network rules. Google Pay cryptograms are single-use and cannot be reused for future transactions.

Merchants can store Google Pay cards in CMP in two ways:

1. **Submit a decrypted wallet credential (DPAN or FPAN) directly to CMP.** The merchant already has the clear DPAN or FPAN and sends it in the [Create Card API](https://docs.verygoodsecurity.com/cmp/developer-resources/api/cards) request.
2. **Submit an encrypted Google Pay payment token to CMP.** CMP decrypts the Google Pay payload, extracts the underlying DPAN or FPAN, and securely stores the card.

Both approaches result in a card stored in CMP that can be retrieved using the standard [GET /cards/{id}](https://docs.verygoodsecurity.com/cmp/developer-resources/api/cards#get-cards-card_id) API.

### Understanding Google Pay Tokens

When a customer pays using Google Pay, the payment credentials returned depend on the authentication method supported by the card and device.

Google Pay supports two authentication methods: `PAN_ONLY` and `CRYPTOGRAM_3DS`.

#### DPAN (Device PAN)

A **DPAN** is a device-specific tokenized credential associated with a particular device and payment card. Google Pay returns a DPAN when the payment authentication method is `CRYPTOGRAM_3DS`.

**Characteristics:**

* Device-specific tokenized credential.
* Used for customer-initiated Google Pay transactions.
* Includes a single-use payment cryptogram for authorization.
* May include an Electronic Commerce Indicator (ECI), depending on the card network.
* Can be securely stored in CMP.

#### FPAN (Funding PAN)

An **FPAN** is the underlying funding card number. Google Pay returns FPAN-based card data when the payment authentication method is `PAN_ONLY`.

**Characteristics:**

* Represents the funding card rather than a device-specific token.
* Uses the `PAN_ONLY` authentication method.
* Does not include a payment cryptogram.
* Can be securely stored in CMP.

#### Google Pay Payment Authorization

Google Pay returns an encrypted payment token containing either a DPAN with a single-use cryptogram or an FPAN. The merchant sends the encrypted token to VGS CMP for decryption. CMP decrypts the token, securely stores the DPAN or FPAN, and returns the card details along with the cryptogram for DPAN transactions or without a cryptogram for FPAN transactions.

The cryptogram is single-use and is not stored by CMP.

### Google Pay Integration Options

Merchants can choose either of the following approaches:

* [**Create Card - Using DPAN or PAN**](https://docs.verygoodsecurity.com/cmp/payment-credentials/google-pay/create-card-using-dpan-and-pan) — Store an already decrypted Google Pay wallet credential in CMP.
* [**Create Card - Google Pay Wallet Decryption**](https://docs.verygoodsecurity.com/cmp/payment-credentials/google-pay/create-card-google-pay-wallet-decryption) — Submit encrypted Google Pay ECv2 payment data to CMP for decryption and card creation.

For mock testing, sandbox testing, and production setup, refer to the [**Google Pay Wallet Decryption Testing Guide**](https://docs.verygoodsecurity.com/cmp/developer-resources/guides/testing/google-pay-decrypt).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verygoodsecurity.com/cmp/payment-credentials/google-pay.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
