Google Pay
Google Pay is the digital wallet offered by Google to store your cards and pay quickly and securely.
Activation
To make this payment method available on the checkout page, it is necessary to configure and activate the service by accessing the page dedicated to Google Pay in the back office. A Google registration is not required.
Payment
Payment with Google Pay is compatible and follows the specifications of the following integration methods:
Below is a summary table of the compatibility and potential limitations of the payment method with the services provided by the XPay gateway:
Countries | Global |
Minimum amount | No limit |
Maximum amount | No limit |
Payment | Yes |
Card verification | Yes |
Preauthorization | Yes |
Maximum preauthorization period | 27 days |
Implicit capture | Yes |
Explicit capture | Yes |
Maximum explicit capture period | 5 days |
Recurring | Yes |
OneClick | Yes |
Full refund | Yes |
Partial refund | Yes |
Multiple partial refunds | Yes |
Maximum refund deadline | 13 months |
Integration with Google API
Through this method, Nexi will only handle the payment authorization; data related to Google Pay will be collected by the merchant's website or app, which will forward the JSON received from Google to Nexi through the API:
To use this service, the merchant must enable the API: https://developers.google.com/pay/api/web/overview. To integrate Google Pay, it is necessary for the merchant to adhere to the Google API Terms of Service, Usage Policy, and Brand Guidelines: https://developers.google.com/pay/api/web/guides/brand-guidelines.
Below is the payment flow:
- The user clicks the Google Pay payment button and sees a payment module with a list of supported payment methods.
- The user selects a payment method, and Google Pay securely returns a payment token for that method to the merchant's website.
- The merchant's website sends the payment token, along with purchase details, to its backend.
- To process the payment, the backend handles the purchase and sends the payment token to Nexi through the API:
POST /orders/googlepay
During integration, Google will request information about the payment provider used during the authorization phase through the "tokenizationSpecification" object. Below are the data to set:
- 'gateway': 'nexi'
- 'gatewayMerchantId': 'MERCHANT_GATEWAY_MERCHANT_ID'
The behavior of the POST /orders/googlepay API varies depending on how Google Pay returns the payload with payment data:
- Payload with tokenized PAN: the API below will process the payment by completing the transaction.
- Payload with clear PAN (real PAN): the API below will not directly process the payment but will return the necessary data to execute it.