HTTP Response - DAS Gateway Documentation

HTTP Response	Description	Explanation
200	Request Successful	The request was successfully received and processed.
201	Resource Created	A new resource has been successfully created.
400	Bad Request	The server could not process the request due to a client error (e.g., malformed request syntax).
401	Unauthorized	Authentication is required, or the provided credentials are invalid.
404	Not Found	The requested resource could not be found on the server.
406	Not Acceptable (Invalid Card)	The request’s content is not acceptable, often due to an invalid card or data format.
412	Precondition Failed	The server does not meet one or more of the preconditions specified in the request.
500	Server Error	An internal server error occurred. Try again later or contact support if the issue persists.
502	Bad Gateway	The server, acting as a gateway, received an invalid response from an upstream server.
504	Gateway Time-out	The server did not receive a timely response from an upstream server and timed out.

Additional Resources

Frequently Asked Questions

Visit our FAQ section for answers to common questions about HTTP response codes and troubleshooting.

Contact Support

Need assistance? Reach out to our support team for help with HTTP response code issues.

Tokenization Response Codes

⌘I