Connectivity - Common Hypertext Transfer Protocol (HTTP) Status Codes
KA-07690
70
02/06/2025 23:42 PM
1.0
Objective
This resource provides guidance related to common HTTP Status Codes and how they correlate to Cybersource.
| SC | Description |
| 150 | Forbidden: The server understood the request but refuses to authorize it. This often means that the user’s profile lacks the necessary permissions to perform the requested operation. Ensure that you have the appropriate permissions and try again. |
| 200 | OK: The request was processed successfully. For a GET request, this means the server has fetched the requested resource. If the resource is empty, the response will reflect that. For a POST request, this means the server successfully created or modified the resource, and the response will provide details about the result. |
| 201 | Created: The request was successful, resulting in the creation of a new resource. If you receive this status for a transaction that didn't seem to succeed, it means that Cybersource or the merchant's processor has marked the transaction for review, or it has been declined or failed. |
| 204 | No Content: The server successfully processed the request, but there is no content to return. This usually happens for requests that modify resources, like a successful DELETE request, where there is nothing to display back to the user. |
| 400 | Bad Request: The server could not understand the request due to invalid syntax. This often means there is something wrong or missing in the merchant's request. Review the request for errors, correct them, and resubmit. |
| 404 | Not Found: The server cannot find the requested resource. This can happen if the token ID does not exist or was entered incorrectly. Verify the token ID and try again. |
| 409 | Conflict: The request could not be completed due to a conflict with the current state of the resource. This might mean that the token you are trying to use is already associated with a payment instrument. |
| 410 | Gone: The requested resource is no longer available and has been permanently removed. This can occur if the token has been deleted and is no longer accessible. |
| 424 | Failed Dependency: The request failed because it depended on another request that also failed. This may mean that the profile represented by the profile ID does not exist, or the profile ID was entered incorrectly. Verify the profile ID and ensure all dependencies are met before retrying. |
| 500 - 502 | Internal Server Error: The server encountered an unexpected condition that prevented it from fulfilling the request. This can indicate a server error or a timeout. Retry the transaction, and if the issue persists, contact customer support for further investigation. |
Additional Information
For a complete list of reasons corresponding to common HTTP Status Codes, refer to our Transaction Response Codes page
Was this article helpful?
Articles Recommended for You