Learn how to accept Google Pay through Safepay's hosted checkout.

Google Pay™

Overview

Safepay supports Google Pay™ on its hosted checkout pages, enabling customers to complete payments using any credit or debit card saved to their Google Account. Merchants using Safepay’s hosted gateway do not need to make any integration changes — Google Pay is automatically enabled on the hosted page for eligible customers.

This document outlines Safepay’s current integration in Phase 1, which includes only the hosted checkout experience. API-based merchant integrations are planned for future phases.

Integration Type

Safepay has implemented a direct integration with Google Pay using the Google Pay JavaScript API. The Google Pay button is rendered on Safepay’s hosted checkout page. When a customer clicks the button, the payment sheet is presented, and a secure token is received, decrypted, and processed via Safepay.

In Phase 1:

• Merchants do not require any integration changes
• Safepay handles all token decryption and processing

Gateway Parameters (For Future Direct API Integration)

For PCI DSS-certified merchants integrating directly with Google Pay in the future, the following parameters should be used:

{
  "gateway": "safepay",
  "gatewayMerchantId": "<your_merchant_id>"
}

Token Handling Options

Safepay supports two secure methods for handling Google Pay payment tokens:

Merchant-Managed Decryption (Advanced, PCI-certified only)

• The merchant decrypts the Google Pay token using a tool such as Tink.
• Safepay receives the raw Primary Account Number (PAN) or network token for further processing.
• This approach is recommended only for PCI DSS Level 1 merchants.

Safepay-Managed Decryption (Default and Recommended)

• The merchant forwards the encrypted Google Pay token directly to Safepay.
• Safepay decrypts the token on behalf of the merchant and securely processes the transaction.
• This is the default method and requires no additional certification or cryptographic handling by the merchant.

Recommended Authentication Method

Safepay supports:

• PAN_ONLY
• CRYPTOGRAM_3DS

Safepay recommends using CRYPTOGRAM_3DS to reduce fraud and increase issuer authorization rates.

Billing Address Handling

• It is recommended to set billingAddressRequired: true in the Google Pay request object.
• The returned billing address should be used to validate against the customer's existing profile.
• Note: Shipping address cannot substitute billing address in any scenario.

3D Secure with PAN_ONLY

Merchants receiving a PAN_ONLY token can:

• Create a payment_method from the tokenized data
• Use it to initiate a 3DS authentication session via Safepay’s 3DS API

Compatibility

Terms of Service

By integrating Google Pay, you agree to comply with Google’s Terms of Service.

Resources

Web Merchants:

• Google Pay Web Developer Documentation
• Integration Checklist
• Brand Guidelines

Android Merchants:

• Google Pay Android Developer Documentation
• Integration Checklist
• Brand Guidelines

Future Roadmap

Safepay will introduce full API-based Google Pay support for merchants in a future release. This will include:

• Google Pay integration guides for direct merchant integration
• Token decryption tools
• Sample merchant checkout implementations

This document will be updated accordingly at that time.