Google Pay™ API V1

Introduction

There are several implementation options for Google Pay™ that support both CRYPTOGRAM_3DS and PAN_ONLY authentication methods.

How to integrate with Google Pay™ API

Integrate your Android app or website with the Google Pay™ API via Google Pay™ & Wallet Console: Google Pay™ API & Google Pay™ & Wallet Console. For full developer documentation, see the Google Pay™ Web developer documentation. Before publishing your integration, review the Google Pay™ web brand guidelines.

On step 4, when completing the tutorial, specify tokenization type PAYMENT_GATEWAY:

copyconst tokenizationSpecification = {
  type: 'PAYMENT_GATEWAY',
  parameters: {
    'gateway': 'kkbpay',
    'gatewayMerchantId': 'YOUR_GATEWAY_MERCHANT_ID'
  }
};

• gateway = kkbpay
• gatewayMerchantId = YOUR_GATEWAY_MERCHANT_ID (merchant login in the payment gateway)

After integration you will be assigned a Google Merchant ID displayed in the top-right corner of the Google Pay & Wallet Console.

Integration schemes

Payment from a mobile app

1. A customer selects to pay via Google Pay™.
2. The application requests masked card data from Google Pay™.
3. Google Pay™ returns masked card data to the application.
4. The application displays the masked card data to the customer.
5. The customer confirms payment.
6. The application requests encrypted card data from Google Pay™.
7. Google Pay™ encrypts the data using the merchant's public key.
8. Google Pay™ returns the encrypted payment data to the application.
9. The application sends a Google Pay™ payment request to the payment gateway containing the token from Google Pay™.
10. The payment gateway decrypts the received token and processes the payment.
11. The payment gateway returns the payment result to the application.
12. The application displays the payment result to the customer.

Payment page on the online store side

1. The customer creates an order and chooses to pay via Google Pay™.
2. The online store generates a request for Google Pay™.
3. Google Pay™ generates the encrypted payment data.
4. The online store receives the encrypted payment data.
5. The online store sends a Google Pay™ payment request with the encrypted data.
6. The payment gateway decrypts the data and makes the payment.
7. The payment gateway returns the payment result to the online store.
8. The payment result is displayed to the customer.

Payment page on the payment gateway side

1. A customer creates an order on the merchant's website.
2. The merchant registers the order in the payment gateway: One-phase payment or Two-phase payment.
3. The payment gateway returns a unique order number and redirect URL.
4. The store redirects the customer.
5. The customer's browser opens the URL.
6. The customer receives the payment form.
7. The customer selects Google Pay™ and confirms.
8. Payment data is exchanged between the payment gateway and Google Pay™.
9. The payment gateway processes the payment.
10. The customer is redirected to the final page.
11. The final page is opened.
12. The payment status is displayed.

Payment via Google Pay™ using 3DS2

This section describes how to make a 3DS2 payment from a merchant's own payment page (not via the hosted payment page).

3DS2 flow description

1. Register the order in EPG via register.do.
2. Collect card info at the merchant's payment page.
3. Call processform.do or paymentorder.do. Either request will send the entered PAN to EPG. If the card is eligible for 3DS2, the call will not finish until the 3DS Server collects cardholder browser information. If the 3DS Server is unable to collect browser information, the call will finish unsuccessfully.
4. Here starts the magic — this is what the hosted payment page actually does.
5. In a separate thread (in parallel) — call EPG check API epg/api/v1/3ds2/inner/check. This API checks if the PAN is eligible for 3DS2 (EPG calls the 3DS Server):
   1. If completed = false, repeat the call after some time (e.g. 0.5 seconds).
   2. If is3Ds2Eligible = false, end the parallel process — processform.do or paymentorder.do will proceed.
   3. This step may be omitted but is highly recommended. If threeDSMethodURL is present and not blank, open an iframe on the payment page. In that iframe add a form with a single parameter threeDSMethodData and fill it with the value from threeDSMethodDataPacked. Submit the form to threeDSMethodURL. The form will call the appropriate API of the issuer's ACS — leave the iframe as-is, you do not need to monitor when it finishes.
      
      If this step is omitted, the 3DS Server will wait ~10 seconds for ThreeDS Method completion notification from the ACS and will send threeDSCompInd = N in AReq.
   4. Collect cardholder browser info and pass it to the 3DS Server. Two options exist:
      1. Preferred: Create a second iframe, add an empty form and submit it to threeDSMethodURLServer (calls the Browser data collection API of the 3DS Server). The 3DS Server will respond with HTML containing JavaScript that collects the required information and submits it automatically. You do not need to monitor when it finishes.
      2. Alternative: Collect cardholder browser information on your own and call the Browser data transfer request directly.
   5. Now the 3DS Server should have received the required cardholder browser information and can proceed with sending AReq to the Directory Server.
6. The call to processform.do or paymentorder.do should finish and the response should be processed according to the EPG API specification.

Description of the 'check' API

URL: epg/api/v1/3ds2/inner/check
Request parameter: mdOrder (from register.do)

Response (JSON) — some extra fields may be present; the parsing software must ignore them without errors:

Why so difficult

When processform.do or paymentorder.do is called, EPG calls the 3DS Server to check whether the card is eligible for 3DS2 (at this point the 3DS Server generates threeDSServerTransID). If the card is eligible, EPG calls the 3DS Server to perform authentication (make AReq), but to do so the 3DS Server needs cardholder browser information. It waits until it receives this information for the threeDSServerTransID. If it receives it within the configured period, it makes the AReq request and sends it to the Directory Server. If it does not receive the information, it is unable to make the request and responds with an unsuccessful response to EPG.

3DS2 flow diagrams

The workflows described above are shown in the schemes below.

Browser-based frictionless flow

Browser-based challenge flow

Requirements for the payment page on merchant's side

The payment page on the merchant's side must meet the following requirements.

• Must be able to redirect to 3-D Secure server if the decrypted token contains payment method CARD.
• Must contain the Google Pay™ button.
• Must contain a script that checks whether the Google Pay™ button can be displayed:

copypaymentsClient.isReadyToPay({allowedPaymentMethods: allowedPaymentMethods})
    .then(function(response) {
      if (response.result) {
        addGooglePayButton();
      }
    })
    .catch(function(err) {
      console.error(err);
    });

function addGooglePayButton() {
  var button = document.createElement('button');
  button.className = 'google-pay';
  button.appendChild(document.createTextNode('Google Pay'));
  button.addEventListener('click', onGooglePaymentButtonClicked);
  document.getElementById('container').appendChild(button);
}

• Google JavaScript must be enabled:
  • Integration checklist
  • https://payments.developers.google.com/js/apis/pay.js
• For testing, the environment must be TEST:

copyvar paymentsClient =
    new google.payments.api.PaymentsClient({environment: 'TEST'});

• Must contain a paymentDataRequest object. Use the following test values:
  • gateway — kkbpay
  • gatewayMerchantId — as provided during sandbox on-boarding

copyfunction getGooglePaymentDataConfiguration() {
  return {
    merchantId: '00000000000000000000', // for environment 'TEST' — not required
    transactionInfo: {
        totalPriceStatus: 'FINAL',
        totalPrice: '123.45',    // amount in major units
        currencyCode: 'EUR'      // ISO 4217
    },
    paymentMethodTokenizationParameters: {
        tokenizationType: 'PAYMENT_GATEWAY',
        parameters: {
            gateway: 'kkbpay',
            gatewayMerchantId: 'YOUR_GATEWAY_MERCHANT_ID'
        }
    },
    allowedPaymentMethods: ['CARD', 'TOKENIZED_CARD'],
    cardRequirements: {
        allowedCardNetworks: ['MASTERCARD', 'VISA']
    }
  };
}

• After clicking the Google Pay™ button, pass paymentDataRequest to Google Pay™:

copyvar paymentDataRequest = getGooglePaymentDataConfiguration();
paymentsClient.loadPaymentData(paymentDataRequest).then(function(paymentData){
  processPayment(paymentData);
}).catch(function(err){
  console.error(err);
});

• The value for the main version of the page must be obtained from Google after performing checks: integration checklist.

Using individual keys

For direct integration with Google Pay™ without using Kyrgyzkommertsbank as payment provider, generate an individual key pair via the Merchant Portal and upload it to your Google account.

Create key pair

1. Log in to your personal area and open the Certificates section.
2. Go to the Google Pay™ tab.
3. Click Create key pair.
4. Fill in the Google ID field with your Google Merchant ID (from Google API integration), then click Confirm.
5. The created key pair will appear in the keys list.

Download public key

1. Open the Certificates section → Google Pay™ tab.
2. Click the actions menu next to your certificate and select Download key.
3. Save the file to your desired location.

Edit Google ID

1. Open the Certificates section → Google Pay™.
2. Click the actions menu and select Edit.
3. Update the Google ID field, then click Confirm.

Disable certificate

1. Open the Certificates section.
2. Select the required payment service (Apple Pay, Google Pay™, or Samsung Pay).
3. Click the actions menu and select Disable key, then click Confirm.

Payment Provider API

This section describes the REST API methods for processing Google Pay™ payments. Merchants can submit payments directly to the EPG from their own checkout page, or integrate via the EPG hosted payment page.

Order registration request

Depending on whether one-phase or two-phase payments are used, one of the following methods is used to register an order:

• register.do — for one-phase payments
• registerPreAuth.do — for two-phase payments

These requests are designed to register orders in the SmartVista E-Commerce Payment Gateway and have the same set of parameters.

Request parameters

Transaction Data block

A single signed data block used to transfer all original transaction data fields to and from a PCI DSS merchant, instead of multiple separate fields. An RSA key pair with CertificateType.TRANSACTION_DATA_SIGNATURE must be generated for the merchant.

Response parameters

Error codes

Request example

copyhttp://<host:port>/payment/rest/register.do?userName=apiuser&password=apiuserpassword&orderNumber=26122017090900&amount=888¤cy=978&returnUrl=http://www.return.url.com

Example of the orderBundle parameter

copy"orderBundle": {
  "cartItems": {
    "items": [
      {
        "name": "item1",
        "positionId": 1,
        "quantity": { "value": 2.0, "measure": "quantity" },
        "itemAmount": 3025,
        "itemCode": "code1"
      },
      {
        "name": "item2",
        "positionId": 2,
        "quantity": { "value": 2.0, "measure": "quantity" },
        "itemAmount": 3025,
        "itemCode": "code2"
      }
    ]
  }
}

Response example

copy{"orderId":"5f9adf5a-4796-4668-9285-07adf3c9a1aa","formUrl":"http://10.7.32.60/payment/merchants/Merchant/payment_en.html?mdOrder=5f9adf5a-4796-4668-9285-07adf3c9a1aa"}

Merchant-side Google Pay™ implementation: payment APIs

Merchants can use Google Pay™ directly on their own checkout page and submit the payment to EPG. The following requests are supported:

• Payment request (paymentorder.do)
• Request for Google Pay™ payment with decrypted data
• Request for Google Pay™ payment with an encrypted token as JSON
• Request for Google Pay™ Payment with Base64-encoded encrypted token

Payment request

The paymentorder.do method is used for a payment request. The payment card data is validated in accordance with the table below. Only POST requests are supported.

Request parameters

Response parameters

Parameters of the additionalResponseCodes block

Transaction Data block

A single signed data block used to transfer all original transaction data fields to and from a PCI DSS merchant. An RSA key pair with CertificateType.TRANSACTION_DATA_SIGNATURE must be generated for the merchant.

Error codes

orderStatusCode values

Request example

copyhttp://<host:port>/payment/rest/paymentorder.do?userName=apiuser&password=apiuserpassword&MDORDER=aca0f48d-9e99-4437-9335-a50a42c363da&$PAN=4000010000000050&$CVC=123&YYYY=2020&MM=06&TEXT=Card Holder&language=EN

Response example — no additional ACS authentication required

copy{"redirect":"https://example.com/epg/merchants/root/finish.html?orderId=ffd85ad3-1851-430f-99da-a78ecd228d4d&lang=en&status=payment_deposited","info":"Your order is proceeded, redirecting...","errorCode":0,"orderStatusCode":2,"orderStatusName":"payment_deposited"}

Response example — 3DS payment requiring ACS authentication

copy{"info":"Your order is proceeded, redirecting...","acsUrl":"http://10.7.32.60:6001/acs/pareq","paReq":"eJxVUdFy...","termUrl":"http://10.7.32.60/payment/rest/finish3ds.do","errorCode":0}

Request for Google Pay™ payment with decrypted data

The /api/v1/googlepay/payment/decrypted method is used to process Google Pay™ payments using decrypted payment data (cleartext PAN) so that EPG could pass this data to SVFE as is (without decryption).

This request is authenticated with the userName and password parameters that must be transferred.

Request parameters

The request includes common digital wallet request parameters and the parameters described below.

Parameters of the paymentData block

Response parameters

Format of the data block

Request example (PAN only)

copyhttp://<host:port>/epg/api/v1/googlepay/payment/decrypted?userName={user}&password={password}
{
  "merchant": "5010000",
  "mdOrder": "f903e52a-54ca-4c9f-aa57-732333710bdf",
  "additionalParameters": {
    "paramName": "paramValue"
  },
  "description": "desc",
  "paymentData": {
    "gatewayMerchantId": "510000",
    "paymentMethod": "CARD",
    "paymentMethodDetails": {
      "authMethod": "PAN_ONLY",
      "pan": "4000010000000001",
      "expirationMonth": 7,
      "expirationYear": 2029
    },
    "messageId": "some-message-id",
    "messageExpiration": "1577862"
  },
  "language": "en",
  "preAuth": true,
  "currencyCode": "840",
  "amount": 70,
  "ip": "127.0.0.1",
  "customerBillingAddress": {
    "billAddrCity": "billAddrCity value"
  }
}

Request example (Cryptogram 3DS)

copyhttp://<host:port>/epg/api/v1/googlepay/payment/decrypted?userName=api&password=1
{
  "orderNumber": "2020122adaddw31666340992",
  "merchant": "testapi",
  "additionalParameters": { "DE22": "100" },
  "description": "uuu",
  "paymentData": {
    "gatewayMerchantId": "192543",
    "messageExpiration": "1671193200719",
    "messageId": "some-message-id",
    "paymentMethod": "CARD",
    "paymentMethodDetails": {
      "expirationYear": 2049,
      "expirationMonth": 12,
      "pan": "4000010000000001",
      "authMethod": "CRYPTOGRAM_3DS",
      "eciIndicator": "07",
      "cryptogram": "/wABCDEFLc6CgzairNjvQVcABCD="
    },
    "language": "ru",
    "preAuth": false,
    "currencyCode": "840",
    "amount": 6050,
    "ip": "127.0.0.1",
    "returnUrl": "https://example.com/"
  }
}

Response example (success)

copy{
  "orderStatus": {
    "errorCode": "0",
    "errorMessage": "Success",
    "orderNumber": "2020122adaddw31666340992",
    "amount": 6050,
    "currency": "840",
    "date": 1610359322132,
    "ip": "127.0.0.1",
    "merchantOrderParams": [{ "name": "DE22", "value": "100" }],
    "attributes": [{ "name": "mdOrder", "value": "fee466e1-03d3-400f-9a0e-93f607495f73" }],
    "cardAuthInfo": {
      "expiration": "202107",
      "secureAuthInfo": { "eci": 7 },
      "pan": "400001**0050"
    }
  }
}

Response example (error)

copy{
  "errorCode": 1,
  "errorMessage": "Order number is duplicated, order with given order number is processed already",
  "success": false,
  "error": {
    "code": "1",
    "description": "Order number is duplicated, order with given order number is processed already",
    "message": "Order number is duplicated, order with given order number is processed already"
  }
}

Request for Google Pay™ payment with an encrypted token as JSON

A Google Pay™ transaction that uses encrypted payment data (DPAN) transfers a token (paymentToken) to EPG. The payment token is a JSON structure that contains Google Pay™ keys (intermediateSigningKey[], signedMessage) and an encrypted token (PAN/DPAN, and other). Once EPG receives the /api/v1/googlepay/payment/encrypted request, it decrypts the token using private keys.

The request is authenticated — userName and password parameters are required.

Request parameters

The request includes common digital wallet request parameters and the parameters described below.

Response parameters

Request example

copy{
  "merchant": "test_merchant",
  "paymentToken": {
    "signature": "MEUCIAbnHry...",
    "intermediateSigningKey": {
      "signedKey": "{"keyValue":"MFkwEwYH...","keyExpiration":"1622102613707"}",
      "signatures": ["MEUCIFXynvg4S+Qc7Obb..."]
    },
    "protocolVersion": "ECv2",
    "signedMessage": "{"encryptedMessage":"e0GX3ccb...","ephemeralPublicKey":"BBYkGq...","tag":"3cChnP..."}"
  }
}

Response example (success)

copy{
  "redirect": "http://localhost:7013/epg/merchants/testapi/finish.html?orderId=da2b2991-c2f3-43f1-966f-c674a9a75b73&lang=en&status=payment_deposited",
  "info": "Your order is proceeded, redirecting...",
  "errorCode": 0,
  "lookup": false,
  "orderStatus": {
    "errorCode": "0",
    "errorMessage": "Success",
    "orderNumber": "adawdawdawd2adawd5428834",
    "orderStatus": 2,
    "actionCode": 0,
    "actionCodeDescription": "No error",
    "amount": 6050,
    "currency": "840",
    "date": 1609940764499,
    "cardAuthInfo": {
      "expiration": "202812",
      "authorizationResponseId": "123456",
      "secureAuthInfo": { "eci": 7 },
      "pan": "521424**0000"
    }
  },
  "success": true,
  "data": { "orderId": "da2b2991-c2f3-43f1-966f-c674a9a75b73" }
}

Response example (error)

copy{
  "errorCode": 10,
  "errorMessage": "Signature verification offline failed: signing key is missing.",
  "success": false,
  "error": {
    "code": "10",
    "description": "Signature verification offline failed: signing key is missing.",
    "message": "Signature verification offline failed: signing key is missing."
  }
}

Request for Google Pay™ Payment with Base64-encoded encrypted token

The /api/v1/googlepay/encodedtoken/encrypted request is used to process payments using a Google-signed and encrypted payment method token in Base-64 encoding. EPG verifies and decrypts the token.

Request parameters

The request includes common digital wallet request parameters and the parameters described below.

Response parameters

Request example

copy/api/v1/googlepay/payment/encodedtoken/encrypted?userName={user}&password={password}
{
  "merchant": "m01",
  "mdOrder": "6d68883a-df01-42ec-b4ef-245e21287547",
  "description": "desc",
  "paymentToken": "ew0KICAgICJzaWduYXR1cmUiOiAiTUVZQ0...",
  "language": "EN",
  "preAuth": true,
  "currencyCode": "840",
  "amount": 190,
  "ip": "127.0.0.1"
}

Response example (success)

copy{
  "redirect": "http://localhost:7013/epg/merchants/testapi/finish.html?orderId=da2b2991-c2f3-43f1-966f-c674a9a75b73&lang=en&status=payment_deposited",
  "info": "Your order is proceeded, redirecting...",
  "errorCode": 0,
  "success": true,
  "data": { "orderId": "da2b2991-c2f3-43f1-966f-c674a9a75b73" }
}

EPG-side Google Pay™ integration: payment APIs

Merchants can be integrated with Google Pay™ via EPG using the hosted payment page. The following requests are supported:

• Request for Google Pay™ payment with encrypted token as JSON via hosted payment page
• Request for Google Pay™ payment with Base64-encoded encrypted token via hosted payment page

Request for Google Pay™ payment with encrypted token as JSON via hosted payment page

The /api/v1/googlepay/payment/encrypted-anonymous request is used to process payments using a Google-signed and encrypted payment method token. The paymentToken is passed as a JSON containing Google Pay™ keys (intermediateSigningKey[], signedMessage) and an encrypted token (PAN/DPAN). EPG decrypts it using private keys.

Request parameters

The request includes common digital wallet request parameters and the parameters described below.

Response parameters

Request example

copy/api/v1/googlepay/payment/encrypted-anonymous
{
  "merchant": "m01",
  "mdOrder": "6d68883a-df01-42ec-b4ef-245e21287547",
  "paymentToken": {
    "signature": "MEUCIAbnHry...",
    "intermediateSigningKey": {
      "signedKey": "{"keyValue":"MFkwEwYH...","keyExpiration":"1622102613707"}",
      "signatures": ["MEUCIFXynvg4S+Qc7Obb..."]
    },
    "protocolVersion": "ECv2",
    "signedMessage": "{"encryptedMessage":"e0GX3ccb...","ephemeralPublicKey":"BBYkGq...","tag":"3cChnP..."}"
  }
}

Response example (success)

copy{
  "redirect": "http://localhost:7013/epg/merchants/testapi/finish.html?orderId=da2b2991-c2f3-43f1-966f-c674a9a75b73&lang=en&status=payment_deposited",
  "info": "Your order is proceeded, redirecting...",
  "errorCode": 0,
  "lookup": false,
  "orderStatus": {
    "errorCode": "0",
    "errorMessage": "Success",
    "orderNumber": "adawdawdawd2adawd5428834",
    "orderStatus": 2,
    "actionCode": 0,
    "amount": 6050,
    "currency": "840",
    "cardAuthInfo": {
      "expiration": "202812",
      "secureAuthInfo": { "eci": 7 },
      "pan": "521424**0000"
    }
  },
  "success": true,
  "data": { "orderId": "da2b2991-c2f3-43f1-966f-c674a9a75b73" }
}

Response example (error)

copy{
  "errorCode": 10,
  "errorMessage": "Signature verification offline failed: signing key is missing.",
  "success": false,
  "error": {
    "code": "10",
    "description": "Signature verification offline failed: signing key is missing.",
    "message": "Signature verification offline failed: signing key is missing."
  }
}

Request for Google Pay™ payment with Base64-encoded encrypted token via hosted payment page

The api/v1/googlepay/payment/encodedtoken/encrypted-anonymous request is used to process payments using a Google-signed and encrypted payment method token in Base-64 encoding via the EPG hosted payment page.

Request parameters

The request includes common digital wallet request parameters and the parameters described below.

Response parameters

Request example

copyhttp://<host:port>/epg/api/v1/googlepay/payment/encodedtoken/encrypted-anonymous
{
  "merchant": "m01",
  "mdOrder": "6d68883a-df01-42ec-b4ef-245e21287547",
  "description": "desc",
  "paymentToken": "ew0KICAgICJzaWduYXR1cmUiOiAiTUVZQ0...",
  "language": "EN",
  "preAuth": true,
  "currencyCode": "840",
  "amount": 190,
  "ip": "127.0.0.1"
}

Response example (success)

copy{
  "redirect": "http://localhost:7013/epg/merchants/testapi/finish.html?orderId=da2b2991-c2f3-43f1-966f-c674a9a75b73&lang=en&status=payment_deposited",
  "info": "Your order is proceeded, redirecting...",
  "errorCode": 0,
  "success": true,
  "data": { "orderId": "da2b2991-c2f3-43f1-966f-c674a9a75b73" }
}

Response example (error)

copy{
  "errorCode": 10,
  "errorMessage": "Signature verification offline failed: signing key is missing.",
  "success": false
}

Merchant-side Google Pay™ implementation: non-payment APIs

The following APIs are provided to decrypt payment token data without initiating a payment request for authorization to SVFE:

• Request for Google Pay™ data decryption from encrypted token as JSON
• Request for Google Pay™ data decryption from Base64 encoded encrypted token

Request for Google Pay™ data decryption from encrypted token as JSON

This request contains the Google-signed and encrypted payment method token. This API endpoint is designed to decrypt the payment token to retrieve the underlying payment data. To initiate the request, the /api/v1/googlepay/token/decrypt method is used.

Request parameters

Response parameters

Format of the paymentData block

Request example

copyhttp://<host:port>/epg/api/v1/googlepay/token/decrypt
{
  "merchant": "testapi",
  "paymentToken": "ew0KICAgICJzaWduYXR1cmUiOiAiTUVZQ0..."
}

Response example (success)

copy{
  "errorCode": 0,
  "paymentData": {
    "gatewayMerchantId": "500000",
    "paymentMethod": "CARD",
    "paymentMethodDetails": {
      "authMethod": "PAN_ONLY",
      "pan": "4000010000000050",
      "expirationMonth": 7,
      "expirationYear": 2021
    },
    "messageId": "some-message-id",
    "messageExpiration": "1577862000000"
  }
}

Response example (error)

copy{
  "errorCode": 10,
  "errorMessage": "Signature verification offline failed: signing key is missing.",
  "success": false,
  "error": {
    "code": "10",
    "description": "Signature verification offline failed: signing key is missing.",
    "message": "Signature verification offline failed: signing key is missing."
  }
}

Request for Google Pay™ data decryption from Base64 encoded encrypted token

The /api/v1/googlepay/encodedtoken/decrypt method is used to decrypt Google Pay™ payment data passed to EPG as a Base64 encoded string which contains the payment token object. EPG does not transfer the transaction for authorization to SVFE. The request contains a payment token object (a Base64-encoded serialized JSON object). EPG decodes the payment data and returns a response with the decrypted payment data (see Non-tokenized card in Google documentation).

The request is not authenticated. The merchant login (merchant) is used to perform all the checks.

Request parameters

Response parameters

Request example

copy{"merchant": "m01",
"paymentToken": "ew0KICAgICJzaWduYXR1cmUiOiAiTUVZQ0..."
}

Response example (success)

copy{
  "errorCode": 0,
  "paymentData": {
    "gatewayMerchantId": "500000",
    "paymentMethod": "CARD",
    "paymentMethodDetails": {
      "authMethod": "PAN_ONLY",
      "pan": "4000010000000050",
      "expirationMonth": 7,
      "expirationYear": 2021
    },
    "messageId": "some-message-id",
    "messageExpiration": "1577862000000"
  }
}

Response example (error)

copy{
  "errorCode": 10,
  "errorMessage": "Signature verification offline failed: signing key is missing.",
  "success": false,
  "error": {
    "code": "10",
    "description": "Signature verification offline failed: signing key is missing.",
    "message": "Signature verification offline failed: signing key is missing."
  }
}