Overview

Google Pay enables your customers to complete their purchases quickly and easily in apps and on the web using the payment methods saved in their Google account or on their Android device.

Google Pay is an external token provider, a type of entity in the payment industry with its own flow that typically collects the customer payment method and transaction details. In some cases, Google Pay performs 3D-Secure authentication. The first time a customer uses a card in the Google Pay system, Google Pay performs 3DS authentication and stores the 3DS values from the successful authentication in a Google Pay token.

This guide describes how to implement Google Pay using Nuvei REST API 2.0, which currently supports non-3D-Secure Google Pay payments.

Supported Countries

• Afghanistan
• Aland Islands
• Albania
• Algeria
• Andorra
• Angola
• Anguilla
• Antarctica
• Antigua and Barbuda
• Argentina
• Armenia
• Aruba
• Australia
• Austria
• Azerbaijan
• Bahamas
• Bahrain
• Bangladesh
• Barbados
• Belarus
• Belgium
• Belize
• Benin
• Bermuda
• Bhutan
• Bolivia
• Bonaire
• Bosnia-Herzegovina
• Botswana
• Bouvet Island
• Brazil
• British Indian Ocean Territory
• Brunei
• Bulgaria
• Burkina Faso
• Cambodia
• Cameroon
• Canada
• Cape Verde
• Cayman Islands
• Central African Republic
• Chad
• Chile
• China
• Chinese Taipei
• Christmas Island
• Close
• Cocos (Keeling) Islands
• Colombia
• Comoros
• Congo
• Cook Islands
• Costa Rica
• Cote dIvoire
• Croatia
• Curacao
• Curaçao
• Cyprus
• Czech Republic
• Denmark
• Djibouti
• Dominica
• Dominican Republic
• Ecuador
• Egypt
• El Salvador
• Equatorial Guinea
• Eritrea
• Estonia
• Ethiopia
• Falkland Islands (Malvinas)
• Faroe Islands
• Fiji
• Finland
• France
• French Guiana
• French Polynesia
• French Southern Territories
• Gabon
• Gambia
• Georgia
• Germany
• Ghana
• Gibraltar
• Greece
• Greenland
• Grenada
• Guadeloupe
• Guam
• Guatemala
• Guernsey
• Guinea
• Guinea-Bissau
• Guyana
• Haiti
• Heard Island
• Honduras
• Hong Kong
• Hungary
• Iceland
• India
• Indonesia
• Iraq
• Ireland
• Isle of Man
• Israel
• Italy
• Jamaica
• Japan
• Jersey
• Jordan
• Kazakhstan
• Kenya
• Kiribati
• Kosovo
• Kuwait
• Kyrgyzstan
• Laos
• Latvia
• Lebanon
• Lesotho
• Liberia
• Libya
• Liechtenstein
• Lithuania
• Luxembourg
• Macau
• Macedonia
• Madagascar
• Malawi
• Malaysia
• Maldives
• Mali
• Malta
• Marshall Islands
• Martinique
• Mauritania
• Mauritius
• Mayotte
• Mexico
• Micronesia
• Moldova
• Monaco
• Mongolia
• Montenegro
• Montserrat
• Morocco
• Mozambique
• Myanmar
• Namibia
• Nauru
• Nepal
• Netherlands
• Netherlands Antilles
• New Caledonia
• New Zealand
• Nicaragua
• Niger
• Nigeria
• Niue
• Norfolk Island
• Northern Mariana Islands
• Norway
• Oman
• Pakistan
• Palau
• Palestinian Territory
• Panama
• Papua New Guinea
• Paraguay
• Peru
• Philippines
• Pitcairn
• Poland
• Portugal
• Puerto Rico
• Qatar
• Reunion
• Romania
• Russia
• Rwanda
• Saint Barthélemy
• Saint Helena
• Saint Kitts and Nevis
• Saint Lucia
• Saint Martin
• Saint Pierre and Miquelon
• Saint Thomas
• Saint Vincent
• Saint Vincent and Grenadines
• Samoa
• San Marino
• Sao Tome and Principe
• Saudi Arabia
• Senegal
• Serbia
• Seychelles
• Sierra Leone
• Singapore
• Slovakia
• Slovenia
• Solomon Islands
• Somalia
• South Africa
• South Georgia, South Sandwich Islands
• South Korea
• Spain
• Sri Lanka
• Suriname
• Svalbard and Jan Mayen Islands
• Swaziland
• Sweden
• Switzerland
• Taiwan
• Tajikistan
• Tanzania, United Republic of
• Thailand
• Timor-Leste
• Togo
• Tokelau
• Tonga
• Trinidad and Tobago
• Tunisia
• Turkey
• Turkmenistan
• Turks and Caicos Islands
• Tuvalu
• Uganda
• Ukraine
• United Arab Emirates
• United Kingdom
• Uruguay
• Uzbekistan
• Vanuatu
• Vatican City
• Venezuela
• Vietnam
• Virgin Islands
• Wallis and Futuna
• Western Sahara
• Yemen
• Zambia
• Zimbabwe

Supported Currencies

Google Pay supports all currencies supported by Nuvei.

Availability

Offering your customers Google Pay as a payment option depends on the following factors:

1. Card Types Supported
   The following card types are supported: VISA, Mastercard, Discover/Diners, AMEX and JCB.
2. Merchant Location
   When it comes to being able to accept Google Pay transactions, the location of your business matters. Merchants in the following regions are eligible:
   • United States
   • Europe
   • Asia Pacific
   • Australia
3. Location of where the Customer’s Card Details are Stored
   Customer compatibility depends on where the customer’s card details are stored:
   • Cards stored on a Google Account:
     • Available worldwide
   • Cards stored on an Android Device:
     Available to customers in the following countries:
     • United States
     • United Kingdom
     • Singapore
     • Australia
     • Hong Kong
     • Poland
     • New Zealand
     • Ireland
     • Belgium
     • Russia
     • Japan
     • Canada
     • Taiwan
     • Spain
     • Ukraine
     • Brazil
     • Czech Republic
     • Slovakia
     • France
     • South Korea

Prerequisites and Notes

• This guide assumes you have completed all account setup prerequisites, and are ready to integrate Google Pay into your payment flow.
• Use these gateway credentials in requests:
  • For the test (sandbox) environment: gatewayMerchantId: “googletest“
  • For the production environment: gatewayMerchantId: “nuveidigital“
• The Google Pay Web environment must be set up according to the Google Pay guidelines:
  • Google Pay Web Developer Documentation
  • Google Pay Brand Promoting Guidelines
    For your domain to be verified with Google, the merchant must send Nuvei’s Integration Team screenshots (like the one shown below) of your payment flow along with your domain URL:
    
  • Google Pay Test Card Suite
  • Google Pay Web Integration Checklist
    
    Only some information in the pages listed are relevant to Nuvei integration. Other information is relevant only for merchants performing a direct Google Pay integration, without Nuvei.

• The Google account used for testing should be linked to a relevant test card:
  • Google Pay provides test cards, see Google Pay Test Card Suite for details.
  • Alternatively, you can use one of the test cards listed in for REST 2.0.
    Test credentials and testing scenarios can be provided by Nuvei if necessary.
    You can contact Nuvei Support for any assistance.

Implementation

Follow these steps to implement Google Pay using Nuvei REST API 2.0:

1. Set up the Google Pay UI.
2. Integrate Google Pay for payments – Nuvei decrypts the Google Pay token.

Upon completion, customers are able to make payments using Google Pay.

Set Up the Google Pay UI

1. Authentication

For Nuvei to authenticate REST API 2.0 requests, the merchant must include its API key in the header. Press here for details.

2. The Google Pay UI Button

1. Create the Google Pay UI button according to the instructions in the Google Pay for Web Payments Brand Guidelines Guide.
2. On your payment page, define the tokenizationSpecification constant as shown below.
   (When the customer presses the Google Pay button, this parameter identifies your gateway and your site’s gateway merchant identifier.)

   Example tokenizationSpecification Request

   const tokenizationSpecification = {
     type: "PAYMENT_GATEWAY",
     parameters: {
       "gateway": "nuveidigital",
       "gatewayMerchantId": "googletest", //'googletest' for test or 'nuveidigital' for production
     }
   };

3. Google Pay Payment Flow

1. The customer triggers the Google Pay payment flow by pressing the Google Pay button.
   At this point, customers not logged in to Google are asked to log in.
2. Google Pay displays all the cards associated with the customer’s Google account, or asks the customer to add new card details.
3. The customer selects a payment method and Google Pay sends the merchant an encrypted Google Pay token.

Payments – Nuvei Decrypts Token

The Google Pay token contains Google Pay authentication values from a successful Google Pay authentication. The merchant sends the encrypted Google Pay token as-is in a non-3DS /payments request. Nuvei decrypts the token and uses the relevant data extracted from it.

Send a non-3DS POST /payments request with its mandatory parameters and include:

• paymentOption block with:
  • store: “none“
  • eWallet block with:
    • provider: “GooglePay“
    • token: “<encrypted token merchant received from Google Pay>“

Example Google Pay /payments Request

{
  "processingEntityId": "<your processingEntityid>",
  "amount": 10.5,
  "currency": "USD",
  "paymentOption": {
    "store": "none",
    "eWallet": {
      "provider": "GooglePay",
      "token": "<encrypted token merchant received from Google Pay>"
    }
  },
  "deviceDetails": {
    "ipAddress": "<customer's IP address>"
  },
  "buyerDetails": {
    "email": "[email protected]",
    "billingAddress": {
      "countryCode": "US"
    }
  }
}

Example /payments Response for Non-3DS

{
  "paymentId": "494321",
  "transactionId": "1110000000009891682",
  "externalTransactionId": "211011237407",
  "amount": 10.5,
  "currency": "USD",
  "transactionType": "Sale",
  "result": {
    "status": "approved"
  },
  "authCode": "465190",
  "partialApproval": {
    "requestedAmount": 10.5,
    "requestedCurrency": "USD"
  },
  "paymentOption": {
    "eWallet": {
      "provider": "GooglePay",
      "eciIndicator": "07",
      "expirationMonth": "12",
      "expirationYear": "2028"
    }
  }
}