Google Pay is a payment provider allowing customers to pay using payment methods saved to their Google account. This section is intended to help you implement Google Pay based on your preferred integration workflow.

Services and compatibility

Configuration

In order to use Google Pay with your merchant account, you must first work with Integrations to add it to your account.

Prerequisites

In order to have Integrations configure your account for use with Google Pay, you need to provide Integrations with the following information:

• A Google Pay Console account
• A Google Pay Console Business Profile
• A Google Pay Console Merchant ID
• An Authorize.Net or Cybersource account (if needed, Integrations Support can assist you with creating the Cybersource account)

Configuration tasks

The following steps provide guidance on how to get ready for adding Google Pay to your account.

1. Go to the Google Pay & Wallet Console.
2. If you do not yet have a Google Pay Console account, complete the requested information and click Continue.
3. After logging into the console, make note of the Merchant ID in the upper right corner of the page.
4. Click Get Started in the Business Profile section of the page to enable the merchant profile.
5. Set up an Authorize.net or Cybersource account (if needed, Integrations Support can assist you with creating the Cybersource account).
   1. For Authorize.net, make note of your login ID and transactionKey.
   2. For Cybersource, make note of your Cybersource merchant ID, merchant key ID, and merchant secret.
6. Contact Integrations Support to provide the required information for the gateway used with Google Pay.

Required fields

The following table shows the required and optional fields for Google Pay transactions in the Create APM one-time-use token request.

Example requests

The following are example one-time-use token requests for Google Pay.

curl -X POST https://api.nexiopaysandbox.com/apm/v3/token \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "data": {
    "amount": 4.00,
    "currency": "USD",
    "paymentMethod": "googlePayAuthNet",
    "customer": {
      "orderNumber": "12345678",
      "firstName": "John",
      "lastName": "Doe",
      "email": "[email protected]",
      "billToAddressOne": "123 Test St",
      "billToCity": "Testerville",
      "billToState": "UT",
      "billToPostal": "12345",
      "billToCountry": "US"
    }
  }
}'

curl -X POST https://api.nexiopaysandbox.com/apm/v3/token \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "data": {
    "amount": 4.00,
    "currency": "USD",
    "paymentMethod": "googlePayCyberSource",
    "customer": {
      "orderNumber": "12345678",
      "firstName": "John",
      "lastName": "Doe",
      "email": "[email protected]",
      "billToAddressOne": "123 Test St",
      "billToCity": "Testerville",
      "billToState": "UT",
      "billToPostal": "12345",
      "billToCountry": "US"
    }
  }
}'

{
  "expiration": "2018-09-18T15:43:05.664Z",
  "token": "830d36f6-a5e3-4455-9600-3a55b63e2fc2",
  "asyncTraceId": "830d36f6-a5e3-4455-9600-3a55b63e2fc2",
  "expressIFrameUrl": "https://www.api.nexiopaysandbox.com/v3?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2",
  "redirectUrls": [
    {
      "paymentMethod": "payPal",
      "url": "https://www.api.nexiopaysandbox.com/v3/popup?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=payPal"
    },
    {
      "paymentMethod": "googlePayAuthNet",
      "url": "https://www.api.nexiopaysandbox.com/v3/popup?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=googlePayAuthNet"
    },
    {
      "paymentMethod": "googlePayCyberSource",
      "url": "https://www.api.nexiopaysandbox.com/v3/popup?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=googlePayCyberSource"
    }
  ],
  "buttonIFrameUrls": [
    {
      "paymentMethod": "payPal",
      "url": "https://api.nexiopaysandbox.com/apm/v3?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=payPal"
    },
    {
      "paymentMethod": "googlePayAuthNet",
      "url": "https://api.nexiopaysandbox.com/apm/v3?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=googlePayAuthNet"
    },
    {
      "paymentMethod": "googlePayCyberSource",
      "url": "https://api.nexiopaysandbox.com/apm/v3?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=googlePayCyberSource"
    }
  ]
}

For the multi iframe integration method: You use the expressIFrameUrl value in the steps for the transaction.

For the individual iframe option: You use the buttonIFrameUrls.url of the Google Pay APM for the transaction.

For the custom redirect option: You use the redirectUrls.url of the Google Pay APM for the transaction.

Transaction types and integration methods

Regardless of the integration method workflow you implement, consumers are redirected to Google Pay to complete their transactions.

Nexio supports the following transaction types for Google Pay:

• Auth Only
• Sale
  • In an iframe that displays all payment methods available to the customer (based on the customer’s location and the merchant’s configured payment methods)
  • In an individual iframe
    
    
  • Using your own copy of the Google Pay logo
• Void
• Capture
• Refund

Testing data

For testing data, see the appropriate page for your target platform:

• For Android: Test card suite
• For Web: Test card suite

Response handling

In the one-time-use token request, Google Pay gets returned in the paymentMethod parameter as googlePayAuthNet or googlePayCyberSource.

Nexio responds with transaction results in one of the following ways, depending on your integration workflow:

• Event messages: This applies to integrations that do not pass a customerRedirectUrl in the request.
• Response fields in the URL: This applies to integrations that do provide a customerRedirectUrl in the request.

In addition to one of the above, if your merchant account is configured to receive webhooks, Nexio provides responses to the webhook URLs that have been registered. For further explanation of the webhook event types, see the webhook Event types table.

For Google Pay, these are the possible webhook event types:

• TRANSACTION_AUTHORIZED
• TRANSACTION_CAPTURED
• TRANSACTION_REFUNDED
• TRANSACTION_SETTLED
• TRANSACTION_VOIDED

For information about how to run each of the integration workflows, see Transaction types and integration methods above.

Status workflows

The status of a successful transaction with Google Pay varies, depending on the options you choose.

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the table).

Next steps

Now, you are ready to get started with running transactions:

• Run a sale transaction

If you have any additional questions or feedback, see Contact us.