User experience best practices

If you integrate with the Google Pay API, various scenarios can occur that are dependant on your buyflow and user experience (UX). To improve the UX, consider the following guidelines:

Set the default payment method to Google Pay

If you set existingPaymentMethodRequired , IsReadytoPayRequest returns true when either of the following conditions are met:

  • The customer already has payment card information in their Google account.
  • The customer has a tokenized card provisioned in their Google Pay app.

If you take this action, you reduce the number of clicks it takes for the customer to get through checkout. This is because the payment and shipping information default to the customer's saved methods.

Optimize for minimal clicks

If you charge immediately after you invoke Google Pay, do so with the following considerations:

  • Ensure that a final and total associated price is shown to the customer before you invoke Google Pay.
  • Set CheckoutOption to COMPLETE_IMMEDIATE_PURCHASE so that users can click Pay within the Google Pay selector.

If you implement this customization, you bypass a traditional confirmation screen within the Google Pay selector, and set the correct expectations before the user is charged. It also optimizes the number of screens and steps involved in the checkout flow. This helps to ensure low cart abandonment rates.

Recommend placements for Google Pay

We recommend that you display Google Pay in each of the following four locations:

No matter which of these locations you choose, we recommend that your customized IsReadytoPayRequest method in your buyflow page matches your IsReadytoPayRequest method elsewhere in the purchase experience. This ensures that, based on your specifications of IsReadytoPayRequest , Google Pay can only appear if the customer is ready to pay with Google Pay.

Add Google Pay to the product page

If you have a quick checkout option directly from the item or product page, add Google Pay to the page to facilitate easy checkout.

If you choose this Google Pay placement, you allow the customer to go directly from the item to the Google Pay selector. This reduces the checkout steps and increases conversions on single-item purchases.

Add Google Pay near the standard checkout option

If you have a checkout or cart button, add Google Pay near the standard checkout option, and set Google Pay as the default when IsReadytoPayRequest returns true.

If you choose this Google Pay placement, you can offer the customer the following improvements:

  • A convenient view of all of the items within the cart
  • A final and total associated price
  • The ability to check out immediately

Place Google Pay at the top of the list of payment options

If you add Google Pay as the top option, you can allow the customer to checkout with a single click.

If you choose this Google Pay placement, you can offer the customer the ability to check out immediately.

Place Google Pay above manual entry fields for payment information

If Google Pay is located prominently above any fields that ask for manual entry of payment information, you allow the customer to check out faster and more easily.

If you prominently display Google Pay as the preferred option at this point in your buyflow, you can entice users to complete the purchase flow as fast as possible with Google Pay. This is because Google Pay doesn't require users to manually enter payment information, such as shipping and billing address, if we already have that data.

Set up the shipping address within Google Pay

If you provide shipping, set shippingAddressRequired to true and customize shippingAddressParameters in your PaymentDataRequest object.

If you request shipping information, customers can select or modify a shipping address within the Google Pay screen at the same time that they select or modify their payment information. The response from the Google Pay API then contains both shipping and payment information from your customers for the transaction.

Use Google Pay’s guest checkout process

If you have guest checkout, specify in your request to the Google Pay API what information you need in order to create an account. For example, the Google Pay API can return an email address when you set emailRequired to true in your PaymentDataRequest object. Alternatively, the Google Pay API can return a name when you set billingAddressRequired to true in CardParameters and define the billingAddressParameters .

If you request additional customer information through the Google Pay API, the customer doesn't need to manually fill out all the information required to check out. This maintains a smooth checkout flow.

Use Google Pay to only gather relevant user data

If you gather data returned by the Google Pay API, it must be used for the purpose of the customer’s current transaction only. This includes order confirmation, shipping notification, shipping tracking, order cancellation, refund, and refund notification information.

For example, the Google Pay API can return an email address when you set emailRequired to true in your PaymentDataRequest object.

If you maintain this practice, you can nurture customer trust and loyalty.

Use Google Pay for subscriptions

If you charge for subscriptions with Google Pay, allow the customer to change the backing payment instrument within Google Pay anytime.

If you maintain this practice, users can easily switch between different cards within Google Pay without interrupting the subscription charge.