the business side of wine

support center

call for help: 707.224.9620 x0
submit a support request
Print

Card Issuer Response Codes


Response Code Description
0 APPROVAL
2 CALL—no original no match. Often returned when the cardholder has exceeded daily credit limits/# of uses. Usually the Issuer wants to make sure the cardholder is still in possession of the card.
3 TERM ID ERROR—terminal ID error.
4 HOLD-CALL—retain card. Usually returned when the Issuer would like the merchant to take possession of the card due to potential fraud. Can also be returned if the transaction declines due to an AVS/CVV setting. The response text in this case is “DO NOT HONOR DUE TO AVS/CVV SETTINGS”.
5 DECLINE—do not honor. Normally occurs when cardholder has exceeded their allowable credit line.
6 ERROR—merchant closed, no match.
7 HOLD-CALL
10 PARTIAL APPROVAL
12 INVALID TRANS
13 AMOUNT ERROR. Occurs when the POS submits an amount field equal to $0.00. Re-enter transaction.
14 CARD NO. ERROR—Card number error. Issuer cannot find the account. Re-enter transaction.
15 NO SUCH ISSUER. Returned when the first six digits of the card number are not recognized by the Issuer. Reenter transaction.
19 RE ENTER—reenter transaction. Bad swipe.
41 HOLD-CALL—lost card.
43 HOLD-CALL—stolen card.
44 HOLD-CALL—pick up card.
51 DECLINE—insufficient funds.
52 NO CHECK ACCOUNT. Occurs when the debit/check card being attempted is not linked to a Checking Account.
53 NO SAVE ACCOUNT. Occurs when the debit/check card being used is not tied to a Savings Account.
54 EXPIRED CARD—card is expired. This response can also be returned in a Card Not Present environment if the cardholder tries to provide a valid expiration date, but the Issuer knows it is expired (indicates potential fraud).
55 WRONG PIN. Occurs in PIN-based Debit when the consumer enters the wrong 4-digit PIN.
56 INVALID CARD
57 SERV NOT ALLOWED—service not allowed. Can be an incorrect MID or terminal number, or attempt to process an unsupported card.
58 SERV NOT ALLOWED—service not allowed. Occurs when the POS attempts a transaction type that they are not set up for based on their MCC. (i.e., a merchant set up with a Direct Marketing MCC trying to perform a Debit transaction).
61 DECLINE. Occurs in PIN-based debit when the cardholder has exceeded their withdrawal limit when performing cash back.
62 DECLINE. Occurs on swiped transactions when the Service Code encoded on the mag stripe does not equal the one stored at the Issuer (potential fraudulent card).
63 SEC VIOLATION
65 DECLINE—activity Limit. Occurs when the cardholder has exceeded the number of times the card can be used in a specific time period. (i.e., 10x in a 48 hr span).
75 PIN EXCEEDED. Occurs when the number of attempts to enter the PIN has been exceeded.
76 NO ACTION TAKEN. Occurs when the reversal data in the POS transaction does not match the Issuer data.
77 NO ACTION TAKEN—duplicate reversal or duplicate transaction.
78 NO ACCOUNT—account suspended, cancelled, or inactive.
80 DATE ERROR
82 CASHBACK NO APP
85 CARD OK
86 CANT VERIFY PIN
91 NO REPLY—time out.
96 SYSTEM ERROR
EB CHECK DIGIT ERR
EC CID FORMAT ERROR—format error.
FR FRAUD—Transaction declined because possible fraud was detected by Heartland.
N7 CVV2 MISMATCH—incorrect number of CVV2/CID digits sent.
PD PARAMETER DOWNLOAD—EMV PDL system response. Response text indicates EMV PDL status code.



Portico Gateway Response Codes


Response Code Description
-21 Unauthorized
-2 Authentication error—Verify and correct credentials.
-1 Portico error—Developers are notified.
0 Success
+1 Gateway system error
+2 Duplicate transactions
+3 Invalid original transaction
+4 Transaction already associated with batch
+5 No current batch
+6 Invalid return amount—This can occur if a credit return request is against a specific original transaction and the return amount is greater than the original transaction’s settle amount, or the return amount is zero.
+7 Invalid report parameters
+8 Bad track data
+9 No transaction associated with batch
+10 Empty report
+11 Original transaction not CPC
+12 Invalid CPC data
+13 Invalid edit data
+14 Invalid card number
+15 Batch close in progress
+16 Invalid Ship Date—Transaction rejected because the ship date and month are invalid. Try again in a few seconds and resubmit.
+17 Invalid encryption version
+18 E3 MSR failure—The message returned with this code is the parsed error message from the MSR data stream.
+19 Invalid Reversal Amount—This can occur if a reversal request includes a new settlement amount that is not less than the current total authorization amount. The total authorization amount is the original authorization plus any incremental authorization minus any previous reversal amounts.
+20 Database operation time out—This may occur when Portico is trying to communicate to the database for large amounts of data. If this is due to a search, it can be corrected by adding more specific criteria.
+21 Archive database is currently unavailable—Try the transaction again later.
+22 Archive database is currently unavailable but an attempt was made to retrieve the data from the real-time database—If there was data available from the real-time database that met the request criteria then it was returned, however, it is not guaranteed to be complete. The request may need to be tried again later.
+23 An error was returned from the tokenization service when looking up a supplied token. This typically means that the provided token is bad, but it can also be returned when the data on the tokenization service has expired, been removed, or is no longer valid.
+24 This typically means that a token was supplied in the request but tokenization is not yet supported for the requested service type (see the section on tokenization for a list of supported services). This can also occur when tokenization is disabled for the entire system.
+25 This error is returned if the merchant provides a token (TokenData.TokenValue) and requests a token (TokenRequest) in CardData. In this case, the transaction is rejected because a token cannot be presented and requested in the same request.
+26 This error is returned if there is an error setting the token attribute. When possible the tokenization service error/return code is returned in the message text.
+27 This error is returned if the requested token was not found. This error can occur during TokenToPan (Lookup) or ManageTokens->Set (Update) requests.
+30 This can occur when Portico does not receive a response from the back end systems and Portico is not sure if the transaction was successful or not. In this case, the POS is responsible for deciding whether or not to issue a reversal for this transaction. This is used in cases where the transaction is an authorizing transaction, e.g. CreditAuth, CreditSale. If the transaction is non-authorizing, e.g. CreditAccountVerify, CreditReversal, and Portico receives no response then Portico sends back a System Error (+1) to the POS.
+31 This occurs when Portico attempts a reversal for the POS, but the reversal fails. In this case, the POS is responsible for issuing the reversal.
+32 Missing KTB error—This can occur when a POS is attempting to send encrypted data, but the expected KTB value was corrupted or not received.
+33 Missing KSN error—This can occur when a POS is attempting to send encrypted data, but the expected KSN value was corrupted or not received.
+34 Invalid data received—This error is returned from a CreditAuth or CreditSale if both GatewayTxnId and a CardData subfield are received.
+35 Device setting error—This error is returned from SendReceipt if the "AllowEmail" setting is not set to true for the device being used.
+36 Invalid Original Txn for Repeat—This error is returned from a CreditAuth or CreditSale if the original transaction referenced by GatewayTxnId cannot be found. This is typically because the original does not meet the criteria for the sale or authorization by GatewayTxnID. This error can also be returned if the original transaction is found, but the card number has been written over with nulls after 30 days.
+37 Missing element—This error is returned if a required (or conditional) element is missing from the transaction.
+38 Invalid auth amount—This error is returned from a CreditAuth or CreditSale by GatewayTxnId when the requested amount is over the threshold set for the transaction type, which is some percentage of the original amount (default = 100%).
+39 Transaction rejected because EMV TLV data was invalid.
+40 Transaction rejected because the referenced transaction has invalid EMV TLV data.
+41 Transaction declined because possible fraud was detected.
+50 Processor System error
+51 Processor Configuration error

Questions or Comments?
Please Contact Us


Vineyard Scene