Google Pay integration guide

Google PayGoogle Pay 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

Payment method gateway nameGoogle Pay
Supported transaction types
Supported integration methods
Supported processing currenciesFor googlePayAuthNet:
  • BRL
  • CAD
  • CLP
  • CZK
  • DKK
  • EUR
  • GBP
  • HKD
  • HNL
  • JPY
  • NOK
  • NZD
  • PLN
  • RUB
  • SEK
  • SGD
  • TWD
  • UAH
  • USD

For googlePayCyberSource:
  • AUD
  • CAD
  • USD
Webhook event types
  • TRANSACTION_SETTLED
  • TRANSACTION_REFUNDED

Configuration

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

In order to configure your account for use with Google Pay, you will need the following:

Required fields

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

FieldRequired?Description
data.amountYThe transaction amount.
data.currencyYThe three-character ISO currency code for the transaction.
data.customer.orderNumberYThe order number.
data.customer.firstNameYThe customer's first name, as it appears on the card.
data.customer.lastNameYThe customer's last name, as it appears on the card.
data.customer.emailYThe customer's email address.
customerRedirectUrlConditionalThe URL to which the customer will be redirected after completing their payment. The customer will be sent here upon successful or failed payment. This URL must use the HTTPS protocol. Required if you intend to use Nexio’s redirectUrls with your own buttons.
data.paymentMethodOptionalThe identifier for the alternative payment method. Use this parameter when you want to only return the Google Pay iframe button URL or the Google Pay redirect URL (rather than data for all payment methods associated with the account).

The value to use is googlePayAuthNet.

Transaction types and implementation methods

Regardless of the implementation workflow you implement, consumers will be redirected to Google Pay to complete their transactions.

Nexio supports the following transaction types for Google Pay:

Testing data

For testing data, see Google Pay Test Accounts.

Response handling

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

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.

  • Webhook notification: For Google Pay, these are the possible webhook event types:
    • TRANSACTION_AUTHORIZED
    • TRANSACTION_CAPTURED
    • TRANSACTION_REFUNDED
    • TRANSACTION_SETTLED

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

Status workflows

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

When isAuthOnly is false, successful sale transactions will have the following statuses:

  • pending (called "authorized" when querying transactions and in Nexio Dashboard)
  • settled

When isAuthOnly is true, successful sale transactions will have the following statuses:

  • authOnlyPending
  • authOnly

Capture

Successful capture transactions will have the following status:

  • settled

Refund

Successful refund transactions will have the following status:

  • settled

Next steps

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

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


Did this page help you?