Searching for Errors in Your Orders

Searching for Errors in Your Orders

Use the Exception Search to find the errors in your transactions. In addition, you can use the Transaction Exception Detail Report, which is a daily downloadable report.

The figure below shows a request that failed because the authorization code had already been used to settle another transaction.

Because the search results page and the report share the same page, both tools show detailed information about transactions that were flagged by CyberSource or by your processor because of errors in the request data of your follow-on transactions. Follow-on services are those that depend on the processing results of another service. For example, you can request the capture service only if you have a successful card authorization, and you can request a follow-on credit only if you have a successful capture.


Follow-on service	Primary service
Credit card capture (if requested separately)	Credit card authorization
Credit card credit	Credit card capture
Credit card and electronic check void	Credit card capture and credit Electronic check debit and credit
Electronic check credit	Electronic check debit


	You will continue to receive immediately in the reply or the transaction receipt those error notifications sent by card processors during authorization attempts.

When you send follow-on transactions that contain data errors, such as a capture amount greater than the authorized amount or missing or invalid fields, these transactions are rejected and set aside. They cannot be processed until you locate and correct the errors. When errors occur, you are notified in the Message Center with a message that remains for seven days. A new message is added for each day when you have errors, with a maximum of seven messages. Messages older than seven days are deleted. The table below describes the type of information that you can find in the exception search.


Reason code	Three-digit reason code for the error that occurred. This number is the same one that you receive in your API reply or transaction receipt. For a list and description of the reason codes that you may receive, see Reason Codes in the Transaction Exception Detail Report.
Error Category	Type of error (data, processor, or settlement) or failure.
Error Message	Brief description of the error, for example: Error message: The authorization code for this request has already been settled. Interpretation: You have already requested to capture the authorization, or the capture has been processed and batched successfully. Suggested action: Verify that the authorization code is correct, and resend the request.
Original Request ID	Identifier generated by CyberSource for the original transaction. For example, if you receive an error message for a credit request, the Original Request ID is that of the capture that you processed originally. If you search for the original request ID, you will find the details page for the capture or for the combined authorization and capture if you had requested them together.

You must review the errors because the information provided may differ from what you received in the initial transaction receipt or reply.


	The message in the Error Information section takes precedence over that in the Request Information section: you must correct the error if you want to capture the order.

Example

This example compares the credit card transaction information that you can receive in the error information section versus what you can receive in the request information section immediately below:


Section	What You Receive	Value or Meaning
Error Information	Reason code Error message	235 The amount that you are trying to capture exceeds the amount that was authorized.
Request Information	Applications Reason code Error message	Credit card capture (green = successful) 100 Request was processed successfully.

After reviewing and correcting the errors, you can resend the request and change your system so that you can avoid these and other errors in the future. For more information on interpreting these errors, see the online help and the Transaction Exception Detail Report in the Business Center Reporting User Guide.