Not fluent in error codes? No problem. Just enter the Status or Reason or Service or HTTP Code receiving from the CyberSource Payment Gateway and allow us to translate Or download the latest version of the response codes and suggestions.
The value that was entered is not a valid response code. Please try again
Represents the overall order status of CyberSource RESTful Service.
These are the reasons behind failing or declined transactions for any Payments API request. Note: ‘errorInformation’ object is introduced in the response payload along with ‘status’ field on declined or unsuccessful transactions only. For successful transactions, ‘status’ is the only field returned in the response.
REST API resource used for making the transaction. Below are possible services that you can currently search with:
Hypertext Transfer Protocol (HTTP) response status codes. CyberSource payments API responds with any of these HTTP status codes 201, 400 or 502
201 - These transactions has resource ‘ID’ created by CyberSource. For any unsuccessful transactions under this HTTP status code, it is most probably under review or declined or failed by CyberSource or merchant’s processor. No request payload changes are expected from Merchant’s end.
400 - There is something wrong or missing in the request payload from Merchant. Try correcting request payload based on error message to get successful response.
502 – Either server error or time-out. Retrying such transactions may work. Please contact support to investigate further.