Google Pay
GooglePay ™
Google Pay allows customers to make payments in your app or website using any credit or debit card saved to their Google Account, including those from Google Play, YouTube, Chrome, or an Android device. Use the Google Pay API to request any credit or debit card stored in your customer’s Google account.
Direct GooglePay Integration
In case a direct integration with GooglePay is required, and not through Components, the following parameters should be used when working with the GooglePay integration:
gateway:
gatewayMerchantID: mrchnt_{merchant_id}
Your merchant ID can be found on the dashboard on the Developers tab.
For merchants who are PCI Level 1 certified and integrating directly with GooglePay, network tokens can be decrypted by the merchant before sending to for processing.
For merchants who are not certified or do not want to detokenize GooglePay payment data, the encrypted blob can be sent to for both decryption and processing. Merchants are not exposed to PCI Scope for obtaining the GooglePay token.
What authMethod should I use for GooglePay?
While supports both auth methods PAN_ONLY and CRYPTOGRAM_3DS strongly encourages the sole use of authMethod CRYPTOGRAM_3DS to mitigate fraud.
In a Googlepay workflow the payment data are directly sent to the server with initial payment request. That means that the transaction can be processed straight away.
Your request has to include the following information:
- - Authentication Credentials
- - Type and amount of transactions
- - Payment information like pan_only/cryptogram_3ds/encrypted
For our Googlepay Workflow REST API you can use the following types of initial payments:
Perform 3DS on a PAN_ONLY GooglePay token
In case of PAN Only, based on risk parameters 3D secure flow may trigger, please refer 3D workflow for more details
Preauthorization (PA):
Request has to be sent to our REST endpoint i.e. /transactionServices/REST/v1/payments using POST method.
The paymentType for this request will be PA.
You can also place a capture transaction request against a successful PA using our Backoffice APIs.
Debit (DB):
Debit request has to be sent to our REST endpoint i.e. /transactionServices/REST/v1/payments using POST method.
With a DB request a successfully authorized transaction gets captured immediately.
The paymentType for this request will be DB.
In our API Specifications you can find a full list of parameters that can be sent in the initial request.
Sample Request
Sample Response
Hashing Rule
is supporting MD5 Cryptographic Hash for the authenticity of payment request send to the server.
Below is the description of fields use for generating checksum.
- memberId <Merchant ID as shared by >
- secureKey <Secure Key that can be generated through 's dashboard>
- merchantTransactionId <Unique transaction ID prived by merchant>
- amount <Amount of transaction>
How to generate Checksum ?
Checksum has to be calculated with following combination and need to be send along with the authentication parameters in each server-to-server request:
<memberId>|<secureKey>|<merchantTransactionId>|<amount>
Standard Notification/ Callback
Checksum has to be calculated with following combination.
<paymentId>|<merchantTransactionId>|<amount>|<short status of transaction>|<secret key>
Example :
77251|011E1D8A5C034|156.00|N|<merchant secret key>
Sample Code
Compatibility
Card brands: Visa, MasterCard, American Express, Discover
Browsers: Google Chrome, Mozilla Firefox, Apple Safari, Microsoft Edge, Opera, or UCWeb UC
Terms of Service
By integrating Google Pay, you agree to Google’s terms of service.
Web Merchants:
Google Pay Web Developer Documentation
Google Pay Web Integration Checklist
Google Pay Web Brand Guidelines
Android Merchants:
Google Pay Android Developer Documentation