|
Google Pay™ offers a fast, simple and secure way for customers to handle payments both online and in store using their digital wallet. Integrating Google Pay™ helps merchants deliver a seamless checkout experience, increasing user satisfaction and encouraging repeat business. Merchants need to place a Google Pay™ button in their online shops or mobile apps. Customers are then presented with a payment sheet displaying saved payment methods from their Google Account, along with other optional data like shipping addresses. Google Pay™ allows merchants to customize the payment button's appearance to match the merchant's UI design, while adhering to Google Pay™ branding guidelines. |
Google Pay™ is now available worldwide, however some Google Pay™ and Google Wallet™ payments features are only available in certain countries and on certain devices. For more details, please check with Google Pay™ feature availability.
All currencies that Google Pay™ supports are currently also supported by the PAYONE platform.
Supported Payment methods:
Google Pay™ may use cards or network tokens. Card based payloads consisting of PAN require PCI DSS compliance and 3D-Secure processing. To avoid the software on your server to come in contact with credit card data, PAYONE gets the complexity away from you via our Google Pay™ implementation in combination with the existing 3D Secure and SCA handling available in our gateway.
You can use Google’s sample cards or PAYONE's test cards to perform test transactions.
When testing the Google Pay™ integration with PAYONE, you can utilize PAYONE test cards, which also support the 3DS flow, providing a comprehensive end-to-end testing experience. The account you use for testing with PAYONE test cards must be added to the Google Pay test card suite group.
Google Pay™ supports liability shift to issuers for qualified transactions using Mastercard and Visa Android device tokens (CRYPTOGRAM_3DS). Meanwhile, Google Pay™ PAN-based transactions follow the same liability shift rules based on the results of 3D Secure and corresponding card scheme rules.
The liability shift features are part of Visa and Mastercard programs with Google Pay™ and are subject to card scheme rules. For Visa, merchants can opt-in for "Fraud Liability Protection for Visa device tokens" at the Google Pay™ & Wallet Console.
Details about liability shift for Google Pay™ can be found in the Google Pay™ FAQ.
Merchants with an existing account on our platform who wish to provide Google Pay™ must follow these preparatory steps:
Please contact PAYONE Merchant Services
To integrate Google Pay™ in your online shop or Android app, you must first register with Google and obtain a Google account. Please follow the checklists below:
Before your production access you should read and accept Google Pay™ Terms of Service and adehere to Google Pay™ and Wallet APIs Acceptable Use Policy
Check the criteria for Google Pay™ API as described in Setup section of the Google documentation
PAYONE handles PCI DSS and alleviates the burden from you when using and integrating Google Pay™. You will receive the encrypted payload (payment token data) from Google Pay™ with the PAYONE Public Key. Use the type: "PAYMENT_GATEWAY" to facilitate integration via the PAYONE Gateway and to avoid receiving PAN data on your end..
You should specify PAYONE as your GatewayId:
The Google Pay™ API offers a streamlined checkout process, allowing customers to make purchases using payment methods saved to their Google Accounts. This not only simplifies the checkout process but also enhances security, as customer payment data is encrypted from Google's servers to the payment processor. With easy integration, you can implement Google Pay™ with minimal coding, potentially leading to a significant increase in unique users and sales volume.
Checkout the Google Pay - checkout experience pages for more buyer's experience with Google Pay.
source: Google Developers
Make sure to follow the Google Pay™ brand guidelines before adding Google Pay™ payment button on your online shop.
Integrate Google Pay™ API in your online shop. For detailed instructions please use the Google Pay™ API web integration guide and Google Pay™ API web integration checklist
To process the actual payment, you will need make an API Pre- /Authorization request to PAYONE including the payment token received from Google as Base64 encoded.
The Google Pay™ API provides a streamlined checkout process for native Android applications, enabling customers to make purchases using payment methods saved to their Google Accounts within an app. When the customer clicks the Google Pay button in the app, the payment sheet appears, displaying all their saved payment methods and optional fields for shipping address data.
Integration steps with PAYONE are similar to those for the web. However, the integration of the Google Pay API in an online shop or Android app differs.
source: Google Developers
Make sure to follow the Google Pay™ brand guidelines before adding Google Pay™ payment button on Android application.
Integrate Google Pay™ API in your Android application. For detailed instructions please use the Google Pay™ API Android integration guide and Google Pay™ API Android integration checklist
The following parameters are mandatory for every Google Pay payment method:
Parameter | Description |
---|---|
paymentProductId | Payment product identifier - please check product documentation for a full overview of possible values. ( for Google Pay is 320 ) |
authorizationMode |
Determines the type of the authorization that will be used. Allowed values:
|
encryptedPaymentData | The payment data if we will do the decryption of the encrypted payment data. Typically you'd use encryptedCustomerInput in the root of the create payment request to provide the encrypted payment data instead. |
threeDSecure.redirectionData.returnUrl | The URL that the customer is redirected to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process. Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of protocol://. This protocol must be registered on the device first. URLs without a protocol will be rejected. |
Simple example for a Google Pay payment via Commerce Platform
Creating a Commerce Case with the initial Checkout including a reference, information about the customer and the items in the shopping cart, including also the Apple Pay payment details.
Example without 3D secure redirection.
POST Commerce Case
|
|
You can identify the corresponding transaction by the field createPaymentResponse.payment.id in the order response. The status PENDING_CAPTURE shows that the amount is authorized and the payment gateway is waiting for a capture.
|
Full Deliver to capture the complete order amount.
POST Deliver
|
|
The payment gateway informs you via webhook about the successful capture.
|
Error | Description | Suggested Activity |
---|---|---|
2702 |
Error decrypting Apple Pay / Google Pay token |
Check the environment settings for GooglePay and mode for PAYONE to match either for Test or for Live. |
2703 |
Certificate service declined request because of validation errors. |
Failure to decrypt or validate the Google Pay payment token due to incorrect encoding or malformed json |