app_reasonCodes

Reason Codes

Table 10 describes the reason codes returned by the Simple Order API for TMS. For a description of replies, decisions, and reason codes, see the information about handling replies in Getting Started with Cybersource Advanced for the Simple Order API.

Because Cybersource can add reply fields and reason codes at any time:

nYou must parse the reply data according to the names of the fields instead of the field order in the reply. For more information about parsing reply fields, see the documentation for your client.

nYour error handler should be able to process new reason codes without problems.

nYour error handler should use the decision field to determine the result if it receives a reason code that it does not recognize.

Table 10Reason Codes
Reason Code	Description
100	Transaction was successful.
101	Required field is null: <field name> Reason: Missing value in the required API field.
101	The request data did not pass the required fields check for this application: <field name> Reason: Invalid field included in the service request.
102	The request data did not pass the required fields check for this application: <field name> Reason: Invalid field included in the service request.
150	A system error has been encountered: Requested service is forbidden. Please contact customer support. Reason: The Token Management Service (TMS) profile is not enabled.
150	A system error has been encountered. This field is invalid or missing. Please contact Customer Support. Possible reasons: nYou are requesting a service using a draft TMS profile. nThe profile is non-transactable. nInvalid Profile ID. nProfile does not exist. nVault does not exist.
150	Error occurred during communication with token service. Please contact customer support. Reason: The TMS system is not responding.
231	The credit card number is either missing or invalid.