Useful tables

On this page:

Response codes
Reason codes
Notification types

Response codes

Responses related to payment approval or address details are shown here:

Response code	Status	Reason	Action
-	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. For more information, read here
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 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.Transaction fails with a response of 203. For more information, read here.
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. For more information, read here.
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.

Reason codes

The reason_code field contains additional data regarding the decision response of the transaction.

Reason code	Description	Possible action
100	Successful transaction	-
102	One or more fields in the request contain invalid data.	See the response field `invalid_fields` to ascertain which fields are invalid. Resend the request with the correct information.
104	The access_key and transaction_uuid fields for this authorization request match the `access_key` and `transaction_uuid` fields of another authorization request that you sent within the past 15 minutes. A duplicate transaction was detected. The transaction might have already been processed.	Resend the request with unique `access_key` and `transaction_ uuid` fields. Before resubmitting the transaction, use the single transaction query or search for the transaction using the Business Center to confirm that the transaction has not yet been processed.
110	Only a partial amount was approved.	-
150	General system failure.	To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status either directly in the Business Center or programmatically through the Single Transaction Query.
151	The request was received but a server timeout occurred. 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 either directly in the Business Center or programmatically through the Single Transaction Query.
152	The request was received, but a service timeout occurred.	To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status either directly in the Business Center or programmatically through the Single Transaction Query.
200	The authorization request was approved by the issuing bank but declined because it did not pass the Address Verification System (AVS) check.	You can capture the authorization, but consider reviewing the order for fraud.
201	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	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.	Request a different card or other form of payment.
203	General decline of the card. No other information was provided by the issuing bank.	Request a different card or other form of payment.
204	Insufficient funds in the account.	Request a different card or other form of payment.
205	Stolen or lost card	Review this transaction manually to ensure that you submitted the correct information.
207	Issuing bank unavailable.	To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status either directly in the Business Center or programmatically through the Single Transaction Query.
208	Inactive card or card not authorized for card-not-present transactions.	Request a different card or other form of payment.
210	The card has reached the credit limit.	Request a different card or other form of payment.
211	Invalid CVN	Request a different card or other form of payment.
221	The customer matched an entry on the processor’s negative file.	Review the order and contact the payment processor.
222	Account frozen	-
230	The authorization request was approved by the issuing bank but declined because it did not pass the CVN check.	You can capture the authorization, but consider reviewing the order for the possibility of fraud.
231	Invalid account number	Request a different card or other form of payment.
232	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	General decline by the processor.	Request a different card or other form of payment.
234	There is a problem with the information in your account.	Do not resend the request. Contact customer support to correct the information in your account.
236	Processor failure	To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status either directly in the Business Center or programmatically through the Single Transaction Query.
240	The card type sent is invalid or does not correlate with the payment card number.	Confirm that the card type correlates with the payment card number specified in the request; then resend the request.
475	The cardholder is enrolled for payer authentication.	Authenticate cardholder before proceeding.
476	Payer authentication could not be authenticated.	-
481	Transaction declined based on your payment settings for the profile.	Review the risk score settings for the profile.
520	The authorization request was approved by the issuing bank but declined based on your legacy Smart Authorization settings.	Review the authorization request.

Notification types

Decision	Description	Type of Notification	Hosted Page
ACCEPT	Successful transaction. Reason codes 100 and 110.	Custom receipt page Customer receipt email Merchant POST URL Merchant receipt email	Accept
REVIEW	Authorization was declined; however, a capture might still be possible.Review payment details. See reason codes 200, 201, 230, and 520.	Custom receipt page Customer receipt email Merchant POST URL Merchant receipt email	Accept
DECLINE	Transaction was declined. See reason codes 102, 200, 202, 203, 204, 205, 207, 208, 210, 211, 221, 222, 230, 231, 232, 233, 234, 236, 240, 475, 476,and 281.	Custom receipt page¹ Merchant POST URL¹ Merchant receipt email¹	Decline
ERROR	Access denied, page not found, or internal server error. See reason codes 102, 104, 150, 151 and 152.	Custom receipt page Merchant POST URL	Error
CANCEL	The customer did not accept the service fee conditions. The customer cancelled the transaction.	Custom receipt page Merchant POST URL	Cancel

¹ If the retry limit is set to 0, the customer receives the decline message, Your order was declined. Please verify your information. before the merchant receives it. The decline message relates to either the processor declining the transaction or a payment processing error, or the customer entered their 3D Secure credentials incorrectly.

Useful tables

Response codes

Reason codes

Notification types

Do you like our page?