Reason Codes for the Simple Order API

Transaction was successful.

Request is missing one or more required fields. Examine the response fields

missingField_0

through

missingField_N

to identify which fields are missing. Resend the request with all the required fields.

One or more fields in the request contain invalid data. Examine the response fields

invalidField_0

through

invalidField_N

to identify which fields are invalid. Resend the request with valid data.

Merchant reference code for this authorization request matches the merchant reference code for another authorization request that you sent within the past 15 minutes. Resend this request with a unique merchant reference code.

Merchant transaction identifier (MTI) sent with this request has already been used in the past 60 days. Resend this request with a unique MTI.

Only a partial amount was approved.

System error. 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

Cybersource

system error, or it might indicate a processor rejection because of invalid data. In either case, do not design your system to endlessly try to resend a transaction when a system error occurs. See the documentation for the

Cybersource

client (SDK) that you are using for important information about how to handle system errors and retries.

Request was received but a server timeout occurred. This error does not include timeouts that occur 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 for information about handling retries in the case of system errors.

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 Business Center. See the documentation for your

Cybersource

client for information about handling retries in the case of system errors.

Your account is not enabled for the OCT service. Contact customer support to have your account enabled for this service.

The payout failed due to a MAC validation failure. The merchant is safe to retry the payout as it has not been send to the customer.

Authorization request was approved by the issuing bank but declined because the address verification system (AVS) could not verify it. You can capture the authorization, but consider reviewing the order for possible fraud.

Issuing bank has questions about the request.

Authorization:

You cannot 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.

Card is expired. You might also receive this value if the expiration date that you provided does not match the date that the issuing bank has on file. Request a different card or other form of payment.

Card was declined. No other information was provided by the issuing bank. Request a different card or other form of payment.

Account does not contain sufficient funds. Request a different card or other form of payment.

Card is lost or stolen. Review this transaction manually to ensure that you submitted the correct information.

Issuing bank is unavailable. Wait a few minutes and resend the request.

Card-Not-Present Transaction:

Card is inactive or not authorized for card-not-present transactions. Request a different card or other form of payment.

Card-Present Transaction:

Card is inactive, or the PIN is missing or incorrect. Ask the customer to re-enter the PIN or provide a different form of payment.

CVN did not match. Request a different card or other form of payment.

Account reached the credit limit, or the transaction amount exceeds the approved limit. Request a different card or other form of payment.

CVN is invalid. Re-enter the CVN or request a different form of payment.

EMV transaction was rejected. Resubmit the request with chip and PIN.

Account is in fraud watch status.

Some of the card data was invalid (CVV, expiration date, card number, name on card).

Generic decline. Request a different form of payment.

Customer's account is frozen. Review the order or request a different form of payment.

Customer's name matched an entry on the processor’s negative file. Review the order and contact the payment processor.

Authorization request was approved by the issuing bank but declined because CVN could not be verified. You can capture the authorization, but consider reviewing

the

order for possible fraud.

Account number is invalid. Request a different card or other form of payment.

Payment processor does not accept the card type. Contact your merchant bank to confirm that your account is set up to receive the card type.

Processor declined the card. For more information about the decline, search for the transaction in the Business Center and view the transaction details. Request a different card or other form of payment.

Information in your account is incorrect. Do not resend the request. Contact customer support to correct the information in your account.

Capture:

The requested capture amount exceeds the authorized amount. Send a new authorization and capture request for the new amount.

PIN Debit Purchase:

Transaction amount exceeds the approved limit. Send a new PIN-debit purchase request for a lower amount.

Processor failed. Wait a few minutes and resend the request.

Transaction was already captured.

Transaction was already reversed.

Requested transaction amount does not match the previous transaction amount. Correct the amount and resend the request.

Card type 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.

PIN Debit:

Processor declined the card. For more information about the decline, search for the transaction in the Business Center and view the transaction details.

Other Payment Method:

Request ID is invalid. Request a new authorization and, if successful, proceed with the capture.

Capture:

You requested a capture, but there is no corresponding, unused authorization. This situation occurs when there is no previously successful authorization request or when the previously successful authorization has already been captured. Request a new authorization, and if successful, proceed with the capture.

Reversal:

You requested a reversal, but there is no corresponding transaction or the transaction specified by the authorization code has already been settled.

Transaction is already settled or reversed.

Account number did not pass a verification check.

One of the following:

Capture or credit cannot be voided because the capture or credit information has already been submitted to your processor.
You requested a void for a type of transaction that cannot be voided.

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

The Boleto request was declined by your processor.

Request was received, but a timeout occurred at the payment processor. To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Business Center.

Customer has exceeded the debit card's limit on frequency of use, number of PIN entry tries, or maximum amount for the day. Request a different card or other form of payment.

Stand-alone credits are not allowed. 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 learn whether your processor supports stand-alone credits.

Credit amount exceeds the maximum allowed for your account. Contact customer support or your acquirer for details.

Gift card account or prepaid card account is already active.

Reload limit for the gift card or prepaid card was exceeded.

Requested amount conflicts with the minimum or maximum amount allowed on the gift card or prepaid card.

The merchant account set up is either invalid or missing on the acquirer’s gateway.

Request is still in progress. Wait for a response from

Cybersource

.

Mass transit transaction (MTT) was declined. When the transaction amount is less than the transit chargeback threshold, and the other mandated checks are performed, you can capture the authorization. Your acquirer can provide information about mandated checks and transit chargeback thresholds.

Processor missing field.

Transaction Error: Unable to confirm. Please contact Barclaycard help desk. Do not reprocess. Contact

Barclays

to understand payment status to know if the consumer received their funds.

Fraud score exceeds threshold. You can capture the authorization, but consider reviewing the order for the possibility of fraud.

Communication error. This can be caused by HTTP errors or using incorrect or outdated API keys for validation. Check the HTTP transmission and API validation keys.

Your request for a strong customer authentication (SCA) exemption was declined. SCA is required for this transaction.

Apartment number missing or not found. Ask the customer to verify the address information and resend the request.

Insufficient address information. Ask the customer to verify the address information and resend the request.

House/box number not found on street. Ask the customer to verify the address information and resend the request.

Multiple address matches were found. Ask the customer to verify the address information and resend the request.

P.O. Box identifier not found or out of range. Ask the customer to verify the address information and resend the request.

Route service identifier not found or out of range. Ask the customer to verify the address information and resend the request.

Street name not found in postal code. Ask the customer to verify the address information and resend the request.

Postal code not found in database. Ask the customer to verify the address information and resend the request.

Unable to verify or correct address. Ask the customer to verify the address information and resend the request.

Multiple internatinal address matches were found. Ask the customer to verify the address information and resend the request.

Address match not found. No reason given. Ask the customer to verify the address information and resend the request.

Unsupported character set. Verify the character set that you are using to process transactions.

Encountered a Payer Authentication problem. Payer could not be authenticated. Authenticate the cardholder before continuing with the transaction.

PIN data required. Request that the cardholder enter their PIN in the terminal.

The cardholder is enrolled in Payer Authentication. Authenticate the cardholder before continuing with the transaction.

Encountered a Payer Authentication problem. Payer could not be authenticated. Authenticate the cardholder before continuing with the transaction.

Strong customer authentication (SCA) is required for this transaction.

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 within 30 days, the order is rejected.

The order has been rejected by

Decision Manager

. Depending on your permissions, you can:

Convert the order to an Accepted status.
Void the authorization if it has not been sent to the payment processor for settlement.
Reverse the authorization if it has been sent to the payment processor for settlement but is not yet settled.
Settle the transaction if it has an authorization code.

One of these messages can display with this response code:

One of these messages can display with this response code:

Your acquirer or aggregator is rejecting this transaction: SAFEGUARDS.

Internal safeguards are preventing this transaction from processing.

Authorization request was approved by the issuing bank but declined 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 discover why

Cybersource

rejected the request.

The customer matched the Denied Parties List. Reject the customer's order.

Export

bill_country

/

ship_country

match. Reject the customer's order.

Export

email_country

match. Reject the customer's order.

Export

hostname_country

/

ip_country

match. Reject the customer's order.