Google Pay

Overview

Google Pay is a digital wallet developed by Google that allows users to store payment cards and make fast, secure transactions. It provides a seamless checkout experience, whether on Android devices or in supported browsers. With millions of users worldwide, Google Pay works with a wide range of banks and payment card providers across the globe.

Functionalities

Supported card schemes

• Visa
• Mastercard
• American Express
• Discover
• Diners Club International
• JCB

Liability Shift

If you want to learn all about liability shift with Google Pay, please review this guide - Shift liability to issuer.

Integration options

• Merchant hosted
• Netaxept hosted

Merchant Hosted Integration

As the name suggests, this method expects you to handle the direct integration of Google Pay into your checkout. Before proceeding, we strongly recommend familiarizing yourself with how Google Pay works. For more details, visit the official page: Google Pay official documentation

Activation in Netaxept

The activation can be achieved following the steps below:

1. Log in to the Admin portal.
2. Go to Options.
3. Select the Agreement tab.
4. In the Agreements dropdown search and select Google Pay.
5. Click on the Add button.
6. Select Currency*.
7. Click on the Add button.

*Note that if you have a multicurrency account, the activation process above must be repeated for each desired currency.

Google Pay API Integration Guidelines

When building the PaymentDataRequest that you'll be sending to Google make sure that:

• allowedPaymentMethods.parameters.allowedAuthMethods is set to both PAN_ONLY and CRYPTOGRAM_3DS. This ensures that all of the customer’s available cards appear as payment options, whether they are stored in the user's Google Account or as Android device tokens.
• allowedPaymentMethods.parameters.allowedCardNetworks is populated according to the card schemes supported for your account.
• allowedPaymentMethods.tokenizationSpecification.type is set to PAYMENT_GATEWAY.
• allowedPaymentMethods.tokenizationSpecification.parameters.gateway is set to epaymentnets. This tells Google that your integration will be processed via Netaxept.
• allowedPaymentMethods.tokenizationSpecification.parameters.gatewayMerchantId is filled with your Netaxept merchand Id.

Netaxept API Integration Guidelines

The following Google Pay-specific parameters must be included in the Netaxept's Register request:

• paymentData must be filled with the PaymentData response payload received from Google.
• paymentMethodActionList must be set to [{"PaymentMethod":"GooglePay"}].
• serviceType must be set to M.
• redirectUrl is mandatory only for the Web interface. Not applicable for Android integrations.

If possible, it is recommended to use the auto-sale or auto-auth option to skip the Process request and complete the authorization immediately after the Register step is finalized.

The snippets below show examples of Register request and response payloads.

https://test.epayment.nets.eu/Netaxept/Register.aspx?
merchantId=xxxxxx
&token=xxxxxxxxxx
&orderNumber=123456

<?xml version="1.0" encoding="utf-8"?>
<RegisterResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <TransactionId>1234567890</TransactionId>
    <URL>https://test.epayment.nets.eu/epay/default.aspx?merchantId=xxxxxx&amp;transactionId=1234567890</URL>

Netaxept Hosted Integration

For this type of integration, a dedicated Google Pay merchant account is not required.

Activation in Netaxept

The activation can be achieved following the steps below:

1. Log in to the Admin portal.
2. Go to Options.
3. Select the Agreement tab.
4. In the Agreements dropdown search and select Google Pay.
5. Click on the Add button.
6. Select Currency*.
7. Enter your Webshop hostname. That must be the hostname of the website where the checkout initiation occurs. Expected format 'www.webshop.com'.
8. Click on the Add button.

*Note that if you have a multicurrency account, the activation process above must be repeated for each desired currency.

Subscription-based payments

Netaxept supports Recurring and Unscheduled Credential-on-File (UCOF) payments for Google Pay. You can process subscriptions, memberships, and other recurring transactions seamlessly following the same flow as you do for standard card payments.

Recurring payments

Initial payment

You need to add the following parameters in the Register request for the first transaction:

• recurringType must be set to R.
• recurringFrequency specifies the desired frequency at which the customer will be charged.
• recurringExpiryDate is the date when the agreement for the payment expires.

After successful authorization, you must use the Query request on the specific transaction to retrieve the token from the panHash parameter, which will be returned in the response. You must store and use this payment token reference for all subsequent transactions in this payment flow.

Subsequent payments

Please make sure that all subsequent Register requests include the following data:

• panHash must be filled with the payment token generated in the initial transaction.
• serviceType must be set to A.
• recurringType must be set to R.

For more details on how to use the API parameters above, refer to the API reference.

Unscheduled Credential-on-File (UCOF) payments

Initial payment

You need to add the following parameters in the Register request for the first transaction:

• recurringType must be set to S.

After successful authorization, you must use the Query request on the specific transaction to retrieve the token from the panHash parameter, which will be returned in the response. You must store and use this payment token reference for all subsequent transactions in this payment flow.

Subsequent payments

Please make sure that all subsequent Register requests include the following data:

• panHash must be filled with the payment token generated in the initial transaction.
• serviceType must be set to A.
• recurringType must be set to M.
• recurringTransactionType must be set to 1.

For more details on how to use the API parameters above, refer to the API reference.

Testing

To properly test your Google Pay integration with Netaxept, you'll need to join the Google Pay test card suite group.

This action configures your Google Pay account to display a set of test cards in the Sandbox environment instead of real production-linked cards on the payment method selection screen. Please use the Netaxept test cards from that list.