Google Pay™

Overview

Bluefin TECS Payment Gateway offers and fully integrates with the Google Pay™ as a payment method through our TECS Web Iframe.

Adding Google Pay to your payment methods allows your customers to use their stored Google Pay data to quickly and securely pay for goods and services.

With Google Pay, customers can make purchases using credit or debit cards stored in their Google account. Customers get to experience a simpler checkout process whether they are buying from their Android devices, on the web, or in-store through POS terminals. For more, see Learn What the Google Pay App Is & How To Use It.

The TECS Web iframe embeds this payment method involving a Google account during the checkout process, following its own workflow. It uses its own Google authentication method and form to enter and encrypt the sensitive information (in order to store a credit/debit card). For the required extra security as a payment service provider, we comply with the PSD2 regulations and SCA requirements as detailed out below.

🚧

PSD2, SCA, and 3D Secure Handling as a Payment Service Provider

Google Pay supports both tokenized and non-tokenized (PAN_ONLY) payment methods. Merchants are not required to implement 3D Secure (3DS) for PAN_ONLY transactions themselves.

As the Payment Service Provider (PSP), we manage the entire 3DS flow based on regional requirements and compliance rules. This means we determine when 3DS needs to be triggered.

Specifically, when a PAN_ONLY transaction without a cryptogram (CRYPTOGRAM_3DS) is detected, we automatically initiate the 3DS process, ensuring that the transaction is handled as a standard 3DS transaction.

Bluefin, as a payment service provider, fully complies with PSD2 (Payment Services Directive 2) regulations and enforces Strong Customer Authentication (SCA) requirements as mandated. For more, see Visa | Strong Customer Authentication.

For more on the Bluefin TECS Web 3D Secure Authentication Flow and use cases, refer to Introduction | 3D Secure Transaction.

The merchant is not dependent on understanding and using the Google Pay™ Web API in order to handle its specific checkout data directly.

Once the merchant is integrated with our eCommerce payment gateway and the Google Pay™ method (accepting the Google Pay™ terms and policies), the setup and configuration is taken care of by the Bluefin's integrations team (contact email: [email protected]).

Upon TECS Web URL creation, the Google Pay™ method is presented as one of the payment methods of the web iframe with the method settings configured according to the merchant's needs.

📘

Compatibility and References

For more information on Google Pay™ availability, refer to:

• List of countries where you can use Google Pay
• List of supported browsers
• Adhere to Google Pay Acceptable Use Policy

For all the features that Google Pay offers during online checkout, refer to Google Pay: Seamless online checkout.

Bluefin TECS Merchant Onboarding

📘

Terms and Policies

These terms and policies are directly referenced from the Google Pay™ | Frequently Asked Questions.

Google Pay API Terms of Service

All merchants must agree to and adhere to the Google Pay API Terms of Service.

Google Pay API Acceptable Use Policy

All merchants must agree to and adhere to the Google Pay API Acceptable Use Policy.

The Bluefin integrations team enables the Google Pay™ payment method during the merchant on-boarding process via the TECS management portal (PAM) and accepting the terms defined in the Google Pay API Terms of Service.

TECS Web Iframe

After the merchant server creates Tecs Web Request Token, the Tecs Web iframe contains Google Pay as one of the preferred payment methods the customer can select to process their payment.

Selecting Payment Method

🚧

allowedCardNetworks

The card networks the Bluefin TECS Payment Gateway supports through the Google Pay Web API as allowedCardNetworks are AMEX, MASTERCARD, VISA, DISCOVER.

Adding Credit or Debit Card

After you have selected the Google Pay™ payment method, the TECS Web iframe will spawn a Google browser pop-up window as a payment sheet to enter the GPay sensitive information via the Google Account used during the checkout process.

The following screenshot is the case when the customer doesn't have a card previously stored on our Google account.

After the customer submits the encrypted data through the Google account, the transaction process follows the TECS workflow using the Google checkout data in the backend of TECS Payment Gateway. For the illustrated workflows, refer to the Introduction | Use Cases.

As mentioned above, when a PAN_ONLY transaction without a cryptogram (CRYPTOGRAM_3DS) is detected, we automatically initiate the 3DS process, ensuring that the transaction is handled as a standard 3DS transaction.

Testing & Go Live

To test Google Pay™ while in the certification/testing environment of your Bluefin TECS eCommerce integration, you have two different options:

• Login to a Google account and create a Google Pay wallet with valid card details.
• Follow the requirements and use a sample card from Google's test card suite.

For all the TECS environment endpoints, check out API Endpoints.

📘

Production

In production, Google Pay™ will only be available if:

• The customer is logged in to their Google account.
• The customer has at least one valid payment method on their Google Pay account.