on web

Integrating Google Pay into a website can be done either through:

Redirect and embedded methods require integration only with Flitt's API or SDK and thus less coding and complexity.

Integrating Google Pay with Google Pay API directly requires additional Apple certificates management and encryption/decryption procedures coding.

Direct method also involves different approaches depending on tokenized Primary Account Number (DPAN) or an encrypted payment container is used during payment flow processing.

Google Pay with redirect to Flitt checkout page¶

Refer to create order to create order on your backend or frontend and redirect payer to the checkout page. Google Pay button will automatically appear at checkout page. The payment is processed on Flitt’s secure platform, reducing complex coding and the risk of handling sensitive data.

Google Pay button, embedded to merchant website¶

Embedded method provides a seamless checkout experience without leaving the merchant website, which can increase conversion rate.

Embedded Google Pay button can be placed in a way to fit the look and feel of the website, providing a more cohesive brand experience.

This type of integration also gives greater control over the checkout process and design.

Meanwhile, this method is more complex than redirect method to implement, requiring more development resources and expertise.

Example Google Pay button:

See the Pen Flitt - Apple, Google Pay buttons by Flitt.com (@flitt) on CodePen.

Verify your domain in Google Pay developer account

To embedd Google Pay button from Flitt, you must register all of your web domains where button will be displayed. This relates to top-level domains (for example, site.com) and subdomains (for example, shop.site.com, www.site.com), both production and development sites.
Tell Flitt to activate your domain with Google.