WL SIPS DOCS

Here are the rules applied to the Google Pay™ means of payment:

2 authentication methods are available :

• CRYPTOGRAM_3DS : The Google Pay API will return a device token on an Android-powered device authenticated with a 3-D Secure cryptogram .
• PAN_ONLY : The Google Pay API will return cards on file on Google.com.

All anti-fraud checks are supported under the Google Pay™ means of payment payments (fraud tool).

To define the Google Pay payment logo on your payment page, you'll have to follow the Google Pay™ brand guideline available here : https://developers.google.com/pay/api/web/guides/brand-guidelines

Depending on the authentication method selected by the customer (CRYPTOGRAM_3DS or PAN_ONLY, the authentication could be handled by Google Pay™ or the issuer's bank

Regardless of the authentication method selected, once the customer validate its payment with Google Pay™, then Google will cyphered the payment data with our key. You'll have to send this data to us using paymentDataProviderCheck function, in order to decypher and check the payment data.

Then you'll get 2 options :

• In "CRYPTOGRAM_3DS" authentication method : The customer use a payment card enrolled in its Google Wallet and authenticate its payment on a Android-powered device. Then the authentication is handled by Google and we'll send you in response a DPAN (Device Payment Account Number), the card expiry date,a CAVV/TAVV (3-D secure cryptogram) and an ECI indicator. You should use these data to call the cardOrder function in order to process authorisation.

• In "PAN_ONLY" authentication method : The customer use a payment card registered in its Google account, then he'll have to authenticate itself to the issuer of its payment card selected. In this case, you get in response a paymentToken Sips (card PAN tokenized) and the card expiryDate. Tou should use these data to call the cardCheckEnrollment function, then we'll send you the ACS redirection URL in order to request a customer authentication, and to finalize you should call the cardValidateAuthenticationAndOrder function to process the authorisation.

The maximum capture delay allowed for an the Google Pay™ means of payment payment is 6 days.

If you enter a longer capture delay, it will be automatically forced by the payment platform.

Payments are remitted to a bank according to the payment terms you set. As standard, the remittance in bank is triggered at night as from 10 pm CET (Central European Time) via a file exchange with the acquirer.

This model is applicable with a device token on an Android-powered device authenticated with a 3-D Secure cryptogram Google Pay™

This model is applicable with a card on file returned from Google.com

To process a Google Pay™ payment with Sips Office, vous first have to integrate in your checkout page the the Google Pay™ means of payment button and and configure it. Then the Google Pay™ means of payment will create a secured paytment token that you'll have to send us in order to decipher it with paymentDataProviderCheck.

The following fields must be set :

{
  "protocolVersion": "ECv2",
  "signature": "MEQCIH6Q4OwQ0jAceFEkGF0JID6sJNXxOEi4r+mA7biRxqBQAiAondqoUpU/bdsrAOpZIsrHQS9nwiiNwOrr24RyPeHA0Q==",
  "intermediateSigningKey": {
    "signedKey": "{\"keyExpiration\":\"1542323393147\",\"keyValue\":\"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE/1+3HBVSbdv+j7NaArdgMyoSAM43yRydzqdg1TxodSzA96Dj4Mc1EiKroxxunavVIvdxGnJeFViTzFvzFRxyCw\\u003d\\u003d\"}",
    "signatures": [
      "MEYCIQCO2EIi48s8VTH+ilMEpoXLFfkxAwHjfPSCVED/QDSHmQIhALLJmrUlNAY8hDQRV/y1iKZGsWpeNmIP+z+tCQHQxP0v"
    ]
  },
  "signedMessage": "{\"tag\":\"jpGz1F1Bcoi/fCNxI9n7Qrsw7i7KHrGtTf3NrRclt+U\\u003d\",\"ephemeralPublicKey\":\"BJatyFvFPPD21l8/uLP46Ta1hsKHndf8Z+tAgk+DEPQgYTkhHy19cF3h/bXs0tWTmZtnNm+vlVrKbRU9K8+7cZs\\u003d\",\"encryptedMessage\":\"mKOoXwi8OavZ\"}"
}

All possible response status :

The following fields are set in order to decypher the Google Pay™ payment token.

authenticationResult field (only for CRYPTOGRAM_3DS) is a container with the following fiels inside.

To make a payment with Sips Office, you must use cardOrder function.

The Google Pay payment request includes all mandatory fields of the connector you are using.

The following fields have a particular behaviour:

The following table summarises the different response cases to be processed:

For the complete response codes (responseCode) and acquirer response codes (acquirerResponseCode), please refer to the Data dictionary.

You use the 3-D Secure enrollment of the card using the cardCheckEnrollment.

The the Google Pay™ means of payment payment request includes all mandatory fields of the connector you are using.

The following fields have a particular behaviour in the PAN_ONLY kinematic :

When you receive the response, before analyzing it and following the advice in the table below, check the seal. The recalculated seal must be identical to the seal received.

Please refer to the paragraph relating to the redirection to the ACS of the Sips Office documentation to know how to implement this message.

Please refer to the paragraph back from the ACS of the Sips Office JSON documentation to know how to implement this message.

Please refer to the paragraph 3-D Secure authorisation request of the Sips Office JSON documentation to know how to implement this message.