Reason Codes
S
The following table describes the reason codes returned by the Simple Order API for the credit card services. 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
.
Important
Because CyberSource can add reply fields and reason codes at any time:
You 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.
Your error handler should be able to process new reason codes without problems.
Your error handler should use the decision field to determine the result if it receives a reason code that it does not recognize.
Table 88 Reason Codes
Reason
Code
100
Description
101
102
104
Successful transaction.
AIBMS:
If ccAuthReply_processorResponse is
08
, you can accept the transaction if the customer provides you with identification.
The request is missing one or more required fields.
Possible action: see the reply fields missingField_0 through missingField_N for which fields are missing. Resend the request with the complete information. For information about missing or invalid fields, see
Getting Started with CyberSource
Advanced for the Simple Order API
.
One or more fields in the request contains invalid data.
Possible action: see the reply fields invalidField_0 through invalidField_N for which fields are invalid. Resend the request with the correct information. For information about missing or invalid fields, see
Getting Started with CyberSource
Advanced for the Simple Order API
.
The merchant reference code for this authorization request matches the merchant reference code of another authorization request that you sent within the past 15 minutes.
Possible action: Resend the request with a unique merchant reference code.
Credit Card Services Using the Simple Order API | April 2017
423
Appendix S Reason Codes
Table 88 Reason Codes (Continued)
Reason
Code
110
Description
150
151
152
200
201
202
203
204
205
207
Only a partial amount was approved.
Possible action: see
"Partial Authorizations," page 91
.
General system failure.
See the documentation for your CyberSource client for information about handling retries in the case of system errors.
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 CyberSource client for information about handling retries in the case of system errors.
The request was received, but a service did not finish running in time.
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 CyberSource client for information about handling retries in the case of system errors.
The authorization request was approved by the issuing bank but declined by
CyberSource because it did not pass the Address Verification System (AVS) check.
Possible action: You can capture the authorization, but consider reviewing the order for the possibility of fraud.
The issuing bank has questions about the request. You do not receive an authorization code programmatically, but you might receive one verbally by calling the processor.
Possible action: Call your processor to possibly receive a verbal authorization. For contact phone numbers, refer to your merchant bank information.
Expired card. You might also receive this value if the expiration date you provided does not match the date the issuing bank has on file.
Possible action: Request a different card or other form of payment.
General decline of the card. No other information was provided by the issuing bank.
Possible action: Request a different card or other form of payment.
Insufficient funds in the account.
Possible action: Request a different card or other form of payment.
Stolen or lost card.
Possible action: Review this transaction manually to ensure that you submitted the correct information.
Issuing bank unavailable.
Possible action: Wait a few minutes and resend the request.
Credit Card Services Using the Simple Order API | April 2017
424
Appendix S Reason Codes
Table 88 Reason Codes (Continued)
Reason
Code
208
Description
209
210
211
221
230
231
232
233
234
235
236
237
238
239
Inactive card or card not authorized for card-not-present transactions.
Possible action: Request a different card or other form of payment.
CVN did not match.
Possible action: Request a different card or other form of payment.
The card has reached the credit limit.
Possible action: Request a different card or other form of payment.
Invalid CVN.
Possible action: Request a different card or other form of payment.
The customer matched an entry on the processor’s negative file.
Possible action: Review the order and contact the payment processor.
The authorization request was approved by the issuing bank but declined by
CyberSource because it did not pass the CVN check.
Possible action: You can capture the authorization, but consider reviewing the order for the possibility of fraud.
Invalid account number.
Possible action: Request a different card or other form of payment.
The card type is not accepted by the payment processor.
Possible action: Contact your merchant bank to confirm that your account is set up to receive the card in question.
General decline by the processor.
Possible action: Request a different card or other form of payment.
There is a problem with the information in your CyberSource account.
Possible action: Do not resend the request. Contact CyberSource Customer
Support to correct the information in your account.
The requested capture amount exceeds the originally authorized amount.
Possible action: Issue a new authorization and capture request for the new amount.
Processor failure.
Possible action: Wait a few minutes and resend the request.
The authorization has already been reversed.
Possible action: No action required.
The authorization has already been captured.
Possible action: No action required.
The requested transaction amount must match the previous transaction amount.
Possible action: Correct the amount and resend the request.
Credit Card Services Using the Simple Order API | April 2017
425
Appendix S Reason Codes
Table 88 Reason Codes (Continued)
Reason
Code
240
Description
241
242
243
246
247
250
254
The card type sent is invalid or does not correlate with the credit card number.
Possible action: Confirm that the card type correlates with the credit card number specified in the request, then resend the request.
The request ID is invalid.
Possible action: Request a new authorization, and if successful, proceed with the capture.
You requested a capture, but there is no corresponding, unused authorization record. Occurs if there was not a previously successful authorization request or if the previously successful authorization has already been used by another capture request.
Possible action: Request a new authorization, and if successful, proceed with the capture.
The transaction has already been settled or reversed.
Possible action: No action required.
One of the following:
The capture or credit is not voidable because the capture 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.
You requested a credit for a capture that was previously voided.
Possible action: No action required.
The request was received, but there was a timeout 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.
Stand-alone credits are not allowed.
Possible action: Submit a follow-on credit by including a request ID in the credit request. A follow-on credit must be requested within 60 days of the authorization.
To process stand-alone credits, contact your CyberSource account representative to find out if your processor supports stand-alone credits.
Credit Card Services Using the Simple Order API | April 2017
426
