Google Pay™

Google Pay™

The Google Pay API enables fast, simple checkout on the website, and gives the merchant convenient access to hundreds of millions of cards saved to Google Accounts worldwide.

General Information

Qenta uses the credit card data from the Google Pay checkout to initate a transaction with the merchant’s credit card acquirer activated on the customerID. This also means that the payout happens via the appropriately activated/used credit card acquirer. Some credit card acquirer cannot handle Google Pay. Please get in touch with our sales department for further information.

Example: If AMEX is not activated on the CustomerID, an AMEX credit card is also not selectable during Google Pay checkout

Supported Acquirer

The chosen credit card acquirer must support Google Pay.

Acquirers supporting Google Pay:

  • Card Complete

  • SIX AT (Paylife)

  • Hobex

  • American Express

Registration

Qenta handles the entire payment process in the background, a seperate registration for Google Pay is not required!

Parameters

Google Pay API payment method can be initialized if the merchant sends GOOGLEPAY for parameter paymentType.

allowedCardNetworks

MERCHANTS can set optionally the allowed creditcard brands for googlepay with the parameter allowedCardNetworks.

Possible value(s) of allowedCardNetworks Description

AMEX

American Express

DISCOVER

Discover

DINERS

Diners Club

MASTERCARD

Mastercard

VISA

Visa

By default all possible brands (based on the merchant’s configuration) will be activated.

shippingAddressRequired

MERCHANTS can optionally force the customer to select/define the shipping address within googlepay with the parameter shippingAddressRequired.

Merchants will get the responseGooglepay parameters for in the response.

phoneNumberRequired

MERCHANTS can optionally force the customer to select/define the phonenumber within googlepay with the parameter phoneNumberRequired.

Merchants will get the googlepayShippingPhone parameter for in the response.

allowedCountryCodes

MERCHANTS can optionally define the allowed countries for googlepay with the parameter allowedCountryCodes.

If parameter is not set, all countries are allowed.

paymentToken

If QMORE Checkout Seamless is used, MERCHANTS must send the parameter paymentToken during Frontend-Initiation.

3D Secure/Recurring

Caused by the circumstance that GooglePay is basically a credit card transaction, please consider the section 3D Secure 2/Recurring for initiations as well for recur payments.

General Information about the Integration

QENTA integrated GooglePay for web merchants based on the following documentations:

There is no need to follow these integration guidelines as they are already covered within the QENTA products.

Information about the authorization methods can be found here.

QENTA offers GooglePay in the hosted payment solutions, which allows the merchant to communicate directly with the QENTA API.

GooglePay encrypted payment information (cryptogram) is handled directly by QENTA.

In general, gateway credentials are mandatory for the GooglePay integration. The gateway and gatewayMerchantId are set by QENTA and are not needed to be set by the merchant.

Order Flow Diagram

Image

To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.

All possible states of transaction for all specific acquirers can be found here.