# Google Pay

## **Storing Google Pay DPAN in CMP**

### **Create Card API Request**

CMP’s Create Card API also supports storing Google Pay digital wallet cards (DPANs), along with standard physical cards (PANs).

Cards classified as `dpan`  from Google Pay do **not** activate downstream services like Account Updater or Network Token provisioning, even if [onCreate enrollment type](/cmp/platform/cmp-account.md#on-create-enrollment) is enabled.

To add a Google Pay DPAN, include the wallet token in the `pan` field and provide the following fields in the card object:

* `wallet_type`: google\_pay
* `token_type`: dpan 

### **Google Pay Digital Wallet Fields**

CMP can store decrypted Google Pay DPAN cards securely. While stored like regular PANs, these cards are flagged to indicate their Google Pay source.

* `wallet_type`: google\_pay
* `token_type`: dpan

Merchants must use **lowercase** for these fields to pass validation checks.

**Important:** Google Pay wallet tokens are only accessible through `GET /cards/{id}`. Notifications will **not** include these cards, but the card object will clearly indicate DPAN using the `token_type` field.

#### **Create Card - Validation Rules for Google Pay**

* If creating a DPAN from Google Pay, the `wallet_type` field is **required**. Omitting it results in a **422 Unprocessable Entity** error.
* For physical PANs, both `wallet_type` and `token_type` are optional, but `token_type` always appears as `pan` in the response.
* You can also explicitly set `"token_type": "pan"` and `"wallet_type": "google_pay"` for a regular PAN. This allows you to indicate that the card is associated with Google Pay even if it isn’t a DPAN.
* Both fields must be lowercase. Variations such as `"Google Pay"` or `"google_Pay"` will fail validation. Uppercase `DPAN` will also fail and return **400 Bad Request**.

Sample request and response: **VGS Card Management API –** [**Create a Card**](/cmp/developer-resources/guides/testing/create-card.md).

#### **Retrieve Card (GET /cards/{id})**

Google Pay cards will return the `wallet_type` and `token_type` as originally sent (`wallet_type: google_pay`, `token_type: dpan`), confirming the card’s type and source.

Reference: **VGS Card Management API –** [**Get a Card**](/cmp/developer-resources/guides/testing/get-card.md).

#### **Onboarding Requirements**

No additional onboarding is required. Any customer already able to create cards in CMP can start storing Google Pay cards immediately.

#### Card Attributes

[Card Attributes](/cmp/products-and-services/card-attributes.md) are available for DPAN. 


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.