Cybersource error codes are used to indicate the status of a transaction. They can be used to troubleshoot problems with transactions and to identify the specific reason for a decline.
Cybersource error codes
Here are some of the most common Cybersource error codes:
Reason Code | Reply Flag (SCMP) | Description | Possible Action |
---|---|---|---|
100 | SOK | Successful transaction | |
101 | DMISSINGFIELD | Declined – The request is missing one or more fields | See the reply fields missingField_0…N for which fields are invalid. Resend the request with the correct information. |
102 | DINVALIDDATA | Declined – One or more fields in the request contains invalid data. | See the reply fields invalidField_0…N for which fields are invalid. Resend the request with the correct information.
I’m receiving Reason Code 102 |
104 | DDUPLICATE | Declined – The merchantReferenceCode sent with this authorization request matches the merchantReferenceCode of another authorization request that you sent in the last 15 minutes. | Resend the request with a unique merchantReferenceCode value. |
110 | SPARTIALAPPROVAL | Partial amount was approved | Partial Authorizations in Credit Card Services Using the Simple Order API |
150 | ESYSTEM | Error – General system failure. | A system error occurred.
You must design your transaction management system to include a way to correctly handle system errors. Depending on which payment processor is handling the transaction, the error might indicate a valid Cybersourcesystem error, or it might indicate a processor rejection because of some type of invalid data. In either case, it is best not to design your system to endlessly try to resend a transaction when a system error occurs. See the documentation for the Cybersourceclient (SDK) that you are using for important information about how to handle system errors and retries. |
151 | ETIMEOUT | Error – The request was received but there was a server timeout. This error does not include timeouts between the client and the server. | 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 (SDK) for information about how to handle retries in the case of system errors. |
152 | ETIMEOUT | Error: The request was received, but a service did not finish running in time. | 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 (SDK) for information about how to handle retries in the case of system errors. |
154 | ESYSTEM | Bad MaC key | It signifies that the payout due to MAC validation failure. The merchant is safe to retry the payout as it has not been send to the customer.
On receipt of this response code, the TID used is out into quarantine for 24 hours. Cybersource operation team gets an alert and they request a MAC reset by Barclays, the TID then comes back into service 24 hours after it went out of service. Payout merchants should always boarded with multiple TIDs to prevent the quarantining process from bring them hard down for payouts. |
200 | DAVSNO | Soft Decline – The authorization request was approved by the issuing bank but flagged by Cybersource because it did not pass the Address Verification Service (AVS) check. | You can capture the authorization, but consider reviewing the order for the possibility of fraud. |
201 | DCALL | Decline – 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. | Call your processor to possibly receive a verbal authorization. For contact phone numbers, refer to your merchant bank information. |
202 | DCARDEXPIRED | Decline – 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. |
Request a different card or other form of payment. |
203 | DCARDREFUSED | Decline – General decline of the card. No other information provided by the issuing bank. | Request a different card or other form of payment. |
204 | DCARDREFUSED | Decline – Insufficient funds in the account. | Request a different card or other form of payment. |
205 | DCARDREFUSED | Decline – Stolen or lost card. | Refer the transaction to your customer support center for manual review. |
207 | DCARDREFUSED | Decline – Issuing bank unavailable. | Wait a few minutes and resend the request. |
208 | DCARDREFUSED | Decline – Inactive card or card not authorized for card-not-present transactions. | Request a different card or other form of payment. |
209 | DCARDREFUSED | Decline – card verification number (CVN) did not match. | Request a different card or other form of payment. |
210 | DCARDREFUSED | Decline – The card has reached the credit limit. | Request a different card or other form of payment. |
211 | DCARDREFUSED | Decline – Invalid Card Verification Number (CVN). | Request a different card or other form of payment. |
220 | DCHECKREFUSED | Decline – Generic Decline. | Request a different form of payment. |
221 | DCHECKREFUSED | Decline – The customer matched an entry on the processor’s negative file. | Review the order and contact the payment processor. |
222 | DCHECKREFUSED | Decline – customer’s account is frozen | Review the order or request a different form of payment. |
230 | DCV | Soft Decline – The authorization request was approved by the issuing bank but flagged by Cybersource because it did not pass the Card Verification Number (CVN) check. | You can capture the authorization, but consider reviewing the order for the possibility of fraud. |
231 | DINVALIDCARD | Decline – Invalid account number | Request a different card or other form of payment. |
232 | DINVALIDCARD | Decline – The card type is not accepted by the payment processor. | Contact your merchant bank to confirm that your account is set up to receive the card in question. |
233 | DINVALIDDATA | Decline – General decline by the processor. | Request a different card or other form of payment. |
234 | DINVALIDDATA | Decline – There is a problem with your Cybersource merchant configuration. | Do not resend the request. Contact Customer Support to correct the configuration problem. |
235 | DINVALIDDATA | Decline – The requested amount exceeds the originally authorized amount. Occurs, for example, if you try to capture an amount larger than the original authorization amount. | Issue a new authorization and capture request for the new amount. |
236 | DINVALIDDATA | Decline – Processor failure. | Wait a few minutes and resend the request. |
237 | DINVALIDDATA | Decline – The authorization has already been reversed. | No action required. |
238 | DINVALIDDATA | Decline – The transaction has already been settled. | No action required. |
239 | DINVALIDDATA | Decline – The requested transaction amount must match the previous transaction amount. | Correct the amount and resend the request. |
240 | DINVALIDDATA | Decline – The card type sent is invalid or does not correlate with the credit card number. | Confirm that the card type correlates with the credit card number specified in the request, then resend the request. |
241 | DINVALIDDATA | Decline – The referenced request id is invalid for all follow-on transactions. | No action required. |
242 | DNOAUTH | Decline – The request ID is invalid.
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 in another capture request. |
Request a new authorization, and if successful, proceed with the capture. |
243 | DINVALIDDATA | Decline – The transaction has already been settled or reversed. | No action required. |
246 | DNOTVOIDABLE | Decline – 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. | No action required. |
247 | DINVALIDDATA | Decline – You requested a credit for a capture that was previously voided. | No action required. |
248 | DBOLETODECLINED | Decline – The boleto request was declined by your processor. | |
250 | ETIMEOUT | Error – The request was received, but there was a timeout at the payment processor. | To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Enterprise Business Center. |
251 | DCARDREFUSED | Decline – The Pinless Debit card’s use frequency or maximum amount per use has been exceeded. | Request a different card or other form of payment. |
254 | DINVALIDDATA | Decline – Account is prohibited from processing stand-alone refunds. | 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. |
268 | ETIMEOUT | Transaction Error: Unable to confirm, please contact Barclaycard help desk. Do not re-process | Contact Barclays to understand payment status to know if the consumer received their funds. |
400 | DSCORE | Soft Decline – Fraud score exceeds threshold. | You can capture the authorization, but consider reviewing the order for the possibility of fraud. |
450 | DINVALIDADDRESS | Apartment number missing or not found. | Ask the customer to verify the address information and resend the request. |
451 | DINVALIDADDRESS | Insufficient address information. | Ask the customer to verify the address information and resend the request. |
452 | DINVALIDADDRESS | House/Box number not found on street. | Ask the customer to verify the address information and resend the request. |
453 | DINVALIDADDRESS | Multiple address matches were found. | Ask the customer to verify the address information and resend the request. |
454 | DINVALIDADDRESS | P.O. Box identifier not found or out of range. | Ask the customer to verify the address information and resend the request. |
455 | DINVALIDADDRESS | Route service identifier not found or out of range. | Ask the customer to verify the address information and resend the request. |
456 | DINVALIDADDRESS | Street name not found in Postal code. | Ask the customer to verify the address information and resend the request. |
457 | DINVALIDADDRESS | Postal code not found in database. | Ask the customer to verify the address information and resend the request. |
458 | DINVALIDADDRESS | Unable to verify or correct address. | Ask the customer to verify the address information and resend the request. |
459 | DINVALIDADDRESS | Multiple addres matches were found (international) | Ask the customer to verify the address information and resend the request. |
460 | DINVALIDADDRESS | Address match not found (no reason given) | Ask the customer to verify the address information and resend the request. |
461 | DINVALIDADDRESS | Unsupported character set | Verify the character set that you are using to process transactions. |
475 | DAUTHENTICATE | The cardholder is enrolled in Payer Authentication. Please authenticate the cardholder before continuing with the transaction. | Authenticate the cardholder before continuing with the transaction. |
476 | DAUTHENTICATIONFAILED | Encountered a Payer Authentication problem. Payer could not be authenticated. | Authenticate the cardholder before continuing with the transaction. |
478 | DAUTHENTICATE | Strong customer authentication (SCA) is required for this transaction. | Resubmit using SCA. |
480 | DREVIEW | The order is marked for review by Decision Manager | Depending on your permissions, you can: – Accept, reject, or settle the order. – Void or reverse the authorization. – Take no action. If no action is taken, the order will be rejected after 30 days. |
481 | DREJECT | The order has been rejected by Decision Manager | Depending on your permissions, you can: – Convert the order to an Accepted status. – If the authorization has not been sent to the payment processor for settlement, it can be voided. – If the authorization has been sent to the payment processor for settlement but is not yet settled, it can be reversed. – If the transaction has an authorization code, it can be settled. See Decision Manager or Fraud Management Essentials. |
490 | Your aggregator or acquirer is not accepting transactions from you at this time. | Contact your acquirer or payment technology partner. | |
491 | Your aggregator or acquirer is not accepting this transaction. | Contact your acquirer or payment technology partner. | |
520 | DSETTINGS | Soft Decline – The authorization request was approved by the issuing bank but declined by Cybersource based on your Smart Authorization settings. | Do not capture the authorization without further review. Review the ccAuthReply_avsCode, ccAuthReply_cvCode, and ccAuthReply_authFactorCode fields to determine why Cybersource rejected the request. |
700 | DRESTRICTED | The customer matched the Denied Parties List | Reject the customer’s order. |
701 | DRESTRICTED | Export bill_country/ship_country match | Reject the customer’s order. |
702 | DRESTRICTED | Export email_country match | Reject the customer’s order. |
703 | DRESTRICTED | Export hostname_country/ip_country match | Reject the customer’s order. |
These are just some of the most common Cybersource error codes. The specific error codes that you may encounter may vary depending on the type of transaction and the reason for the decline.
If you receive a Cybersource error code, you can consult the Cybersource documentation for more information about the specific error code. You can also contact Cybersource customer support for assistance.
I hope this helps! Let me know if you have other questions or requests.