Server-Side Integration

Transaction Components

  1. Submit a payment transaction on an account that has 3DS 2.x enabled. See the following request fields in addition to standard required fields for cc:sale and cc:authonly:

    1. Endpoint https://x1.cardknox.com/gateway - accepts the parameters as querystring values or application/x-www-form-urlencoded

    2. Endpoint https://x1.cardknox.com/gatewayJSON - accepts the payload in JSON format

Possible xStatus Responses

  • Approved/Declined/Error

To configure behavior on non-authenticated 3DS responses, contact Support.

  • Verify

    • Pass the response object to the client. (The client will call ck3DS.verifyTrans with the response as a parameter to continue the 3DS authentication.)

    • This transaction response contains the 3DS fields necessary for the website to complete the authentication: xVerifyURL, xVerifyPayload, xInternalID, xRefnum, x3dsActionCode

2. [Conditional: If the previous step returned xStatusofVerify] Submit a verification request to https://x1.cardknox.com/verify to complete the 3DS authentication and process the payment with the bank. In addition to the standard required fields for cc:sale and cc:authonly, the following fields may be required:

The transaction response xStatus will be Approved or Declined, and the payment is now complete. 3DS Response Fields below.

Response Fields

Present on a completed cc:sale/cc:authonly

Last updated