Testing Google Pay Transaction Processing

The certification testing you need to perform depends upon the integration method you implement. This section provides information about the required tests for the eProtect integration method.

If you are experiencing an issue with your production Google Pay API setup, contact the gTech Ops Team for resolution here: https://developers.google.com/pay/api/faq. You can find additional information and help at the Google Developer’s site: https://payments.google.com/solutions/onboarding/.

Testing Google Pay using eProtect

In this integration method, your application submits information to the Google test environment, receives a low-value token, and then submits the low value token to Worldpay in a normal payment transaction.

The table below provides key data values you provide in the submitted transaction.

  1. Perform an implicit token registration by submitting a Sale or Authorization transaction using the data shown for the androidpay_1 (orderId) transaction in Table 1.

  2. Verify the response message includes the key Response values shown.

  3. Perform an explicit token registration by submitting a Register Token Request using the data shown for the androidpay_2 (orderId) transaction in Table 1.

  4. Verify the response message includes the key Response values shown.

TABLE 2-31  Google Pay using eProtect Test Data

orderId

Supplied Data Elements

Key Response Elements

Element

Value

Element

Value

androidpay_1

 

<orderSource>

<paypageRegistrationId>

androidpay

Value returned from Google

<response>

<message>

000

Approved

androidpay_2

<paypageRegistrationId>

Value returned from Google

<response>

<message>

 

 

801

Account number was successfullyregistered

Note: Under certain circumstances this test could return 820 - Account number was previously registered.

Example:  Google Pay Authorization Transaction

<cnpOnlineRequest version="12.0" xmlns="http://www.vantivcnp.com/schema" merchantId="100">

  <authentication>

    <user>User Name</user>

    <password>Password</password>

  </authentication>

  <authorization id="834262" reportGroup="ABC Division" customerId="038945">

    <orderId>androidpay_1</orderId>

    <amount>40000</amount>

    <orderSource>androidpay</orderSource>

    <paypage>

      <paypageRegistrationId>Low-Value Token</paypageRegistrationId>

<expDate>1250</expDate>

    </paypage>

  </authorization>

</cnpOnlineRequest>

Testing the Submission of the Decrypted Google Pay Payload in cnpAPI

To test the submission of an Google Pay transaction in cnpAPI when you decrypt the payload, you must include the information listed in the table below in an Authorization or Sale transaction. Assuming you submit valid XML with appropriate values, the test environment will return an approved response message.

TABLE 2-32  cnpAPI Elements for Merchant Decrypted Google Pay Payload

cnpAPI Element

Value

number

Use any valid (Mod-10 compliant) test card number. In production you submit the dpan.

expDate

Use any valid expiration date (i.e., a date in the future).

authenticationValue

Any Base-64 encoded value between 40 and 512 characters in length. This value simulates the cryptogram extracted from the encrypted payload.

orderSource

Set to androidpay