Credit Card Error Messages and Rejection Codes

Last reviewed: 12/05/2011
Article ID: R11249

The information in this article applies to:

Note:  Tabs3 does not provide technical support for credit card rejections. If you need assistance with correcting issues that are causing rejections, please contact TSYS Merchant SolutionsSM Technical Support at (800) 228-2443.

Summary

When processing credit card transactions in Tabs3 and Trust Accounting Software, all authorization is handled using the PayFuse processing service. PayFuse is the Internet-based e-commerce payment processing solution for merchants provided by TSYS Merchant SolutionsSM (formerly First National Merchant Solutions®).

The PayFuse Web site is located at: https://www.payfuse.com/cgi-bin/clearcommerce_engine.exe.

General Troubleshooting

The following suggestions can help minimize chargebacks, double charges, and ease acceptance of credit card transactions.

Do not repeatedly submit credit card transactions when experiencing errors or rejections.
Repeatedly submitting credit card authorization requests could lead to duplicate charges to the client's credit card. When experiencing an error more than once, we recommend you call TSYS Merchant SolutionsSM Technical Support.
 
Test your Merchant Account to determine connectivity.
When experiencing connectivity issues with the PayFuse Web site, try using the Test Account button in Merchant Account Setup (Utilities | Customization | Merchant Services tab). If the test is successful, communication with the PayFuse Web service is possible and you can re-try your credit card transaction. If the test fails, check your network connection, your firewall settings, and your Internet Service Provider to make sure they are functional and correctly configured.

Error Messages

The following error messages may be encountered when entering credit card information, during the transmission of information from Tabs3 to PayFuse, or during the transmission of confirmation information from PayFuse to Tabs3.

Please select <field name>.
Please enter <field name>.
This message is shown when a required field is missing.
 
<fieldname> cannot be longer than <x> characters.
This message is shown when the data entered in a field is longer than that field allows.
 
The Card Number entered is not consistent with the selected Card Type. Are you sure you want to continue?
This message is shown when the credit card number entered does not match the credit card type selected.
 
The cardholder's last name cannot be more than 32 characters.
This message is shown when the cardholder's last name is longer than 32 characters. Although up to 65 characters can be entered in the Name field, everything following the last space is considered the last name by the PayFuse processing system. If this portion is longer than 32 characters, the last name must be truncated.
 
No supported card swiping device detected. Error:  <x>
This message is shown when the Swipe button is clicked, but no MagTek Mini Swipe USB device is detected.
This Credit Card type is not supported.
This message is shown when a credit card is swiped, and the card number does not match any type of credit card that Tabs3 supports. Tabs3 only supports Visa®, MasterCard®, Discover®, American Express® and Diners Club® cards.
 
This Credit Card type is not supported by this Merchant Account.
This message is shown when a credit card is swiped, and the card number does not match the type of credit cards that the merchant account has been configured to accept.
 
Error: <exception>. Verify that the credit card information is correct and try to submit the payment again.
This message is shown if an unexpected network error prevents Tabs3 from submitting the payment. This can be due to network problems, or lack of a response.
 
This credit card payment was sent to PayFuse and it may have been authorized.  However, an error occurred while receiving the response from PayFuse.  Please check the PayFuse Web site for the status of this transaction.  If the authorization was successful and you would like to keep Tabs3 synchronized with PayFuse, void the transaction on the PayFuse Web site and resubmit the credit card payment through Tabs3.

or (in executables dated 9/29/09 or later)
This credit card transaction was sent to PayFuse and it may have been authorized. However, an error occurred while receiving the response from PayFuse. Please check the PayFuse for the status of this transaction. If you find that the authorization was successful and you would like to keep <programName> synchronized with PayFuse, void the transaction on the PayFuse Web site and resubmit the credit card transaction through <programName>.
This message is displayed below an error message when Tabs3 has sent the credit card transaction to PayFuse, but an error occurs before Tabs3 receives a confirmation message. To correct this error, first check the PayFuse Web site for the transaction.
If this message is repeated, we recommend contacting TSYS Merchant SolutionsSM Technical Support at (800) 228-2443 to determine if there is a problem.
 
A number of error messages can be displayed along with the above message, including the following:
Could not parse the response.
This message is shown if Tabs3 receives a response from the PayFuse processing service, but it contains no valid codes. This could indicate network problems, or that errors occurred after the transaction was transmitted. Perform the recommendations in the previous message, and resubmit the payment if necessary.
Internet Exception: The operation timed out.
This message is shown if Tabs3 is able to transmit the credit card transactions to PayFuse, but never receives a response. This could indicate network problems, or that errors occurred after the transaction was transmitted. Perform the recommendations in the previous message, and resubmit the payment if necessary.
 
Internet Exception: <message>.
This message indicates an Internet connection issue prevented a response from being sent or received by Tabs3. Perform the recommendations in the previous message, and resubmit the payment if necessary. It may be necessary to contact your Internet Service Provider if this message is persistent.
 
Bad Request. HTTP Status Code: <number>.
This message is shown if Tabs3 is able to transmit the credit card transactions to PayFuse, but receives a response from the server that the HTTP request was invalid. This could indicate network problems, or that errors occurred after the transaction was transmitted. Perform the recommendations in the previous message, and resubmit the payment if necessary.
An error occurred while processing the transaction.
This message is shown if PayFuse reports an error while attempting to authorize the credit card. This message will be accompanied by a rejection code and/or an additional message code, as shown in the following sections.
 
The PayFuse Client ID you have entered is defined in <program> Merchant Services. Using the same PayFuse Client ID in Tabs3 and Trust Accounting is not recommended as it may result in commingled funds. Are you sure you want to use this PayFuse Client ID?
This message is shown when defining merchant accounts in Tabs3 Billing or Tabs3 Trust Accounting Software (TAS) when the same PayFuse Client is has been used in both programs. Due to most state bar prohibitions on commingling of firm and client funds, it is recommended that separate PayFuse Client IDs be used for credit card transactions from these programs.

Rejection Codes

All rejection codes and additional message codes are sent by the PayFuse service and are reported via the Credit Card Rejection window in Tabs3. The following list of rejection codes is available for troubleshooting purposes.

There are two error messages that may appear on the Payment Rejection window in Tabs3. The first, the Processor Error Code, is a more generic message about why the payment was rejected. Other codes may appear in the Additional Messages section, and are more specific. In some cases, only one code may be shown. The following is a list of possible rejection codes.

Processor Error Codes

1 - Approved.
2 - Referral (General).
3 - Referral - Call bank for manual approval.
4 - AVS request accepted.
5 - Transaction approved for authorization via batch.
6 - Transaction approved for conditional-settlement via batch.
7 - Transaction approved for authorization and capture via batch.
8 - Transaction approved for cancellation via batch.
20 - Partial Approval (Prepaid Cards only).
50 - Declined (General).
51 - Connection timed-out.
52 - Error connecting to processor or sending data.
53 - Error during Payment Commit phase.
54 - Timed out waiting for response.
55 - Issuer or switch is unavailable. No reply.
56 - Destination not found. Routing to issuer is not valid.
100 - Transaction failed to settle due to Soft Error.
101 - Transaction failed to settle due to Hard Error.
102 - Transaction failed to settle because the transaction is marked as Locked.
400 - Entry mode is not valid.
401 - Card-present flag is not valid.
402 - Customer-present flag is not valid.
403 - Terminal type is not valid.
404 - Terminal capability is not valid.
500 - Declined - Transaction considered fraudulent by Fraud component.
501 - The transaction was Approved by the processor. However, it failed a post-processing fraud rule and has been voided.
502 - The transaction was Approved by the processor. However, it failed a fraud rule and has been marked for review.
1001 - Invoice number not valid.
1002 - Amount not valid.
1003 - Interchange or Payment Service data submitted is not valid.
1004 - Level III data is missing or is not valid.
1005 - Currency is not valid.
1006 - BIN is not valid.
1007 - Card number is not valid.
1008 - Start date (Switch or Solo card) is not valid.
1009 - Issue number (Switch or Solo card) is not valid.
1010 - Magnetic stripe data is not valid.
1011 - Card expiration date is not valid.
1012 - Transaction date or time is not valid.
1013 - Date is not valid.
1014 - Transaction is not valid.
1015 - PIN is not correct.
1016 - Merchant ID is not valid.
1017 - Account is not valid.
1018 - Encryption Error.
1019 - Check Digit Error.
1020 - Verification Error.
1021 - Destination not found.
1022 - Service code is not valid or is restricted.
1023 - Violation, cannot complete.
1024 - Error response text from check service.
1025 - No account.
1026 - No such issuer.
1027 - PIN tries exceeded.
1028 - Transaction not permitted.
1029 - Security Violation.
1030 - Unable to back out transaction.
1031 - Unable to locate. No match was found.
1032 - Inconsistent data, rev. or repeat.
1033 - Already reversed at switch.
1034 - Cannot verify PIN.
1035 - Terminal ID is not valid.
1036 - Message format error.
1037 - Track 2 data is not valid.
1050 - Declined - Insufficient funds.
1051 - Customer card is expired.
1052 - Lost or stolen card.
1053 - Pick up card. Issuer wants card returned.
1054 - Response is not valid.
1055 - CVV failure or CVV Value supplied is not valid.
1056 - Transaction type or code is not valid.
1057 - Declined - Do not honor.
1058 - Declined - Exceeds issuer withdrawal limit.
1059 - Declined - Exceeds withdrawal limit.
1060 - Declined - Activity limit exceeded.
1061 - Declined - Cashback limit exceeded.
1062 - Cashback service not available.
1063 - Resend Batch.
1064 - Download failed.
1065 - Switch or issuer system error.
1066 - Unable to route transaction.
1067 - System error.
1068 - Duplicate transmission.
1069 - Honor with identification.
1070 - Currency conversion failed.
1071 - Periodic transaction - new account information available.
1072 - Periodic transaction - try again later.
1073 - Periodic transaction - do not try again.
1074 - Duplicate transaction.
1075 - Unsolicited reversal transaction.
1076 - Unable to complete transaction.
1077 - Re-enter transaction.
1078 - Previous message located.
1079 - Incomplete access, could not do reversal lookup. Re-send may be successful.
1080 - Undetermined reversal error. Re-send may be successful.
1081 - Timeout performing reversal. Re-send may be successful.
1082 - Issuer considers transaction fraudulent.
1083 - The date of birth indicates customer is less than 18 years of age.
1500 - Checking account is not valid.
1501 - Savings account is not valid.
2001 - Terminal ID not set up for settlement on this card type.
2002 - Terminal ID not set up for authorization on this card type.
2003 - Process code, authorization type, or card type is not valid.
2005 - Source ID is not valid.
2006 - Summary ID is not valid.
2008 - Bankcard merchant number in the processor host database is not valid.
2009 - File access error occurred in the processor host database.
2010 - Terminal flagged as Inactive in the processor host database.
2011 - Merchant ID and terminal ID combination is not valid.
2012 - Unrecoverable database error from an authorization process; this might indicate that the merchant ID and terminal ID combination was already in use.
2013 - Processor host-database-access lock encountered, Retry after 3 seconds.
2014 - Processor host-database error in summary process. Retry after 3 seconds.
2015 - Transaction ID is not valid, is incorrect, or is out of sequence.
2016 - Terminal flagged as Violated in processor host database. Call customer support.
2017 - Terminal ID not set up for leased line access on processor host database.
2018 - Settle Trans for Summary ID where earlier Summary ID still open.
2019 - Account number found by authorization process is not valid.
2020 - Settlement data found in summary process (trans level) is not valid.
2021 - Settlement data found in summary process (summary level) is not valid.
2024 - Transaction count value is not valid.
2025 - Entry not valid. Reenter the authorization request.
2026 - Lost or stolen card. Card issuer wants the card returned.
2027 - Batch is out of balance.
2028 - Terminal is not programmed for this service.
2050 - Dependent data is missing or is not valid.
2051 - Division ID is not valid.
2052 - Credit card number does not match the method of payment.
2053 - Method of payment is not valid for the division ID.
2054 - Card was authorized, but approval was overwritten per merchant.
2055 - Issuer requires more information.
2056 - Restricted card.
2057 - MAC code is invalid.
2058 - Check merchant entitlement.
2059 - Capture not allowed.
2060 - Communication error - resend.
2061 - Non-numeric folio number.
2062 - Retain card.
2063 - No action taken.
2064 - Suspicion of manipulation.
2065 - Requested function not supported.
2066 - Secondary transaction was not carried out with the card which was used for the original transaction.
2067 - The transaction amount of the secondary transaction is higher than original transaction amount.
2068 - Card issuer temporarily not reachable.
2069 - The card type is not processed by the authorization center.
2070 - Processing temporarily not possible.
2071 - The POS terminal has to initiate an automatic re-initialization.
2072 - The user should initiate an automatic re-initialization.
2073 - Declined - data entry error.
2074 - Declined - negative data.
2075 - Declined - scoring decline.
2076 - Declined - no response from host.
2077 - Institution is no longer valid.
2078 - Card not active. Effective date not valid.
2079 - Merchant not entitled for card type.
2080 - Failed to acquire a terminal id for the transaction.
2081 - Invalid routing number.
2082 - Missing bank account name.
2083 - Invalid account type.
2084 - Account holder deceased.
2085 - Account has been frozen.
2086 - Customer has refused to allow transaction.
2087 - No address for account on record.
2088 - Customer has not authorized transaction.
2089 - Invalid Canadian ECP action code.
2090 - Invalid Customer Permanent Id.
2091 - Please review this transaction for fraud. The transaction was approved by the processor, but the processor also indicates the transaction has characteristics of fraud.
2092 - Customer requested stop of specific recurring payment.
2093 - Customer requested stop of all recurring payments from specific merchant.
2094 - Stored Value card number is already active.
2095 - Card type verification error.
2096 - Hierarchy verification error.
2097 - Check is OK but cannot be converted.
2098 - ABA number is not valid. Not an ACH participant.
2099 - Check amount greater than the limit.
2100 - Check failed negative file comparison, unpaid items.
2101 - Duplicate check number.
2102 - MICR Error.
2103 - Too many checks. Over merchant or bank limit.
2104 - Deny Transaction. A new card has been issued.
2105 - Merchant not enrolled in cancellation program.
2106 - Submitted ECI (Electronic Commerce Indicator) is not valid.
2107 - MOTO (Mail Order / Telephone Order) indicator is not valid.
2108 - Three pass (HDC Error).
2109 - VPAS data error.
2110 - Insufficient permission to perform requested action.
2111 - The session has expired.
2112 - The billing agreement was cancelled.
-1 - Transaction status not found in response. Check the Merchant account credentials.
page top

Additional Message Codes

There are many additional message codes that can be received, and these codes vary depending on many factors (such as the type of credit card used, credit card issuer, network status, etc). When contacting TSYS Merchant SolutionsSM Technical Support for assistance with credit card rejections, please provide both the error code and the description. The following additional message codes are the most common.

35 - The data for element <field> is not valid.
220 - The card has expired.
221 - The card failed compliancy checks.
page top

References

THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

© 1999-2012 Software Technology, Inc.   All rights reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol (The "Pinwheel" symbol is a Registered Trademark of Software Technology, Inc.) are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base:   http://support.Tabs3.com
Web Site:   http://www.Tabs3.com