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.
Only VISA and Mastercard are supported payment options for Google Pay™.
1. Registration with Google™ and JPM MPS
- Merchant creates the account and provides company legal details to Google at Google Pay Console.
- Merchant provides Merchant ID of Google™ to the Product Solutions Specialist for configuration.
- Merchant integrates with JPM MPS using WEB-SDK / SmartPay.
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.
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.
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.
Storing Google Pay™ is allowed only in case of subscriptions and unattended MIT payments.
- 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:
1. Google Pay integration type
For Google Pay API integration type, select: Gateway.
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.
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.
3. Registration of the shop domain
Register the Shop domain that hosts the checkout to Google through Google Console.
Provide this domain to the dedicated Product Solutions Specialist upon registration with Google.
4. Registration of the Google Pay connector
Register the Google Pay connector URL: api.googlepay.upcf.jpmmps.com through Google Console.
5. Request to go live
After all the steps have been completed, the merchant can request activation for PROD integration through Google console.
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.
Useful links when integrating Google Pay
Google Pay Web developer documentation
Google Pay Web integration checklist
Google Pay Web Brand Guidelines
All merchants must login to Google Pay Business Console and accept Google Pay APIs Acceptable Use Policy and agree to the terms defined in the Google Pay API Terms of Service.