SCA and Google Pay API

Strong Customer Authentication

To enable Google Pay to return appropriate payment credentials for transactions subject to SCA, you might need to make a few minor updates to your implementation.

If you’ve completed a Google Pay API V2 integration, the following changes are required.

Update your PaymentDataRequest object

Update your PaymentDataRequest object with the following properties:

Updated PaymentDataRequest object example

The following is an example of an updated PaymentDataRequest object:

  "apiVersion": 2,
  "apiVersionMinor": 0,
  "merchantInfo": {
    "merchantName": "Example Merchant"
  "allowedPaymentMethods": [
      "type": "CARD",
      "parameters": {
        "allowedAuthMethods": ["PAN_ONLY", "CRYPTOGRAM_3DS"],
        "allowedCardNetworks": ["AMEX", "DISCOVER", "INTERAC", "JCB", "MASTERCARD", "VISA"]
      "tokenizationSpecification": {
        "type": "PAYMENT_GATEWAY",
        "parameters": {
          "gateway": "example",
          "gatewayMerchantId": "exampleGatewayMerchantId"
  "transactionInfo": {
    "totalPriceStatus": "FINAL",
    "totalPrice": "12.34",
    "countryCode": "GB",
    "currencyCode": "GBP"

Handle the response object

Merchants receive one of the following:

  • An authenticated payload that can be processed without any further step-up or challenge.
  • A PAN that requires 3D Secure 2.0 through an in-house or a PSP-provided solution.