Skip to main content

Google Pay

Introduction​

Google Pay™ is a contactless payment service that enables users to make payments both online and in physical stores using Android devices. It simplifies payments by securely storing card details and allowing transactions via NFC technology.

Google Pay™ transactions use tokenization to protect sensitive card information, replacing the actual card number with a virtual account number. This ensures secure processing without exposing card details. Google Pay™ supports one-time transactions as well as subscriptions and other recurring payments, based on merchant configurations.

Google Pay™ is available in various regions worldwide, supporting multiple currencies. For online and in-app payments, SmartPay's SDK securely collects payment details, which are then transmitted to Apple's servers for processing and authorization. The entire flow keeps sensitive data hidden from the merchant, providing customers with a secure and easy payment experience.

Workflows and Transaction Types​

SmartPay Integration Flow for Merchants​

Merchants should adhere to the integration process detailed in the Google Pay™ Integration Prerequisites, ensuring all registration and verification steps are completed.

Customer Initiated Transactions (CIT)​

  • Guest Payments: Google Pay™ facilitates guest payments without the need to store payment credentials.
  • Registered Users: Registered users can store Google Pay™ as a payment option for streamlined future transactions.

Merchant Initiated Transactions (MIT)​

  • Subscriptions: Google Pay™ supports recurring payments for subscription services.
  • Storable Payment Option: Google Pay™ can be stored as a payment option, enabling efficient future transactions.

Transaction Status Flow​

Merchants should implement SmartPay notifications to receive transaction status updates. Upon receiving a notification, merchants must call the Get Payment Status API to verify the transaction status.

Google Pay™ Integration Prerequisites​

Integration of Google Pay™ payment option includes registration, preparation and testing of the new payment option.

After the testing is successful, it is possible to continue with the preparation for production deployment.

The merchant provides integration details to both Google™ and dedicated Product Solutions Specialist during the integration process.

info

Only VISA and Mastercard are supported payment options for Google Pay™.

1. Registration with Google™ and JPM MPS​

  1. Merchant creates the account and provides company legal details to Google at Google Pay™ Console.
  2. Merchant provides Merchant ID of Google™ to the Product Solutions Specialist for configuration.
  3. Merchant integrates with JPM MPS using SmartPay's SDK.

2. Customization of Google Pay™ button​

The Google Pay™ button can be customized. The following parameters can be configured:

Color customization - color of the Google Pay™ button

  • Default: the standard Google Pay™ button color.
  • Black: the button will appear in black.
  • White: the button will appear in white.

Button type customization - the action associated with the Google Pay™ button in the paymentForm:

  • Book: the button is related to booking a product or service.
  • Buy: for purchasing products or services.
  • Checkout: the button is part of a checkout process.
  • Donate: donation-related actions.
  • Order: for placing an order.
  • Pay: the button is specifically for payment.
  • Plain: a simple, unbranded button.
  • Subscribe: subscription-related actions.

Contact your dedicated Payment Product Specialist if you would like to customize the Google Pay™ button.

3. Test Google Pay™ on the testing environment​

Testers need to join a Google™ group to be automatically enrolled for using test cards in the test/integration environment.

Join the group using an account registered with Google™ in the registration process.

info

For authorization add "paymentOptionCode": GGLPAY.

Merchants can now use END-TO-END functionality for seamless payment completion. When a tester clicks on the Google Pay™ button, the process maintains the browser's user activation behavior, allowing the Google Pay™ API to display a payment sheet without interference from pop-up blockers.

important

Before processing the transaction, the merchant must display a final price to the user. If the amount to be charged has varied based on data received from the Google Pay™ API, the merchant is expected to show a confirmation page with the final price.

info

Storing Google Pay™ is allowed only in case of subscriptions and unattended MIT payments.

important
  • For TEST environment, only test cards from Google Chrome are accepted.
  • For PROD environment, only Google Wallet cards are accepted.

4. Integration prerequisites for Production​

Once the testing is done, the next step is preparing for the production deployment and implementing the procedure for going live. During this phase, the merchant provides integration details to both Google and dedicated Product Solutions Specialist for activation:

  • Google Pay™ integration type.
  • Screenshots of the checkout.
  • Registration of Shop domain that hosts the checkout.
  • Registration of Google Pay™ connector URL.

Before going live in production, the merchant should submit integration details to Google via the Google™ Console.

Before submitting the integration to Google for validation with a PaymentsClient configured for a TEST environment, ensure that the exit criteria are fulfilled for each of the following functional and branding checks:

4. 1. Google Pay™ integration type​

For Google Pay™ API integration type, select: Gateway.

4. 2. Screenshots of the Checkout for Google Pay™​

Provide the following screenshots of the Checkout for Google Pay™ through Google Console:

  • Item selection - screenshot of the UI when the user is browsing an item or service.
  • Pre-purchase screen - screenshot of the UI when the user is ready to make a purchase.
  • Payment method screen - screenshot of the UI when the user selects Google Pay™ as their payment method.
  • Google Pay™ API payment screen - screenshot of the UI when the user is shown the payment info, they've saved it to Google Pay™.
info

Android doesn't allow taking a screenshot of this screen, so the screenshot should be taken using another device.

  • Post-purchase screen - screenshot of the UI when the user has made a successful purchase.

4. 3. Registration of the shop domain​

Register the Shop domain that hosts the checkout to Google through Google™ Console.

info

Provide this domain to the dedicated Product Solutions Specialist upon registration with Google™.

4. 4. Registration of the Google Pay™ connector​

Register the Google Pay™ connector URL: api.googlepay.upcf.jpmmps.com through Google™ Console.

4. 5. Request to go live​

After all the steps have been completed, the merchant can request activation for PROD integration through Google™ console.

important

JPM MPS does not support the PAN_ONLY method on PROD, which means that only Google Pay™ with device authentication using Google Wallet APP is supported.

Payment Options Test Data​

For testing Google Pay™ in the sandbox environment, follow the instructions here: Google Pay™ for Web - Test card suite.

 Imprint
|
Data protection and privacy
© 2024 J.P. Morgan Mobility Payments Systems GmbH. All rights reserved.