Google Pay™ Documentation
Last updated
Last updated
Before working with the Google Pay™ API, it is essential to review the official documentation. It contains service usage requirements, integration guidelines, and a checklist for verifying the correctness of the connection.
For mobile app developers: Includes information on Google Pay™ API usage rules, Google Pay™ branding,, and an.
: Covers guidelines for applying the Google Pay™ API and its branded elements, , and an .
in your website or application, ensure the following:
Use a web page with the HTTPS protocol and a valid TLS certificate.
Configure the following parameters:
The gatewayMerchantId
is a unique store identifier assigned when connecting to the Alliance Bank payment gateway.
3DS verification for PAN_ONLY
is enabled by default.
If the integration is successful, a payment button will appear on your website or app. When clicked, the user will see a pop-up window displaying a list of their Google™ account-linked payment cards.
If your online store is already integrated with Alliance Bank, contact your account manager or send a request to ecom.support@bankalliance.ua
.
If integration with Alliance Bank has not yet been completed, also contact the specified email address ecom.support@bankalliance.ua
.
There are two methods for processing the received token:
Decryption on the merchant's side – The data is decrypted before being sent to Alliance Bank.
Decryption on the Alliance Bank side – The data is transmitted in its original form to Alliance Bank.
Example parameters returned by the Google Pay™ API can be found in the documentation.
For decrypting , Google™ recommends using the library.
Refer to the for details.
Review the to ensure all steps for the payment page integration are completed.
Ensure the Android app meets all requirements.
Submit a live access request for .
Submit a live access request for your .