Please ensure that the following checklist has been fully completed before submission.

Branding

Requirement

Android

Web

Hosted

☐

Make sure that the first and most prominent mention of Google Pay™ includes the trademark symbol ™.

needed

needed

needed

☐

If you provide Google Pay™ as a payment method to your customers, you must use the official Google Pay logo and button assets in compliance with Google Pay Android brand guidelines and Google Pay web brand guidelines, without modifications to the Google Pay™ asset colors, proportions, or appearance.

needed

needed

needed

Accepted Use

Requirement

Android

Web

Hosted

☐

Adhere to Google policies: All merchants are required to follow the Google Pay and Wallet API's Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service.

needed

needed

needed

Implementation Paths

Requirement

Android

Web

Hosted

☐

If you provide Google Pay™ to Web or Android applications, you must follow our process described at Pay with Google Pay™.

needed

needed

n/a

☐

If you provide Google Pay™ to Android applications, you must follow the official Google documentation as Google Pay Android developer documentation, Google Pay Android integration checklist and Google Pay Android brand guidelines.

needed

n/a

n/a

☐

If you provide Google Pay™ to Web applications, you must follow the Google Pay Web developer documentation, Google Pay Web integration checklist and Google Pay Web Brand Guidelines.

n/a

needed

n/a

☐

If you provide Google Pay™ by using Smart Checkout (our hosted checkout and payment page), you must call the secuconnect API from the server back-end. You must not display the hosted page inside an iframe.

n/a

n/a

needed

☐

Make sure the you generate proper IsReadyToPayRequest and PaymentDataRequest properties needed for your integration. The source for each parameter value is described at Pay with Google Pay™. This includes the you are required to complete the registration with the Google Pay & Wallet Console to provision a Google MerchantID value.

needed

needed

n/a

Implementation Details

Requirement

Android

Web

Hosted

☐

Depending on the merchant's contract, we provide 3DS on Google Pay PAN_ONLY transactions. For both, Google Pay PAN_ONLY transactions, and for any non-Google Pay card transactions, you must implement the needed process variant for 3-D Secure (3DS). This process is described in detail at Pay with Google Pay™, sect. Authorize the Payment.

needed

needed

n/a

☐

If you provide Google Pay™ to Web or Android applications, you must set for both gateway and gatewayMerchantID, the values received from us.

As a supported payment service provider with the Google Pay API, our integration lets you as a merchant to use Google Pay API's gateway integration type, where we handle all of the decryption on your behalf.

When you integrate with the Google Pay API as a merchant, ensure to set the following values in the TokenizationSpecification object:

  • gateway: set to "secupay"
  • gatewayMerchantID: set this value to the secupay contract ID you receive during onboarding ("GCR_...")

Here's an API configuration example:

"tokenizationSpecification": {
"type": "PAYMENT_GATEWAY",
"parameters": {
"gateway": "secupay",
"gatewayMerchantId": "<Contract ID GCR_... assigned by secupay>"
}
}

needed

needed

n/a

☐

Depending on the merchant's contract, our integration with Google Pay supports two types of card credentials:

  1. PAN_ONLY: physical card details stored in Google Pay™
  2. CRYPTOGRAM_3DS: tokenized virtual card stored on device

If you provide Google Pay™ to Web or Android applications, you must not set values for allowedAuthMethods that you have not been advised from us. Details are described in detail at Pay with Google Pay™, sect. Google Pay™ Button Integration and (if applicable) sect. Obtaining the Button Parameters Dynamically.

If your integration includes PAN_ONLY, the application must implement the process variant for 3-D Secure (3DS). It is described in detail at Pay with Google Pay™, sect. Authorize the Payment.

If your integration includes only CRYPTOGRAM_3DS, the application is not required for 3-D Secure. It cannot appear since the authentication is performed by Google Pay™.

needed

needed

n/a

☐

Depending on the merchant's contract, we support VISA, Mastercard, and American Express card networks with the Google Pay API. You can shall these values in the allowedCardNetworks property and find the appropriate values in Google Pay's web developer documentation and Google Pay's Android developer documentation. Details are described in detail at Pay with Google Pay™, sect. Google Pay™ Button Integration and (if applicable) sect. Obtaining the Button Parameters Dynamically.

needed

needed

n/a

☐

If you receive it from Google Pay, you are required to pass the full billing address, and if known the phone number to our API. The process is described in detail at Pay with Google Pay™, sect. Authorize the Payment.

The need to require the address and phone number from Google Pay will depend on your needs, the exact implementation (e. g. whether express checkout) and obligations communicated by us.

needed

needed

n/a

☐

Make sure the Google encrypted payment data and transaction data are sent to our servers through the API calls described at Pay with Google Pay™, sect. Authorize the Payment.

needed

needed

n/a

See Also