Antom, leading provider of tailored payment solutions
Contact Us
Log In

Accept payments with Google Pay

Through the Google Pay service, buyers can make payments using credit or debit cards stored in their Google accounts. With Antom Payment Element, you do not need to integrate the Google Pay SDK separately. Payment Element will automatically load Google Pay for you and can be configured to support Google Pay as an express payment method.
Web/WAP
Android

After payments

After completing the payment, you can perform the following actions:

Cancellation
Server-side

For successful payments, if the buyer requests cancellation or a refund on the same day, you can use Antom’s cancellation capability to cancel the order or release funds. Orders not yet completed can also be cancelled directly. For details, refer to Cancel.

Refund
Server-side

Different payment methods have varying refund capabilities. To learn about Antom refund rules and how to initiate a refund for a successful transaction, refer to Refund.

Dispute
Server-side

Antom provides dispute resolution services for contested transactions. For more information, refer to Dispute Guidance and Dispute resolution.

Additional content

Antom also offers the following customization options:
  • Specify payment methods: You can use API parameters to define which payment methods are displayed in Payment Element, control the order of the payment method list, and configure the display of express payment options.
  • Payment method features: Learn about the characteristics of APM and card payments.

Best practice

Card payment features also apply to Google Pay. The following table outlines the support status of these features for Google Pay:
Type
Supported
Conditions
Antom Tokenization
Conditional
  • ​Not supported in CIT (Cardholder-Initiated Transaction) scenarios. It is recommended to store cards via Google accounts.
  • Supported in MIT (Merchant-Initiated Transaction) scenarios.
COF
Yes
None
3D Secure 2
Yes
  • If you set the paymentMethodMetaData.googlePayConfiguration.allowedAuthMethods parameter to
    CRYPTOGRAM_3DS
    (or use the default value), and 3DS authentication has already been completed on the Google Pay side, Antom will follow the standard third-party 3DS processing flow. As a result, no additional 3DS experience will be triggered by the payment method within the Payment Element. For details, refer to Google Pay - Enabling liability shift for eligible Visa device token transactions globally.
  • If you set the paymentMethodMetaData.googlePayConfiguration.allowedAuthMethods parameter to both
    CRYPTOGRAM_3DS
    and
    PAN_ONLY
    (or use the default value), and 3DS authentication has not been completed on the Google Pay side, Payment Element will determine whether 3DS authentication is required based on the values you provide for the is3DSAuthentication and enableAuthenticationUpgrade parameters.
Antom 3DS-Retry
Yes
None
MIT
Yes
None
Installment payments
No
None