Google Pay ™ Processing

Google Pay™

Google Pay™ is Google Inc.'s digital wallet platform and online payment system. Merchants can integrate the payment service into their websites and mobile applications. Android users may add payment cards to Google Pay™ and use them to make purchases in stores, applications, and online.

Google Pay™ is compatible with Android smartphones, tablets, and wearables. Google Pay™ at retail outlets transmits card information via Near Field Communication (NFC), allowing funds transmission to the retailer. By allowing users to upload card data to the Google Pay™ wallet, it replaces credit or debit card chip and PIN or magnetic stripe transactions at point-of-sale terminals. Using a near field communication (NFC) antenna, host-based card emulation (HCE), and Android's security, the service enables Android devices to communicate wirelessly with point of sale systems.

Where applicable, Google Pay™ makes use of physical authentication methods such as fingerprint ID. Google Pay™ is activated using a passcode on devices without fingerprint ID. When a user makes a payment to a business, Google Pay™ does not provide the retailer the user's credit or debit card number. Rather than that, it creates a virtual account number that corresponds to the user's account details. This service protects the customer's payment information by transmitting a one-time encryption token rather than the card or user information.

Users can add payment cards to the service by using the camera on their device or manually entering their information. To pay at a point of sale, a user must have an authenticated device nearby.

Customer can also make a payment with Google Pay™ in apps or on their websites that offer Google Pay ™ as a payment method.

As a merchant integrating with Google Pay™, you must adhere to the Google Pay APIs Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service.

Paymentvision's Google Pay integration supports the major card networks ONLY within the United States: Visa, Mastercard, Discover, Amex.

Configuration Setup

Web Setup

Before using Google Pay from web, a user must add a payment method to the wallet or enter the card information manually. The payment method is stored in the wallet for future use. See Web Integration for details. And this currently the only submitted setup in which Paymentvision is offering right now. We are working on an "Android Setup" in the never future.

Payment Service Support for Google Pay™ Integration

Paymentvision's API that can be used to integrate with Google Pay™ both for in-app purchases on mobile devices and purchases made on store websites.

Google Pay™ Integration Flow

This is the flow to complete a Google Pay™ transaction for the single request integration using Paymentvision payment service APIs.

  1. At checkout, when a Google Pay™ user taps the Google Pay™ button, a payment sheet displays the payment methods that have been saved to the Google Account and optional fields such as a shipping address.
  2. The user can select a payment method in the wallet, or add new payment information, and provide shipping address if required
  3. The client application connects to the Google server with gateway ID paymentvision and using their merchantPrimaryCode as the gateway merchant ID, and receives encrypted payment token data in JSON format.
  4. The client application creates a CreditCardAuth request including the authorization amount, GooglePaySigningKey (key signature, value, and expiration), EphemeralPublicKey, Tag, Version, encryption signature, and encrypted token.
  5. The client application sends the CreditCardAuth request to Paymentvision's API.
  6. Paymentvision backend systems will use its private key along with the ephemeral public key passed in the API call to decrypt the payment data.
  7. The Payment Service processes the request as a regular Card Not Present transaction and returns a success or failure response.
  8. The client application receives the success or failure response and prompts the user accordingly.

The billing address are not mandatory by default, however we could make certain fields mandatory based on your use case.

If would like to enable 3DS for PAN_ONLY credentials returned via the Google Pay API for your merchant account, please send a request to support@paymentvision.com for availability and our support team will enable it for the merchant account.

Google Pay™ PaymentMethodToken Payload Example

Production
Demo
Copy
JSON
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard