Introduction

You can use the
Cybersource
 platform to process and manage Google Pay transactions.

Google Pay Overview

Google Pay is a simple, secure in-app mobile and Web payment solution. You can choose
Cybersource
 to process Google Pay transactions through all e-commerce channels.
You can simplify your payment processing by allowing
Cybersource
 to decrypt the payment data for you during processing.
This method integrates simply and enables you to process transactions without seeing the payment network token and transaction data.
  1. Using the Google API, request the customer’s encrypted payment data.
  2. Using the
    Cybersource
     API, construct and submit the authorization request, and include the encrypted payment data from the Google Pay callback.
  3. Cybersource
     decrypts the encrypted payment data to create the payment network token and processes the authorization request.

Google Pay Overview

Google Pay is a simple, secure in-app mobile and Web payment solution. You can choose
Cybersource
 to process Google Pay transactions through all e-commerce channels.
You can simplify your payment processing by allowing
Cybersource
 to decrypt the payment data for you during processing.
This method integrates simply and enables you to process transactions without seeing the payment network token and transaction data.
  1. Using the Google API, request the customer’s encrypted payment data.
  2. Using the
    Cybersource
     API, construct and submit the authorization request, and include the encrypted payment data from the Google Pay call back.
  3. Cybersource
     decrypts the encrypted payment data to create the payment network token and processes the authorization request.
Introduction

Payment Network Tokens

Authorizations with payment network tokens enable you to securely request a payment transaction with a payment network token instead of a customer’s primary account number (PAN).
The payment network token is included in the customer’s encrypted payment data, which is returned by the payment processor.
For information about authorizations with payment network tokens, see the Authorizations with Payment Network Tokens Guide.
Introduction

Prerequisite Requirements

Before using Google Pay, you must have:
Introduction

Supported Processors

Processor
Card Types
Optional Features
Visa Platform Connect
Supported acquirers:
  • Advanced Bank of Asia Cambodia (ABA Bank) on Visa Platform Connect
  • BAC Credomatic Cost Rica and BAC Credomatic Panama on Visa Platform Connect
  • BAC Credomatic Guatemala on Visa Platform Connect
  • BAC Credomatic Honduras on Visa Platform Connect
  • BAC Credomatic Nicaragua on Visa Platform Connect
  • BAC Credomatic El Salvador on Visa Platform Connect
  • BC Card Co., Ltd on Visa Platform Connect
  • Commercial Bank of Qatar on Visa Platform Connect
  • Maybank on Visa Platform Connect
  • Mastercard
  • Visa
  • Recurring Payments
Introduction

How Google Pay Works

The following figure describes the Google Pay workflow:
  1. The customer chooses the Google Pay button. Using the Google API, your system initiates the Google Pay request identifying
    Cybersource
     as your payment gateway, passing your
    Cybersource
     merchant ID as the gateway merchant ID.
  2. The customer confirms the payment. The Google API contacts Google Pay services to retrieve the consumer’s payment parameters.
  3. If the customer’s selected payment credentials are tokenized, or you are tokenizing new payment credentials, the Google Pay service contacts the appropriate payment network to retrieve the appropriate cryptogram.
  4. The payment network returns the appropriate token and cryptogram to the Google Pay service.
  5. Google creates encrypted payment data using the gateway-specific key that is supplied in the Wallet request and includes it in the Google API response.
  6. The Google Pay callback returns the encrypted payment data.
  7. Your system prepares the Google Pay response information for submission to the
    Cybersource
     service.
    1. Cybersource
       sends the authorization request to the acquirer.
    2. The acquirer processes the request from
      Cybersource
       and creates the payment network authorization request.
    3. The payment network processes the request from the acquirer and creates the issuer authorization request.
    4. The issuer processes the request from the payment network. The issuer looks up the payment information and returns an approved or declined authorization message to the payment network.
    5. The payment network returns the authorization response to the acquirer.
    6. The acquirer returns the authorization response to
      Cybersource
      .
  9. Cybersource
     returns the authorization response to your system.
  10. Your system returns the authorization response to the payment application.
  11. The payment application displays the confirmation or decline message to the customer.
    1. The acquirer submits the settlement request to the issuer for funds.
    2. The issuer supplies the funds to the acquirer for the authorized transactions.
Introduction

Additional Services

These additional services can be used with Google Pay.

Follow-on Services

After the authorization is requested, you can request follow-on services to complete the transaction. For more information on these services, see Follow-on Services.
Authorized Reversal
An authorized reversal is a follow-on service that uses the request ID returned from the previous authorization. An authorization reversal releases the hold that the authorization placed on the customer’s credit card funds. Use this service to reverse an unnecessary or undesired authorization.
Capture
A capture is a follow-on service that uses the request ID returned from the previous authorization. The request ID links the capture to the authorization. This service transfers funds from the customer’s account to your bank and usually takes two to four days to complete.
Sale
A sale is a bundled authorization and capture. Request the authorization and capture services at the same time.
Cybersource
 processes the capture immediately.

Follow-on Transactions

After the payment transaction is complete, additional follow-on transactions can be made as Merchant-Initiated Transactions (MITs).
For more information on how to process MITs, see
Merchant-Initiated Transactions
.
MITs include:
  • Delayed Authorizations
  • Incremental Transactions
  • Installment Payments
  • No-Show Transactions
  • Reauthorizations
  • Recurring Transactions
  • Resubmissions
  • Unscheduled Transactions
Introduction