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.

Requirements

Before using Google Pay, you must have:
  • A
    Cybersource
     merchant evaluation account if you do not have one already:
  • A merchant evaluation account with a supported processor. See Supported Processors.
  • The
    Cybersource
    REST
     API Client installed on your system.
  • A Google developer account.
  • Google Pay APIs embedded into your application or website.
    For details about integrating Google Pay, see the Google Pay API documentation.
Payment Network Tokens

Supported Processors

Merchant-initiated transactions and multiple partial captures are described in the
Authorizations with Payment Network Tokens
 guide. Recurring payments and split shipments are described in the
Credit Card Services
 guide.
Processor
Card Types
Optional Features
Visa Platform Connect
Supported acquirers:
  • Australia and New Zealand Banking Group Limited (ANZ)
  • Vantiv
  • Westpac
  • Mastercard
  • Visa
  • Recurring Payments
Payment Network Tokens

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.
Payment Network Tokens

Additional Services

The following additional services can be used with Google Pay. For more information on these services, see the
Credit Card Services
 guide.
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.
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.
Payment Network Tokens

Transaction Endpoints

The following endpoints are used with Google Pay:
  • Test
    : http://ics2testa.ic3.com
  • Production
    : http://ics2a.ic3.com
Payment Network Tokens