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: paycom
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 Pay.com for processing.
For merchants who are not certified or do not want to detokenize GooglePay payment data, the encrypted blob can be sent to Pay.com 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 Pay.com supports both auth methods PAN_ONLY and CRYPTOGRAM_3DS, Pay.com strongly encourages the sole use of authMethod CRYPTOGRAM_3DS to mitigate fraud.
Example API Objects
To create a charge with a GooglePay encrypted object:
POST /api/v1/charges
{
"source_data": {
"type": "googlepay",
"googlepay": {
"signature": "MEQCIGQ...",
"intermediateSigningKey": {
"signedKey": "",
"signatures": ["MEYCIQ..."]
},
"protocolVersion": "ECv2",
"signedMessage": "{\"encryptedMessage\"..."
}
},
"amount": 10000,
"currency": "usd"
}
To create a charge with a network token decrypted from GooglePay object:
POST /api/v1/charges
{
"source_data": {
"type": "network_token",
"network_token": {
"token": "4242424242424242",
"token_type": "googlepay",
"expiry_month": "10",
"expiry_year": "2025",
"three_ds": {
"eci": "06",
"cryptogram": "AgAAAAAAAIR8CQrXcIhbQAAAAAA"
}
}
},
"amount": 10000,
"currency": "usd"
}
Billing Address
Although not required for processing, it is recommended to send billing address for higher success rates.
It is recommended to set BillingAddressRequired to true in your Google Pay Request Object within the Card Parameters. It is recommended to always require a billing address through Google Pay, and compare it with your address on file if exists.
*Note that shipping address cannot be substituted for a billing address.
Address Response Info received in your Address Response Object from GooglePay should be used to populate the corresponding billing fields fields in your request to Pay.com.
Perform 3DS on a PAN_ONLY GooglePay token
In case wanting to perform 3DS on a PAN_ONLY token data, the payment_method that has been created from the GooglePay token, can be used to create an Authentication Session and perform 3DS on the card.
Compatibility
Card brands: Visa, MasterCard, American Express, Discover
Supported methods: Hold, Charge
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
Google Pay Android Integration Checklist
Google Pay Android Brand Guidelines