On This Page

{#jumplink-list}  
[Markdown](/content/cybsdeveloper2021/amer/en/docs/cybs/en-us/google-pay/developer/fdccompass/so/googlepay/googpay-intro/googpay-how-it-works.md)

How Google Pay Works {#googpay-how-it-works}
============================================

The following figure describes the Google Pay workflow:  
![](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/googlepay/images/trans_flow.png/jcr:content/renditions/original)

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.
8. 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.
12. The issuer supplies the funds to the acquirer for the authorized transactions.

