Return Codes for 3DS authentication

The following return codes are provided as a response to the script execution and also after authorization.

In the table below, we present the Return Codes that may be returned as a result of a request.

Reason CodeDescription
100Transaction completed successfully.
101One or more required fields are missing in the request. Possible action: check the missingField_0 to missingField_N fields in the response. Resend the request with complete information.
102One or more fields in the request contain invalid data. Possible action: check the invalidField_0 to invalidField_N fields in the response. Resend the request with correct information.
150Error: general system failure. Possible action: wait a few minutes and resend the request.
151Error: the request was received, but there was a server timeout. This error does not include client-server timeouts. Possible action: wait a few minutes and resend the request.
152Error: the request was received, but there was a service timeout. Possible action: wait a few minutes and resend the request.
234There is a problem with your merchant configuration. Possible action: do not resend the request. Contact support to correct the configuration issue.
475The client is registered for payer authentication. Authenticate the cardholder before proceeding with the transaction.
476The client cannot be authenticated. Possible action: review the client's request.
MPI901Unexpected error.
MPI902Unexpected authentication response.
MPI900An error occurred.
MPI601Challenge omitted.
MPI600The card brand does not support authentication.