On This Page

Reason Codes

The

reason_code

field contains additional data regarding the decision response of the transaction. Depending on the decision of a transaction request, the default receipt page or your receipt page is displayed to the customer. Both you and your customer can also receive an email receipt. See Merchant Notifications.

Reason Codes
Reason Code	Description
100	Successful transaction.
101	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.
102	One or more fields in the request contain invalid data. Possible action: 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. Possible action: resend the request with unique access_key and transaction_uuid fields. A duplicate transaction was detected. The transaction might have already been processed. Possible action: 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. See Viewing Transactions in the Business Center.
110	Only a partial amount was approved.
150	General system failure. Possible action: 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. Possible action: 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. Possible action: 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. Possible action: 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. Possible action: 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. Possible action: request a different card or other form of payment.
203	General decline of the card. No other information was provided by the issuing bank. Possible action: request a different card or other form of payment.
204	Insufficient funds in the account. Possible action: request a different card or other form of payment.
205	Stolen or lost card. Possible action: review this transaction manually to ensure that you submitted the correct information.
207	Issuing bank unavailable. Possible action: 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. Possible action: request a different card or other form of payment.
210	The card has reached the credit limit. Possible action: request a different card or other form of payment.
211	Invalid CVN. Possible action: request a different card or other form of payment.
221	The customer matched an entry on the processor's negative file. Possible action: 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. Possible action: you can capture the authorization, but consider reviewing the order for the possibility of fraud.
231	Invalid account number. Possible action: request a different card or other form of payment.
232	The card type is not accepted by the payment processor. Possible action: contact your merchant bank to confirm that your account is set up to receive the card in question.
233	General decline by the processor. Possible action: request a different card or other form of payment.
234	There is a problem with the information in your account. Possible action: do not resend the request. Contact customer support to correct the information in your account.
236	Processor failure. Possible action: 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. Possible action: 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. Possible action: authenticate cardholder before proceeding.
476	Payer authentication could not be authenticated.
478	Strong customer authentication (SCA) is required for this transaction.
481	Transaction declined based on your payment settings for the profile. Possible action: review the risk score settings for the profile.
520	The authorization request was approved by the issuing bank but declined based on your `Decision Manager` settings. Possible action: review the authorization request.