101

DMISSINGFIELD

The request is missing one or more required fields.

Possible action: If you are using the Simple Order API, see the reply fields missingField_0...N for which fields are missing. Resend the request with the complete information.

102

DINVALIDDATA

One or more fields in the request contains invalid data.

Possible action: If you are using the Simple Order API, see the reply fields invalidField_0...N for the invalid fields. If you are using the Hosted Order Page, you can receive this reason code for invalid (InvalidField_0...N) and missing (MissingField_0...N) fields. Resend the request with the correct information.

104

DDUPLICATE

The transaction is declined because the merchant reference number sent matches the merchant reference number of another transaction sent in the last 15 minutes.

Possible action: Ensure that the merchant reference number is unique.

150

ESYSTEM

Error: General system failure.

See the documentation for your CyberSource client for information about how to handle retries in the case of system errors.

151

ETIMEOUT

Error: The request was received but there was a server time-out. This error does not include time-outs 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 Enterprise Business Center. See the documentation for your CyberSource client for information about how to handle retries in the case of system errors.

202

DCARDEXPIRED

Expired card. You might also receive this if the expiration date you provided does not match the date the issuing bank has on file.

Note The ccCreditService does not check the expiration date; instead, it passes the request to the payment processor. If the payment processor allows issuance of credits to expired cards, CyberSource does not limit this functionality.

Possible action: Request a different card or other form of payment.

203

DCARDREFUSED

The card was declined. No other information was provided by the issuing bank.

Possible action: Request a different card or other form of payment.

204

DCARDREFUSED

The account has insufficient funds.

Possible action: Request a different card or other form of payment.

205

DCARDREFUSED

The card was stolen or lost.

Possible action: Review the customer's information and determine if you want to request a different card from the customer.

207

DCARDREFUSED

The issuing bank was unavailable.

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

208

DCARDREFUSED

The card is inactive or not authorized for card-not-present transactions.

Possible action: Request a different card or other form of payment.

209

DCARDREFUSED

American Express Card Identification Digits (CID) did not match.

Possible action: Request a different card or other form of payment.

210

DCARDREFUSED

The credit limit for the card has been reached.

Possible action: Request a different card or other form of payment.

223

DPAYMENTREFUSED

A request was made to credit an order for which there is no corresponding, unused payment record. Occurs if no previously successful pay Pal Button Create Service or pay Pal Pre approved Payment Service request exists, or if the previously successful payment has already been used by another payPalCreditService request.

Possible action: Verify that have not already credited this payment, or verify that you are crediting the correct payment.

231

DINVALIDCARD

Invalid account number.

Possible action: Request a different card or other form of payment.

233

DINVALIDDATA

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

Possible action: Request a different card or other form of payment.

235

DINVALIDDATA

The requested amount exceeds the originally authorized amount. Occurs, for example, if you try to capture an amount larger than the original authorization amount.

Possible action: Issue a new authorization and capture request for the new amount.

236

DINVALIDDATA

Processor failure.

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

237

DINVALIDDATA

The authorization has already been reversed.

Possible action: No action required.

238

DINVALIDDATA

The authorization has already been captured.

Possible action: No action required.

239

DINVALIDDATA

The requested transaction amount must match the previous transaction amount.

Possible action: Correct the amount and resend the request.

240

DINVALIDDATA

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, and resend the request.

241

DINVALIDDATA

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

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

242

DNOAUTH

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.

243

DINVALIDDATA

The transaction has already been settled or reversed.

Possible action: No action required.

244

DINVALIDACCOUNT

The bank account number did not pass the validation check. Applies to bank transfer refunds with banks in France, Germany, and the United Kingdom; and direct debits and direct debit refunds with banks in Germany.

Possible action: Verify with the customer that the account number is correct; if it was incorrect, request the service again with the corrected information.

246

DNOTVOIDABLE

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.

247

DINVALIDDATA

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

Possible action: No action required.

250

ETIMEOUT

Error: The request was received, but a time-out occurred 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.

253

DNOVALIDATE

The directDebitService_validateRequestID that you provided has already been used in another request for the Direct Debit Service.

Possible action: Request the Direct Debit Validate Service again and use the new request ID that you receive.

301

DINVALIDDATA

The mandate ID that you provided is invalid. This reason code applies only to direct debits in the United Kingdom.

Suggested action: Verify that you provided the correct mandate ID and send the request again.

302

DINVALIDDATA

No valid mandate exists because it has expired, or the customer's bank rejected or canceled it. This reason code applies only to direct debits in the United Kingdom.

Suggested action: Obtain a valid mandate from the customer, and process the direct debit after the appropriate 5-day waiting period.

303

DINVALIDDATA

You must wait at least 5 business days after requesting the mandate before processing the first direct debit. This reason code applies only to direct debits in the United Kingdom.

Suggested action: Wait until the 5 business days have completed, and process the first direct debit.

304

DINVALIDDATA

The bank account number that you provided does not match the account number on file for this mandate. This reason code applies only to direct debits in the United Kingdom.

Suggested action: Verify that the mandate ID and corresponding bank account number are correct, and request the direct debit again.

311

DINVALIDDATA

The direct debit has already been reversed. Therefore, you may not request a refund.

Suggested action: No action required.

312

DINVALIDDATA

The direct debit has not yet been settled. Therefore, you may not yet request a refund.

Suggested action: Wait until the customer’s payment has been received, and request the refund. Look for confirmation of payment in the Payment Events Report. For more information about the report, see the Global Payment Service Planning and User’s Guide.

313

DINVALIDDATA

You have already refunded 100% of the direct debit. Therefore, you may not request a refund for this direct debit.

Suggested action: No action required.

321

DINVALIDDATA

The bank transfer has not yet been settled. Therefore, you may not yet request a refund.

Suggested action: Wait until the customer’s payment has been received, and request the refund. Look for confirmation of payment in the Payment Events Report. For more information about the report, see the Global Payment Service Planning and User’s Guide.

322

DINVALIDDATA

You have already refunded 100% of the bank transfer. Therefore, you may not request a refund for this bank transfer.

Suggested action: No action required.

341

DINVALIDDATA

You have exceeded the maximum daily refund amount allowed.

Suggested action: Resend your request the following day.

342

DINVALIDDATA

An error occurred during settlement.

Suggested action: Verify the information in your request and resend the order.