Google Pay
Intro
Google Pay™ is a digital wallet for online payments offered by Google.
It is a very versatile solution, as customers can add credit/debit cards to their wallet and use them for:
- Android devices in-store and supported websites
- Mobile apps
- Google services
By combining the Google API with our CreatePayment API, the payment process is fast, easy and secure. Boost your conversion rate with these features:
- Your customers simply tap on a device in stores or on a button in a mobile app.
- Google Pay™ and we manage all sensitive customer data for you.
- A safe encryption/decryption method elevates your customers' trust in the whole payment process and significantly reduces online fraud: neither are customer details sent during the payment process nor show Browsers/devices ever unmasked card numbers.
To make all this possible, Google Pay™ tokenises your customers' cards. Google Pay™ identifies two types of cards:
- Non-network tokenised cards: standard physical credits card that require a 3-D Secure check for additional protection against fraud. This is only applicable for payments going through your own checkout page.
- Network tokenised cards: virtual card with a device-specific account number (DPAN). These kind of cards are used in place of the underlying source card. As the digital signature of the mobile device used for the payment protects these cards from fradulent use, 3-D Secure is unnecessary. This is only applicable for customers using a mobile device.
Your customers can use cards from the following brands:
- Google Pay - Visa
- Google Pay - MasterCard
- Google Pay - American Express
Key benefits
- No personal data shared
- Low PCI requirements (no sensitive or personal data shared)
- Allows any standard maintenance operation depending on your acquirer
- Available through Full Service
Onboarding
Please make sure:
- To get a test/production account on our platform.
- That this payment method is active in your account. Check this in the Merchant Portal via Business > Payment methods.
Are you using the Back Office?
You can check the payment method’s activation status via Configuration > PM activation. - To accept the Terms of Service of Google and to adhere to Google Pay API Acceptable Use Policy.
- To meet the requirements for the Google Pay™ API (check the Setup section of the Google documentation and the guidelines for acceptable use).
- To get a Google account and integrate Google Pay™ either in your webshop payment page according to this checklist / or via Android according to this checklist.
- Create successful test transactions, as this is Google’s requirement to get production access to their platform and their approval to use this payment method on your checkout page/in your app. Learn more on Google’s "Request production access" and "Deploy production environment" section.
Use the information available in our Integration and the Testing chapter to get this done.
Countries & currencies
Supported countries
-
Albania
-
Algeria
-
American Samoa
-
Angola
-
Antigua and Barbuda
-
Argentina
-
Australia
-
Austria
-
Azerbaijan
-
Bahrain
-
Belarus
-
Belgium
Brazil
Bulgaria
Canada
Chile
Colombia
Croatia
Czech Republic
Denmark
Dominican Republic
Egypt
Estonia
Finland
France
Germany
Greece
Hong Kong
Hungary
India
Indonesia
Ireland
Israel
Italy
Japan
Jordan
Kazakhstan
Kenya
Kuwait
Lebanon
Lithuania
Luxembourg
Malaysia
Mexico
Netherlands
New Zealand
Norway
Oman
Pakistan
Panama
Peru
Philippines
Poland
Portugal
Qatar
Romania
Russia
Saudi Arabia
Singapore
Slovakia
South Africa
Spain
Sri Lanka
Sweden
Switzerland
Taiwan
Thailand
Turkey
Ukraine
United Arab Emirates
United Kingdom
United States Minor Outlying Islands
United States
Uruguay
Vietnam
Supported currencies
- Albanian lek (ALL)
- Algerian dinar (DZD)
- Angolan kwanza (AOA)
- Argentine peso (ARS)
- Armenian dram (AMD)
- Aruban florin (AWG)
- Australian dollar (AUD)
- Azerbaijani manat (AZN)
- Bahamian dollar (BSD)
- Bahraini dinar (BHD)
- Bangladeshi taka (BDT)
- Barbados dollar (BBD)
Integration
With Google Pay™, your customers can purchase goods/services with a credit or debit card stored in their Google account. Whether they are shopping from their Android devices or in the internet, the payment process is much simpler: Google Pay™ displays a payment sheet that selects the preferred card payment method that the buyers confirm.
Check out the video to how buyers pay with Google Pay™.
To receive a liability shift when using Google Pay™, you must authenticate the transaction with 3-D Secure.
Our platform offers you two types of integration for your business:
Find a high level overview in the "Process flows" chapter.
- When using the Google API, make sure to consult the Web / Android / Web Google Pay™ Brand Guidelines. They tell you about the Google Pay™ do’s and don’ts, show the types of supported buttons and best practices to max out your conversion rate.
- To use this payment method, your customers need to install the Google Pay™ app on their device.
- If you want to offer Google Pay™ on your own checkout page, make sure both Visa and MasterCard are active in your PSPID. Check this in the Back Office (Configuration > Payment methods). Contact us if it is not active yet.
- This integration mode requires your customers with a desktop/tablet device to pay with regular credit cards. In such a scenario, 3-D Secure is mandatory. Learn here how to implement 3-D Secure in the transaction flow.
Google Pay™ on your own Checkout page
Use our JavaScript SDK to implement Google Pay™ with the Google Pay™ button directly into your own checkout page. In this case, you need to open a Google Pay™ sheet and get the payment token that Google will encrypt for you with our public key.
When you have received the payment token, you have to send it to us using our Create Payment API call though the Server API to complete the payment. After this step, we will hand the decryption for you.
To do so, you need to:
- Open a Google Pay™ sheet.
- Get the payment token that Google encrypts for you with our public key with the Google API.
- Send the payment token using our CreatePayment API with one of our Server SDKs so we can handle the decryption for you.
This integration mode gives you the following benefits:
- Better visibility of the Google Pay™ button on your website for higher conversion.
- You can use the Google Pay™ API to retrieve your customer’s personal details as their address or email.
Once you have followed the Google’s setup guidelines, you are ready for the technical integration . Google offers a very clear and and concise tutorial on how to implement Google Pay™ on your Website. The technical integration includes the following steps:
- Retrieve GooglePay™
- Get available Credit card networks
- Comply to Strong Customer Authentication (SCA)
- Render Google Pay™ button
- Initialise Payment sheet
- Get payment token
- Send payment token
- Because you use us to decrypt sensitive payment information, Google uses the following type of tokenization: PAYMENT_GATEWAY. We will explain the how-to in the following steps.
- Depending on the device used for the payment, two scenarios are possible:
- 1. Mobile devices: Your customers use a network-tokenised card for the payment. These virtual cards are linked to a device-specific account number (DPAN). A digital signature protects these card from fraudulent use, making 3-D Secure unnecessary.
- 2. Desktop/Tablet devices: Your customers use a non-network tokenised card for the payment. These are standard physcial credit cards that require a 3-D Secure check. Step
“Send payment token” explains in detail what you have to do in either case.
1. Retrieve Google Pay™
Use the JavaScript Client SDK to retrieve the Google Pay™ payment product via the payment product(s) API call. This will provide you the data needed for the next steps, such as the supported networks. When receiving the payment produt information, the SDK will also call the Google API isReadyToPay to check whether Google Pay™ is available on the device and the settings that your consumers are using. If the call throws an error, the SDKS will not return Google Pay™ as a usable payment method for the transaction.
Use the following code sample to make the call:
// session is an instance of the Session object, which is the main entry point for the SDK
session.getPaymentProduct(320, paymentDetails, paymentProductSpecificInputs).then(
function(paymentProduct) {
// Google Pay™ is available, show the Google Pay™ button
// Store the payment product in the Connect payment request
session.getPaymentProductRequest().setPaymentProduct(paymentProduct);
},
function() {
// Google Pay™ is not available, offer your customer another payment option to complete the payment
}
);
2. Get available credit card networks
You have to specify the credit card network allowed for the current Google Pay™ transaction. The GetPaymentProduct call (both via client-to-server and server-to-server) returns the available networks . The networks are available in the response paymentProduct320SpecificData field. The Google Pay™ API directly acceptes the return values.
Since we decrypt for you the Google Pay™ment token, you need to set a specific value for the ‘gateway’ field in the tokenizationSpecification. This value is also available in the paymentProduct320SpecificData. The gatewayMerchantId is your own merchantID (PSPID) on our platform.
- merchantID: the merchantID you get from Google after registration with the Google Pay™ Business Console.
- merchantName: the name that is rendered in the payment sheet. This is mandatory if you are based in the European Economic Area (EEA) to meet the Strong Customer Authentication (SCA) requirements. Encode the merchantName as UTF-8 according to Google's specifications.
- gateway: use the value returned in the product-response : paymentProduct.paymentProduct320SpecificData.gateway.
- gatewayMerchantId: your merchantID (PSPID) on our platform.
Use the following code snippet to initialise both allowedCardNetworks and the tokenizationSpecification after you have received the Google Pay™ payment product:
Initialise Google Pay™
// If you want to use Google Pay™ in your application, you are required to register
// with Google in order to receive a Google Merchant ID
var paymentProductSpecificInputs = {
googlePay: {
merchantId: '
',
merchantName: '
',
gatewayMerchantId: '
'
}
};
// Retrieve the Google Pay™ Payment Product via the client to server API
// It is assumed that the session, paymentDetails and paymentProductSpecificInputs objects here are all valid
session.getPaymentProduct(320, paymentDetails, paymentProductSpecificInputs).then(
function(paymentProduct) {
const allowedCardNetworks = paymentProduct.paymentProduct320SpecificData.networks;
const tokenizationSpecification = {
type: 'PAYMENT_GATEWAY',
parameters: {
gateway: paymentProduct.paymentProduct320SpecificData.gateway,
gatewayMerchantId: paymentProductSpecificInputs.googlePay.gatewayMerchantId
}
};
// Store the payment product in the payment request which is required for
// creating the encryptedCustomerData later on
session.getPaymentRequest().setPaymentProduct(paymentProduct);
},
function() {
// Google Pay™ is not available, offer your customer another payment option to complete the payment
}
);
3. Comply to Strong Customer Authentication (SCA)
If your acquirer is from the European Economic Area (EEA) , you must submit the acquiring bank’s country/region information to Google in TransactionInfo.countryCode. This will ensure you comply with SCA requirements. Google Pay™ will return corresponding transaction data based on the country/region of your acquirer .
The payment product API call from the Client SDK or the Server-to Server returns the acquirerCountry you have to send to Google. The following code shows how to
- obtain the Acquirer Country code from the payment product response and use it to initialise Google Pay™.
- get the result field of the transactionInfo object.
- specify the totalPrice and MerchantName parameters (as described in step 8.3 of the Google Pay™ tutorial and in the Strong Customer Authentication section on Google's documentation site).
Find more information on Strong Customer Authentication compliance for Google Pay™ at the Google Pay™ API documentation and in our dedicated guide.
Strong Customer Authentication (SCA) compliance
// If you want to use Google Pay™ in your application, you are required to register
// with Google in order to receive a Google Merchant ID
var paymentProductSpecificInputs = {
googlePay: {
merchantId: '
',
merchantName: '
',
gatewayMerchantId: '
'
}
};
//https://developers.google.com/pay/api/web/reference/request-objects#TransactionInfo
var transactionInfo = {
currencyCode: 'currency code=""',
totalPriceStatus: 'final',
totalPrice: 'amount'
};
//Retrieve the Google Pay™ Payment Product via the client to server API
// It is assumed that the session, paymentDetails and paymentProductSpecificInputs objects here are all valid
session.getPaymentProduct(320, paymentDetails, paymentProductSpecificInputs).then(
function(paymentProduct) {
const acquirerCountry = paymentProduct.acquirerCountry;
if (acquirerCountry != null) {
transactionInfo.countryCode = acquirerCountry;
}
},
function() {
// Google Pay™ is not available, offer your customer another payment option to complete the payment
}
);
To make sure the transaction is process according to the SCA guideline, populate these fields to cover your customer's device.
customer.device.acceptHeader
customer.device.browserData.colorDepth
customer.device.browserData.javaEnabled
customer.device.browserData.screenHeight
customer.device.browserData.screenWidth
customer.device.ipAddress
customer.device.locale
customer.device.timezoneOffsetUtcMinutes
customer.device.userAgent
Find more information about these fields in our complete 3-D Secure properties overview.
4. Render Google Pay™ button
If Google Pay™ is available, add the Google Pay™ button on your checkout page. Make sure to follow Google’s guidelines on displaying the Google Pay™ button and Google's brand policy.
Use the following code sample to add it:
Add Google Pay™ button
function addGooglePayButton() {
const paymentsClient = getGooglePaymentsClient();
const button =
paymentsClient.createButton({
onClick: onGooglePaymentButtonClicked
});
document.getElementById('container').appendChild(button);
}
5. Initialise payment sheet
Respond to the customer using the Google Pay™ button by creating a Google Pay™ payment session for the payment:
Show Google Pay™ payment sheet
function onGooglePaymentButtonClicked() {
const paymentDataRequest = getGooglePaymentDataRequest();
paymentDataRequest.transactionInfo = getGoogleTransactionInfo();
const paymentsClient = getGooglePaymentsClient();
paymentsClient.loadPaymentData(paymentDataRequest).then(function(paymentData) {
// handle the response
processPayment(paymentData);
}).catch(function(err) {
// show error in developer console for debugging
console.error(err);
});
}
6. Get payment token
To process the actual payment, you need to request the payment token from Google. To do so, use the following code snippet:
Get the Google Pay™ payment token
function processPayment(paymentData) {
var paymentToken = paymentData.paymentMethodData.tokenizationData.token;
@todo process the paymentToken as described in the next step
}
7. Send payment token
In the Create payment API call, you can provide payment tokens in two different ways:
- Send the token in property mobilePaymentMethodSpecificInput.encryptedPaymentData. Make sure to send also mobilePaymentMethodSpecificInput.paymentProductId
{ "mobilePaymentMethodSpecificInput":{ "encryptedPaymentData":"{\"signature\":\"MEUCIQCcSASjWu3ax9jQ8qX/+rsNLZ95uiyxamXiKnHlJi8A1QIgZj ...", "paymentProductId":"320" } } - Specify the token as the payment value in encryptedCustomerInput. This input is an encrypted list of key-value pairs, usually containing user input, which is compiled based on the actual input field. The customer's encrypted payment details:
- are encrypted again
- sent to your server
- finally to our server
You must use the client-side Android SDK to create the encrypted CustomerInput value. The fieldId of the encrypted payment data field is returned when Google Pay™ receives payment products through API. Although this field is returned as an input field, you should not provide this field to users.// This example assumes that the SDK is initialized correctly var paymentRequest = session.getPaymentRequest(); paymentRequest.setValue("encryptedPaymentData", "{\"signature\":\"MEUCIG/WtsJnBf6yLsvnD2LOGaVMCO8E93QizIE0foMscVujAi...") var encryptor = session.getEncryptor(); encryptor.encrypt(paymentRequest).then(function(encryptedString) { // Send the encryptedString to your backend. This exact String is the expected value for the // encryptedCustomerInput in the Server-to-server CreatePaymentAPI }, function(errors) { // Inform the consumer that something went wrong });
After you have received the token, send the payment request to our platform. Add the following properties to a standard CreatePayment request:
| Properties | Remarks |
|---|---|
|
mobilePaymentMethodSpecificInput |
paymentProductId: Instructs our platform to target GooglePay. requiresApproval: Processes the transaction as an authorisation or direct sale. encryptedPaymentData: The token you have received in the previous step. |
Find detailed information about this object and its properties in our CreatePaymentAPI.
Make sure to determine the device your customers are using for the payment, as it determines whether you have to roll out 3-D Secure manually.
- Your customers use a desktop/tablet: Handle these kind of transactions like ordinary credit card transactions. Hence, you need to include 3-D Secure properties in your request. Have a look at the code samples for to learn how it works:
Request with 3-D Secure properties using encryptedPaymentData
Request with 3-D Secure properties using encryptedCustomerInput - Your customers use a mobile device. The cards used for these kind of transactions are virtual cards linked to a device-specific account number (DPAN). A digital signature protects these card from fraudulent use, making 3-D Secure unnecessary. Have a look at the code samples for:
Request without 3-D Secure properties using encryptedPaymentData
Request without 3-D Secure properties using encryptedCustomerInput
A typical request looks like this:
Request with 3-D Secure properties using encryptedPaymentData
{
"mobilePaymentMethodSpecificInput": {
"paymentProductId": "320",
"requiresApproval": true,
"encryptedPaymentData": "{"signature":"MEUCIG/WtsJnBf6yLsvnD2LOGaVMCO8E93QizIE0foMscVujAi..."
},
"paymentProduct320SpecificInput": {
"threeDSecure": {
"challengeIndicator": "no-preference",
"challengeCanvasSize": "600x400",
"skipAuthentication": false,
"redirectionData": {
"returnUrl": "https://hostname.myownwebsite.url",
"variant": "100"
}
}
},
"order": {
"amountOfMoney": {
"currencyCode": "EUR",
"amount": 2300
},
"customer": {
"billingAddress": {
"countryCode": "BE"
},
"device": {
"acceptHeader": "texthtml,application/xhtml+xml,application/xml;q=0.9,/;q=0.8",
"browserData": {
"colorDepth": 24,
"javaEnabled": false,
"screenHeight": "1200",
"screenWidth": "1920"
},
"ipAddress": "123.123.123.123",
"locale": "en-US",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1 Safari/605.1.15",
"timezoneOffsetUtcMinutes": "420"
},
"locale": "en_US",
"merchantCustomerId": "your id="" of="" the="" consumer="""
}
}
}
Request with 3-D Secure properties using encryptedCustomerInput
{
"mobilePaymentMethodSpecificInput": {
"paymentProductId": "320",
"requiresApproval": true
},
"paymentProduct320SpecificInput": {
"threeDSecure": {
"challengeIndicator": "no-preference",
"challengeCanvasSize": "600x400",
"skipAuthentication": false,
"redirectionData": {
"returnUrl": "https://hostname.myownwebsite.url",
"variant": "100"
}
}
},
"order": {
"amountOfMoney": {
"currencyCode": "EUR",
"amount": 2300
},
"customer": {
"billingAddress": {
"countryCode": "BE"
},
"device": {
"acceptHeader": "texthtml,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8",
"browserData": {
"colorDepth": 24,
"javaEnabled": false,
"javaScriptEnabled": true,
"screenHeight": "800",
"screenWidth": "360"
},
"ipAddress": "123.123.123.123",
"locale": "en-US",
"userAgent": "Mozilla/5.0 (Linux; Android 10; SM-G980F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.101 Mobile Safari/537.36",
"timezoneOffsetUtcMinutes": "420"
},
"locale": "en_US",
"merchantCustomerId": "your id="" of="" the="" consumer="""
},
"encryptedCustomerInput" : "encrypted string="""
}
}
Request without 3-D Secure properties using encryptedpaymentdata
{
"order" : {
"amountOfMoney" : {
"currencyCode" : "EUR",
"amount" : 2300
},
"customer" : {
"merchantCustomerId": "
",
"billingAddress" : {
"countryCode" : "NL"
}
}
},
"mobilePaymentMethodSpecificInput" : {
"paymentProductId" : 320,
"encryptedPaymentData": "{\"signature\":\"MEUCIQCcSASjWu3ax9jQ8qX/+rsNLZ95uiyxamXiKnHlJi8A1QIgZj ..."
}
}
Request without 3-D Secure properties using encryptedcustomerinput
{
"order" : {
"amountOfMoney" : {
"currencyCode" : "EUR",
"amount" : 2300
},
"customer" : {
"merchantCustomerId": "your id="" of="" the="" consumer=""",
"billingAddress" : {
"countryCode" : "NL"
}
}
},
"encryptedCustomerInput" : "encrypted string="""
}
Google Pay™ in app
We also provide Google Pay™ for native Android applications. Our Android SDK client helps you embed Google Pay™ into your application while we will decrypt sensitive payment information for you.
Once you have followed the Google’s setup guidelines, you are ready to beginfor the technical integration with us. Google offers a very clear and and concise tutorial on how to implement Google Pay™ on your WebsiteWebsite. The technical integration includes the following steps:
- Retrieve Google Pay™
- Comply to Strong Customer Authentication (SCA)
- Render Google Pay™ button
- Get payment token
- Send payment token
1. Retrieve Google Pay™
Google Pay™ might not always be available on all devices. The Android SDK client allows you to easily hide Google Pay™ if this is the case. Our platform will then return null. Use the following code sample to make this call:
// Check availability of Google Pay™
private void getGooglePayPaymentProduct() {
// session is an already initialized instance of the SDK's GcSession object
session.getPaymentProduct(
this, // Instance of Android ApplicationContext
Constants.PAYMENTPRODUCTID_GOOGLEPAY,
paymentContext,
this. // Implementation of OnPaymentProductCallCompleteListener
);
}
/**
* Implementation of the callback method for retrieving a payment product
*/
@Override
public void onPaymentProductCallComplete(PaymentProduct paymentProduct) {
if (paymentProduct != null) {
if (Constants.PAYMENTPRODUCTID_GOOGLEPAY.equals(paymentProduct.getId())) {
// Google Pay™ is available, render the Google Pay™ button.
} else {
// A different product was retrieved..
}
} else {
// Google Pay™ is not available, we should not render it.
}
}
2. Comply to Strong Customer Authentication (SCA)
If your acquirer is from the European Economic Area (EEA) , you must submit the acquiring bank’s country/region information to Google in TransactionInfo.countryCode. his will ensure you comply with SCA requirements.. Google Pay™ will return corresponding transaction data based on the country/region of your acquirer .
The payment product API call from the Client SDK or the Server-to Server returns the acquirerCountry you have to send to Google. The following code shows how to
- obtain the Acquirer Country code from the payment product response and use it to initialise Google Pay™.
- get the result field of the transactionInfo object.
- specify the totalPrice and MerchantName parameters (as described in step 8.3 of the Google Pay™ tutorial and in the Strong Customer Authentication section on Google's documentation site).
Find more information on Strong Customer Authentication compliance for Google Pay™ at the Google Pay™ API documentation and in our dedicated guide.
// Obtain Google Pay™ parameters
private JSONObject initializeGooglePayValues(PaymentContext paymentContext, PaymentProduct googlePayProduct) {
JSONObject paymentRequest = new JSONObject();
try {
// Initialize other payment request values.
JSONObject transactionInfo = new JSONObject();
transactionInfo.put("totalPriceStatus", "FINAL");
String totalPrice = formatAmount(paymentContext.getAmountOfMoney().getAmount().toString());
transactionInfo.put("totalPrice", totalPrice);
transactionInfo.put("currencyCode", paymentContext.getAmountOfMoney().getCurrencyCode().toString());
if (paymentProduct.getAcquirerCountry() != null) {
transactionInfo.put("countryCode", googlePayProduct.getAcquirerCountry());
}
paymentRequest.put("transactionInfo", transactionInfo);
} catch (JSONException e) {
// Something went wrong when generating the JSON payment input.
}
return paymentContext;
}
/**
* Formats the amount used in the Connect platform to the format Google is expecting.
*/
private String formatAmount(String amount) {
String formattedAmount = "00" + amount;
formattedAmount = formattedAmount.substring(0, formattedAmount.length() - 2)
+ "."
+ formattedAmount.substring(formattedAmount.length() - 2);
return formattedAmount;
}
3. Render Google Pay™ button
If Google Pay™ is available, display the Googley Pay button in your app. Make sure to follow Google’s guidelines on displaying the Google Pay™ button and Google's brand policy.
4. Get payment token
To process the actual payment, you need to request the payment token from Google. To do so, use the following code snippet:
/**
* This method extracts the Google Pay™ payment token from the PaymentData object that
* is returned when the user has authorized the payment in the payment sheet.
* @param paymentData The Google Pay™ paymentData object that is returned by the payment sheet.
* @return The payment token as a String in the format that is accepted by the our
* Create Payment API.
*/
private String getGooglePayTokenFromPaymentData(PaymentData paymentData) {
String json = paymentData.toJson();
if (json != null && !json.isEmpty()) {
try {
JSONObject paymentDataJson = new JSONObject(json);
return paymentDataJson
.getJSONObject("paymentMethodData")
.getJSONObject("tokenizationData")
.getString("token");
} catch (JSONException e) {
Log.e(TAG, "Payment Token is not in a valid JSON format");
}
} else {
Log.e(TAG, "Only PaymentData in JSON format is accepted.");
}
return null;
}
5. Send payment token
Extract the token and send it to your server via the Server SDK Create Payment API call. You can provide the token in two ways:
- Send the token in property mobilePaymentMethodSpecificInput.encryptedPaymentData. Make sure to send also mobilePaymentMethodSpecificInput.paymentProductId
{ "mobilePaymentMethodSpecificInput":{ "encryptedPaymentData":"{\"signature\":\"MEUCIQCcSASjWu3ax9jQ8qX/+rsNLZ95uiyxamXiKnHlJi8A1QIgZj ...", "paymentProductId":"320" } } - Specify the token as the payment value in encryptedCustomerInput. This input is an encrypted list of key-value pairs, usually containing user input, which is compiled based on the actual input field. The customer's encrypted payment details:
- are encrypted again
- sent to your server
- finally to our server
You must use the client-side Android SDK to create the encrypted CustomerInput value. The fieldId of the encrypted payment data field is returned when Google Pay™ receives payment products through API. Although this field is returned as an input field, you should not provide this field to users.
Payment request with encrypted CustomerInput
private void createPreparedPaymentRequestGooglePay(String token, PaymentProduct googlePay) {
PaymentRequest paymentRequest = new PaymentRequest();
paymentRequest.setPaymentProduct(googlePay); // This is the Google Pay™ PaymentProduct object, which is the result of the getPaymentProduct call that was done before
if (token != null && !token.isEmpty()) {
paymentRequest.setValue(Constants.GOOGLE_PAY_TOKEN_FIELD_ID, token);
// Prepare the payment request by encrypting the payment values
session.preparePaymentRequest(
paymentRequest,
this, // Instance of Android ApplicationContext
this // Implementation of OnPaymentRequestPreparedListener
);
} else {
// Notify the user that an error has occurred
}
}
/**
* Implementation of the callback for encrypting the payment values
*/
@Override
public void onPaymentRequestPrepared(PreparedPaymentRequest preparedPaymentRequest) {
if (preparedPaymentRequest != null) {
String encryptedFields = preparedPaymentRequest.getEncryptedFields();
// Send the encryptedFields to your backend
} else {
// Something went wrong, notify the user
}
}
Process flows
- Your customers finalse an order in your shop / in your app and select Google Pay™.
- Your server sends a specific Google API call to display a list of supported payment methods in the browser / app.
- Your customers select a payment method.
- Your server requests a payment token from Google.
- You send this CreatePayment request to our platform, containing the payment token in property mobilePaymentMethodSpecificInput.encryptedPaymentData
5'(Optional for payments going through your own checkout page). If your customers use a Non-network tokenised card, you redirect the customers to their issuing bank for 3-D Secure authentication.
5''(Optional for payments going through your own checkout page). Your customers perform the 3-D Secure check. Our system receives the result from the issuer. Based on the result, two scenarios are possible:
a) If the identification was successful, the flow continues at step 6.
b) If the identification was unsuccessful, we redirect your customers to your returnUrl, ending the flow. You can request the transaction result as described in step 8. - Google Pay™ processes the actual financial transaction. We receive the transaction result.
- We redirect your customer to your app / returnUrl
- You request the transaction result from our platform via GetPaymentDetails or receive the result via webhooks.
- If the transaction was successful, you can deliver the goods / services.
Testing
Refer to our Test cases for test data and detailed instructions.
Make sure to use the right endpoint and switch back to the live URL as soon as you have finished your tests.