Purchase Flow

Purchase Flow

Overview

Once the accounts have been associated together, the newly created instrument can be used for purchases. Purchases within Google occur in one or two modes:

  • User-initiated
  • System-initiated

Regardless of the mode chosen, in the typical case, the Integrator UI will not be involved in purchases.

How the flow works

The diagram below shows a user-initiated purchase.

Purchase flow-User present

Purchase flow

The objects in the diagram include the following:

  • User: This is the person who wants to purchase something through Google.
  • Google UI: The interface, where the customer begins to make a purchase.
  • Google Server: The backend server at Google that sends the capture command to the Payment Integrator Server.
  • Payment Integrator Server: The backend server of the integrator that accepts the request for a funds capture.

In this purchase flow, the user is in session. They begin the flow by starting to purchase an item.

  1. The User begins to purchase an item through the Google UI.
  2. The purchase information is sent to the Google Server.
  3. Google’s Server sends the Capture request (GPT, amount) to the Payment Integrator Server.
  4. The Payment Integrator Server sends back a Success response to the Google Server.
  5. The Google Server sends back a Success response to the Google UI.
  6. The items are delivered to the customer.

A system-initiated flow is shown below. In this case Google’s system has initiated the payment on the user's behalf. This can happen for a variety of reasons (for example, a monthly subscription).

In this situation the user is not in session.

Purchase flow-User not present

System purchase flow

The objects in the diagram are as follows:

  • Google Server: The backend server at Google that initiates the purchase.
  • Payment Integrator Server: The backend server of the integrator that accepts the request for a funds capture.

In this purchase flow, the user is not present. The Google Server initiates the purchase.

  1. The Google Server triggers a purchase flow with the user not in session.
  2. The Google Server sends a Capture command, including the GPT and the amount of purchase.
  3. The Payment Integrator Server replies with a message of Success.

Best practices and other considerations

The integrator and/or Google may send the user through the re-authentication flow before making a purchase due to various reasons. Some possible reasons include:

  1. Google's risk engine determines that a payment looks suspicious.
  2. Regulatory requirements demand an OTP upon every purchase.

In such cases, Google re-authenticates the user and then allows the user to complete the purchase flow. The result of the re-authentication flow is the proof of user identity and authentication. During the purchase flow, the re-authentication result is sent to the Payment Integrator along with the purchase information.