# 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](/api/transaction/credit-card.md#sale): 1. Endpoint - accepts the parameters as querystring values or application/x-www-form-urlencoded 2. Endpoint - accepts the payload in JSON format | **Field Name** | **Required** | **Description** | | -------------------- | ------------ | -------------------------------------------------------------------------------------------------------------- | | x3dsReferenceId | Yes | This is the ck3DS.referenceId. | | x3dsInitializeStatus | Yes | This is the ck3DS.initializeStatus. | | x3dsError | No | This is the ck3DS.error | | xBillFirstName | Yes | | | xBillLastName | Yes | | | xBillStreet | Yes | | | xBillCity | Yes | | | xBillState | Yes | ISO state or province code in 2-digit alpha format. | | xBillZip | Yes | | | xBillCountry | Recommended | ISO country code in 2- or 3- digit alpha format. This will default to US if an unsupported value is submitted. | | xBillMobile | Yes | | | xBillPhone | Recommended | This will default to the value submitted in xBillMobile if not submitted. | | xEmail | Yes | | | xShipFirstName | Recommended | | | xShipLastName | Recommended | | | xShipStreet | Recommended | | | xShipCity | Recommended | | | xShipState | Recommended | ISO state or province code in 2-digit alpha format. | | xShipZip | Recommended | | | xShipCountry | Recommended | ISO country code in 2- or 3- digit alpha format. This will default to US if an unsupported value is submitted. | Possible xStatus responses: * Approved/Declined/Error * The transaction is complete and no further action is necessary. Jump to [3ds response fields](#response-fields). 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 1. \[Conditional: If previous step returned xStatusofVerify] Submit verification request to complete the 3DS authentication and process the payment with the bank. In addition to [standard required fields for cc:sale and cc:authonly](/api/transaction/credit-card.md#sale), the following fields may be required: a. Endpoint - accepts the parameters as query string values or application/x-www-form-URL encoded b. Endpoint - accepts the payload in JSON format | **Field Name** | **Required** | **Description** | | ------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | | x3dsActionCode | Yes | This is the action code passed as the first parameter to ck3DS.configuration.onVerifyComplete. | | xVersion | Yes | Cardknox version (current version is 5.0.0) | | xCavv | Conditional | Required if x3dsActionCode=SUCCESS. This is the cavv passed as the second parameter to ck3DS.configuration.onVerifyComplete. | | xEci | Conditional | Required if x3dsActionCode=SUCCESS. This is the eci flag passed as the third parameter tock3DS.configuration.onVerifyComplete. | | xRefnum | Yes | This is the cardknox xRefNum passed as the fourth parameter tock3DS.configuration.onVerifyComplete. | | x3dsAuthenticationStatus | Conditional | Required if x3dsActionCode=SUCCESS. This is the authenticate status passed as the fifth parameter tock3DS.configuration.onVerifyComplete. | | x3dsSignatureVerificationStatus | Conditional | Required if x3dsActionCode=SUCCESS. This is the signature verification passed as the sixth parameter tock3DS.configuration.onVerifyComplete. | | x3dsError | No | This is the ck3DS.error and will contain additional info in case of any errors. | The transaction response xStatus will be Approved or Declined, and the payment is now complete. [3ds response fields](#response-fields) below. #### Response fields Present on a completed cc:sale / cc:authonly. | **Field Name** | **Description** | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | xReviewed |

Y: Transaction was authenticated by 3ds. If authentication was submitted to the bank, the merchant will have fraud chargeback protection.

N: Transaction was not able to achieve 3ds authentication. The merchant will not have 3ds fraud chargeback protection.

F: The 3ds authentication process completed but the bank response indicated that the results were invalid. The merchant will not have fraud chargeback protection.

| | x3dsSubmitted | This will be “1” if the bank request included 3ds data elements. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.solapayments.com/products/3d-secure/server-side-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.