Google Pay

Specific information about the payment method Google Pay.

The Google Pay payment service allows consumers to make contactless and in-app payments as frictionless and secure as possible. Customers can securely store credit and debit card information in their Google Pay wallets and confirm transactions by authenticating on their Android device or Google Chrome browser. Google Pay transactions are still MasterCard, Visa or American Express card transactions (as it is their cards that "sit" in the wallet). However, existing card processing connections and merchant acquiring connections may support these Google Pay payments.

When using Google Pay, you will have to take care of the following things for the integration:

  • Pre-requisite for processing payments is a full integration of Google Pay. More information can be found here. You can follow the full example for detailed step-by-step information.
  • The Google Pay button must be displayed on the checkout page in your web shop. Please also check the detailed Google Pay documentation.
  • Before Go Live, please consult the Google Integration Checklist

IMPORTANT NOTE: When setting your payment tokenization method, only aciworldwide is currently supported.

Basic process
  • The customer selects Google Pay as the preferred payment method.
  • Once the customer clicks on the buy button, he will be shown the "action chooser".
  • The customer logs in to their Android Pay/Google account with the help of the "action chooser".
  • The customer selects the preferred payment method and shipping address.
  • After confirmation, the customer will be redirected to the web shop.
  • The customer reviews and confirms the purchase information as shown in the web shop.
  • The merchant requests the payment credentials for the customer's Android Pay/Google account.
  • Once the merchant has processed the payment, a confirmation page including a confirmation number for successful transaction will be displayed to the customer.


Google Pay as well as Accounting as a Service generally support both payment execution options, authorize and capture in 2 steps or authorize and capture in 1 step. By default, authorize and capture will be applied in 1 step. In case you want to execute authorize and capture in 2 steps as your default flow, the related configuration is part of the onboarding procedure and can be found in the technical application. Should you already have been onboarded, please contact us or send us your request for configuration change.


The settlement for GooglePay payments follows the standard technical PSP model in Accounting as a Service. Google Pay payments can not be differentiated from normal card payments.


In case of a refund to be handled as part of a return, you should follow our use case Return creation to trigger the refund procedure in Accounting as a Service. Alternatively, if the refund happens in the context of a goodwill procedure, please follow the use case Good will creation for triggering a goodwill credit within Accounting as a Service.

See also