Reason Codes

The following table lists the Electronic Check Services reason codes returned by the Simple Order API. See the information about handling replies in Getting Started with CyberSource Essentials.

 

Cybersource reserves the right to add new reason codes at any time. If your error handler receives a reason code that it does not recognize, it should use the decision field to determine the result.

Table 15Reason Codes

Reason Code

Description

100

Successful transaction.

101

The request is missing one or more required fields.

Possible action: See the reply fields missingField_0...N for which fields are missing. Resend the request with the complete information. See the information about missing and invalid fields in Getting Started with CyberSource Essentials.

102

One or more fields in the request contains invalid data.

Possible action: See the reply fields invalidField_0...N for which fields are invalid. Resend the request with the correct information. See the information about missing and invalid fields in Getting Started with CyberSource Essentials.

150

Error: General system failure.

See the documentation for your client for information about handling retries in the case of system errors.

151

Error: The request was received, but there was a server timeout. This error does not include timeouts between the client and the server.

Possible Action: To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Business Center. See the documentation for your client for information about handling retries in the case of system errors.

152

Error: The request was received but there was a service timeout.

Possible action: To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Business Center. See the documentation for your client for information about handling retries in the case of system errors.

220

The processor declined the request based on a general issue with the customer’s account.

Possible action: Request a different form of payment.

221

The customer matched an entry on the processor’s negative file.

Possible action: Review the order and contact the payment processor.

222

The customer’s bank account is frozen.

Possible action: Review the order or request a different form of payment.

223

The customer’s payment or credit has been declined because there is an existing duplicate check, the original transaction was not approved, or a valid authorization could not be located.

Possible action: Review the order and contact the payment processor.

233

The processor declined the request based on an issue with the request itself.

Possible action: Request a different form of payment.

234

There is a problem with your merchant configuration.

Possible action: Do not resend the request. Contact Customer Support to correct the configuration problem.

235

The processor declined the request due to the requested amount exceeding the authorized amount.

Possible action: Review the order and contact the payment processor.

236

Processor failure.

Possible action: Wait a few minutes and resend the request.

241

The request ID is invalid for the follow-on request.

Possible action: Verify the request ID is valid and resend the request.

246

The debit or credit is not voidable because the debit or credit information has already been submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided.

Possible action: No action required.

247

You requested a credit for a debit that was previously voided.

Possible action: No action required.

250

Error: The request was received, but it timed out at the payment processor.

Possible action: To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Business Center.

388

Error: The routing number did not pass verification as described in ACH Verification.

Possible action: (1) Ask your customer to contact their bank to get an ACH routing number. (2) Ask your customer to provide the routing number and account number for a different bank account if they have one. (3) Request a different form of payment.