# Google Pay™

### General information 

Google Pay**™** is an easy, fast and secure way to pay for your purchases in online-stores and apps. When paying through the Google Pay service, the card number is not transmitted, instead, the generated virtual  account number (DPAN) is used. 

Before starting the integration, you need to familiarize yourself with two general  documents provided by Google itself for customers who want to use their  services: 

·       [Terms of Service](https://payments.google.com/payments/apis-secure/u/0/get_legal_document?ldo=0\&ldt=buyertos)

·       [Acceptable Use Policy](https://pay.google.com/about/policy/)

### Google Pay API's Developer Documentation Checklist

* [Google Pay Web developer documentation](https://developers.google.com/pay/api/web/overview)
* [Google Pay Web integration checklist](https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist)
* [Google Pay Web Brand Guidelines](https://developers.google.com/pay/api/web/guides/brand-guidelines)

### Integration with Google Pay**™** through the PSP payment page 

If you use the PSP payment page, then additional registration in Google services is not required, just leave a request to connect Google Pay**™** with your key account manager. 

When you use the PSP payment page, the device will automatically check the possibility of paying through the Google Pay service. The button “Pay with Google Pay” will be displayed, if the client's device or browser supports this feature.

<figure><img src="https://161584178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FREcAb9SNYOCAyn8iWZWq%2Fuploads%2FmbkEnUyVOSLDEGOwtGR8%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-04-09%20%D0%B2%2014.19.37.png?alt=media&#x26;token=1029c444-18bb-44a9-bfba-46e0f830adf8" alt="" width="375"><figcaption></figcaption></figure>

### Server-to-server integration (Third party processor)

With such an integration, you will need to register with the Google Pa&#x79;**™** service.&#x20;

If you are considering not transferring the token, and decrypting it yourself  using the tools of your services, then you will need to transfer the decrypted  data in the API request in the secure3d parameter.

{% content-ref url="additional-capabilities" %}
[additional-capabilities](https://docs.bizon.one/08.01/api-payment-gateway/additional-capabilities)
{% endcontent-ref %}

<figure><img src="https://161584178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FREcAb9SNYOCAyn8iWZWq%2Fuploads%2F9c1NlOGYqdzmPNrUBH6A%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-04-09%20%D0%B2%2014.23.08.png?alt=media&#x26;token=b602e03d-b3c0-46de-ac50-29553bc9173f" alt="" width="375"><figcaption></figcaption></figure>

### Integration with the merchant's website

For working with this type of integration, you need full integration in the Google Pay™ service. After going through a full integration cycle, the merchant needs to transfer only the received token from his website.&#x20;

**Integration process:**&#x20;

1\.     Get from the PSP Support team GatewayMerchantID;&#x20;

2\.     Register as a Developer (need to add a link) on the Google Pay™ portal;&#x20;

3\.     Carry out a full cycle of integration with Google Pay™ on your website;

4\.     Pass testing and get commercial access to Google Pay™;

5\.     Submit the necessary information for integration to the PSP for setup.

After receiving the token from Google Pay™ on their website, the merchant passes it to the PSP payment gateway via an API request. Then the token is decrypted and the result will be sent back.&#x20;

The operation of this method is described in the API documentation [(here)](https://docs.bizon.one/08.01/api-overview#id-1-authentication) in the section ‘Authorization with the transfer of an encrypted token (POST/orders/token\_pay)’.

<figure><img src="https://161584178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FREcAb9SNYOCAyn8iWZWq%2Fuploads%2Fmm6kUgvx9Q8aHNzwoH4O%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-04-09%20%D0%B2%2014.27.45.png?alt=media&#x26;token=caf7fe54-ab59-4ccf-a340-efe2b77a74fc" alt="" width="375"><figcaption></figcaption></figure>

### Payments with 3-D Secure for Google Pay™

Google Pa&#x79;**™** uses 2 types of cards:&#x20;

·       CRYPTOGRAM\_3DS - cards that are stored as tokens on a specific user's device. The token stores the virtual card number and expiration date, so such  cards do not participate in 3-D Secure verification.&#x20;

·       PAN\_ONLY - cards available on any user's devices. The token stores the data  of the physical card: number and expiration date, so 3-D Secure authentication  is required for this type of card.&#x20;

The procedure for 3-D Secure authentication does not differ from the standard and is described in API documentation ([link](https://docs.bizon.one/08.01/actions#example-3-d-secure)) in the section ‘Authorize’ (POST /orders/authorize).

### Google Pay request object

```
{
  "type": "CARD",
  "parameters": {
    "allowedAuthMethods": ["PAN_ONLY", "CRYPTOGRAM_3DS"],
    "allowedCardNetworks": ["VISA", "MASTERCARD"]
  },
  "tokenizationSpecification": {
    "type": "PAYMENT_GATEWAY",
    "parameters": {
      "gateway": "<your Google-registered gateway name>",
      "gatewayMerchantId": "<GatewayMerchantID provided by PSP>"
    }
  }
}
```

#### Supported authentication methods:

* `PAN_ONLY`
* `CRYPTOGRAM_3DS`

#### Supported card networks:

* `VISA`
* `MASTERCARD`

#### Where:

* `gateway` - is the Google Pay gateway identifier registered for the PSP;
* `gatewayMerchantId`  - is the merchant identifier issued by the PSP for Google Pay integration.

### Additional&#x20;

Brand guidelines – <https://developers.google.com/pay/api/android/guides/brand-guidelines>