Empower Customers by providing a frictionless checkout experience in Android Apps or on your website using Google Pay. Your customers will experience a checkout experience that is not only convenient but also simple to use. You the merchant can expect fewer abandoned payments and enhanced levels of customer satisfaction that will not only encourage customer retention but promote further customer acquisition.
Google Pay supports all the major payment networks: Visa, Mastercard, American Express, Discover, JCB.
Along with that Google Pay supports two authorization methods:
If you currently don't have an account with Windcave, please contact our sales team for details. For informations regarding Hosted Payment Page please refer to this page.
If you are an existing customer who already uses Hosted Payment Page and wants to accept Google Pay, please contact our support team. This will not require any changes on the existing integration.
Google Pay allows for merchant hosted integrations on a web as well as in Android applications.
Please note that Windcave currently support only Google Pay API version 2.
You would also need to consult with Windcave support team to get the list of payment networks that we can enable for your Windcave account.
The merchant hosted integration of Google Pay is currently supported only using Windcave Restful API. The full developer reference for Windcave Restful API can be found here.
Please refer to Google Pay for Payments > Web tutorial for all the details on how to integrate Google Pay on your checkout page.
You would need to make a few Windcave-specific adjustments to the request though. In the payment tokenization options you need to make sure that the type is set to PAYMENT_GATEWAY, the gateway field is set to 'windcave' and the gatewayMerchantId is set to the value provided to you by our support team after you have expressed the interest in doing merchant hosted integration. Here is the example:
Once the Google Pay process is finished and your callback for loadPaymentData is triggered, you need to pass the payment token back to your backend
Here is the example of the payment token:
The backend code should then format and submit the Restful API Create Transaction request incorporating the payment token into it.
Here is the example of Create Transaction request with Google Pay token included:
You will get the response whether the card has been authorized or if there was an error while processing it.
For the full details on request requirements and information that needs to be included please refer to Restful API Developer Reference.
Please refer to Google Pay for Payments > Android tutorial for all the details on how to integrate Google Pay into your Android application.
You would need to make a few Windcave-specific adjustments to the code. In the payment tokenization options you need to make sure that the type is set to PAYMENT_GATEWAY, the gateway field is set to 'windcave' and the gatewayMerchantId is set to the value provided to you by our support team after you have expressed the interest in doing merchant hosted integration.
Here is the example:
Once the Google Pay process is finished and you get access to the PaymentData instance, you need to either pass the payment token back to your backend for submitting to Windcave, or submit the Restful API Create Transaction request directly from the application.
Prior to going live with Google Pay you would need to run test transactions. You should receive two sets of credentials from our support team - test user credentials and production user credentials.
When using test user credentials on your merchant hosted page, you need to make sure that when you construct the instance of PaymentsClient you put the value 'TEST' in the environment field.
You would also need to have real card(s) added into the Google account and/or Google Pay wallet.
In the test environment those cards will not be charged, as Google Pay will include a mock card number into the payment token instead of your real card details.
When using your test credentials in the in-app integration, you would need to make sure that you set the environment to ENVIRONMENT_TEST when constructing WalletOptions.
As with merchant hosted integration, in the test environments your card will not be charged as Google Pay would include a mock card number into the payment token instead of the real card details.
Once the testing is done and you are ready to go live, you would need to switch to using production user credentials and switch the environment to Production.