HTTP response status codes

This page lists the common HTTP response status codes that are returned when an incorrect request is sent to the 3DS Server.

Status code: 401

Possible error scenario

Authentication failed. For example, API key is missing or incorrect in the request header or the request authentication credentials are invalid.

Proposed solution

Validate that the API Key is the one you received at the time of boarding or the username and password is correct. Authentication sample request and response

Status code: 403

Possible error scenario

API key in the request header is a public key.

Proposed solution

Validate that the API Key is the one you received at the time of boarding.

Status code: 405

Possible error scenario

Invalid request method.

Proposed solution

/3ds2/lookup and /3ds2/authenticate requests are valid only with the POST method.

/3ds2/challenge_result request is valid only with the GET method.

Status code: 406

Possible error scenario

Invalid value specified in the Accept header. Invalid values could be 'text/html', 'text/plain', 'application/xml', etc.

Proposed solution

The Accept header should either be empty or the only accepted value is application/json.

Status code: 413

Possible error scenario

Payload too large. Request entity is larger than the limit defined by server i.e. 256 KB.

Proposed solution

Try to truncate values in the optional fields.

See the documentation for a list of required and optional parameters for each request sent to the 3DS Server.

/3ds2/authenticate request parameters description

Status code: 415

Possible error scenario

Accepted Content-Type in the header is application/json. For any other value specified in the Content-Type such as ‘application/xml’, ‘text/xml’, 'multipart/form-data', etc., the response returns an error.

Proposed solution

Validate the Content-Type value in the request header is set to application/json.

error_outline
note

This release of 3DS integration does not support versioning. The application ignores any data that you provide in the Accept-Version header.