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.
|Google Pay is currently only available on the Qenta Checkout Page!|
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
Qenta handles the entire payment process in the background, a seperate registration for Google Pay is not required!
Google Pay API payment method can be initialized if the merchant sends
GOOGLEPAY for parameter
MERCHANTS can set optionally the allowed creditcard brands for google pay with the parameter allowedCardNetworks.
|Possible value(s) of
By default all possible brands (based on the merchant’s configuration) will be activated.
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.
QENTA integrated 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 in the hosted payment solutions, which allows the merchant to communicate directly with the QENTA API.
encrypted payment information (cryptogram) is handled directly by QENTA.
In general, gateway credentials are mandatory for the integration.
gatewayMerchantId are set by QENTA and are not needed to be set by the merchant.