Common Errors & Troubleshooting NMI

• Processor Errors: These are errors stemming from us at Talus Pay but being communicated through the NMI platform

CODE	GENERAL DESCRIPTION
400	Transaction error returned by processor.
410	Invalid merchant configuration.
411	Merchant account is inactive.
420	Communication error.
421	Communication error with issuer.
430	Duplicate transaction at processor.
440	Processor format error.
441	Invalid transaction information.
460	Processor feature not available.
461	Unsupported card type.

• Other common Processor Errors by Processor (TSYS or First Data Omaha)

First Data Omaha:

•  INV BATCH SEQ
  • Batch Sequence: If anything upsets the batch sequence at Omaha, this error will be received.
  • Force Close of Batch: Closing out a batch manually outside the gateway. Sometimes called "force closing" a batch.
  • Re-routing Refunds: This will be seen when an Omaha MID is closed and refunds are not re-routed and someone tries to run a refund.
  • MID number change (historical): We used to see this when the MID number was changed inside an already existing setup, rather than a new MID being added and refunds rerouted to the new MID. This is now blocked on Omaha to prevent this problem.
• INVALID AMOUNT
  • Max ticket amount be set at the processor level. The affiliate will need to contact either the processor or the customers bank to get more information.
  • Transactions over are not allowed 99,999.99
• INVALID MRCH #
  • Affiliate must call Omaha to verify the info in the gateway compared to set up at Omaha. -Could mean not set up for AMEX if an AMEX being attempted.
• INVALID TRAN TYPE (INV TRAN TYPE)
  • The account is new. This response will also show in the 24 hour set up period.
  • A test card (ex. 411111...) was used on the account.
  • ETC (Electronic Ticket Capture) needs to be set as ETC Type 7 (terminal based settlement) as opposed to ETC Type 3 (host based settlement). (This isn't a gateway setting, they will need to Contact First Data Omaha to change).
  • If this is only happening on specific cards, they will need to contact FDMSO to determine why this message was returned.
• INVALID CARD #
  • Merchant received a INVALID CARD # when trying to use a prepaid chase card on Omaha.
  • Unsure if they take this type of card.
  • The card# passed our LUHN10 Validation, however the Issuer believes this to be an invalid credit card number.
  • Have the customer verify their information or contact their card issuer for more information.

 TSYS:

• Bad Bin or Host disconnect
  • Check VAR: Check VAR data against the processor configuration in the gateway to confirm there are no entry errors.
  • Check settlement type: Check with TSYS to make sure the setup is terminal based settlement. Can get this message when the account is set up as host based settlement.
  • SSL Flag: The SSL flag should be set to 'Y'.
  • Merchant Category: A bad 'Merchant Category' can return this message.
  • Check BIN: It could literally be a bad BIN, or a mistypes BIN (Bank ID #) on the VAR sheet.
• Re-enter transaction
  • Check Zip Code/Address Info under Merchant Information Section (or within the processor config): Check the basic data entered for the merchant; in this case the merchants zip code was only 4 digits and when the trans was entered it came back as a failed trans; re-enter transaction.
    • Zip entered as "OH" caused same error
    • Had a merchant getting this error, their Zip was ok. However, the State was spelled out in the configuration [check "More fields..." in the pencil]. Two letter state "AL, IL, PA etc" is needed. Either delete the field or replace [for example "Tennessee" with "TN"], or delete the field from the processor pencil and it will be pulled from the profile... and their transactions started working. 
• Transaction not permitted by issuer
  • Occurs on 'Validate' transactions. Root cause unknown. Have heard on other processors that the acquiring bank can be an issue, but not sure if that is the case here.
  • Apparently can also happen on transactions where TSYS is not able to run the card. Seems this may be the case when the card cannot be run in that specific currency.
• Activity Limit Exceeded
  • This is a decline message that means the credit card being used has reached it's limit. Frequently seen if a test card is used on a live account.
• Daily Threshold Exceeded
  • There can be a daily limit set at TSYS for a merchant, will see this response when they've gone above it. (May be setup error rather than real limit). Need to follow up with processor.
• For other useful articles, click the link below to access NMI Web Support Center
  • NMI Support Center

General Transaction Authorization Response Codes:

Response code	Authorization response message	Response definition	Action
00	APPROVAL	Approved and completed	Nothing to do, transaction was successful.
01	CALL	Refer to issuer	The issuing bank prevented the transaction. Ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
02	CALL	Refer to issuer-Special condition	The issuing bank prevented the transaction. Ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
03	TERM ID ERROR	Invalid Merchant ID	The issuing bank prevented the transaction. Ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve. If this is happening on multiple different cards, contact Client Services to make sure your terminal/POS is set up properly.
04	HOLD-CALL	Pick up card (no fraud)	The issuing bank prevented the transaction. Ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
05	DECLINE	Do not honor	The issuing bank prevented the transaction. Ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
06	ERROR	General error	The issuing bank prevented the transaction. Ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
07	HOLD-CALL	Pick up card, special condition (fraud account)	The issuing bank prevented the transaction. If it’s for a one-time transaction, do not run the card again, and don’t provide any more goods or services for the cardholder. If it was a recurring or scheduled transaction, follow up with your customer to make sure your business wasn’t incorrectly flagged as fraudulent. Ask that they follow up with their bank or update their account with a newly provided card.
12	INVALID TRANS	Invalid transaction	The transaction you’re attempting is invalid — e.g. refunding a refund. Make sure you’re transacting the right payment types and try the transaction again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
13	AMOUNT ERROR	Invalid amount	The number field you attempted to transact was invalid. This usually is the result of a typo (negative amount or ineligible symbol). Double-check what you entered and try the transaction again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
14	CARD NO. ERROR	Invalid card number	The card number is invalid, and your terminal is having trouble finding the relevant account. Double-check the number provided and try again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
15	NO SUCH ISSUER	No such issuer	The card number entered is incorrect. Double-check the number provided and try the transaction again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
19	RE ENTER	Re-enter transaction	An unknown error occurred. Try it again, and if it continues, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve. If this happens with multiple different cards, contact Client Services.
25	NO CARD NUMBER	Unable to locate the account number	The card number is invalid, and your terminal is having trouble finding the relevant account. Double-check the number provided and try again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
28	NO REPLY	File is temporarily unavailable	An unknown error occurred. Try it again, and if it continues, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve. If this happens with multiple different cards, contact Client Services.
39	NO CREDIT ACCT	No credit account	The account that card number is associated with can not be found. Double-check the number provided and try again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
41	HOLD-CALL	Lost card, pick up (fraud account)	The issuing bank prevented the transaction. If it’s for a one-time transaction, do not run the card again, and don’t provide any more goods or services for the cardholder. If it was a recurring or scheduled transaction, follow up with your customer to make sure your business wasn’t incorrectly flagged as fraudulent. Ask that they follow up with their bank or update their account with a newly provided card.
43	HOLD-CALL	Stolen card, pick up (fraud account)	The issuing bank prevented the transaction. If it’s for a one-time transaction, do not run the card again, and don’t provide any more goods or services for the cardholder. If it was a recurring or scheduled transaction, follow up with your customer to make sure your business wasn’t incorrectly flagged as fraudulent. Ask that they follow up with their bank or update their account with a newly provided card.
46	CLOSED ACCOUNT	Closed account	The account that card number is associated with is showing as a closed account. Double-check the account number given and try again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
51	DECLINE	Insufficient funds	The customer’s issuing bank has denied the transaction because either the customer is already over their credit limit or that transaction will put the customer’s credit card over the limit. Either ask the customer to call their issuing bank and request a credit limit or request a different form of payment.
54	EXPIRED CARD	Expired card	The expiration date entered is in the past. Double-check the number provided, ask the customer to confirm the expiration date with their issuing bank, or request an alternate payment method.
55	WRONG PIN	Incorrect PIN or Invalid PIN	The pin number entered was not correct, retry the transaction and have the customer enter their PIN again. If they did not enter one, the issuing bank may be requiring a PIN. Try again and ensure they enter the PIN.
57	SERV NOT ALLOWED	Transaction not permitted-Card	This code will appear if you are attempting a transaction and your customer’s card is not configured for that type of transaction. Have your customer call their issuing bank (the number is typically printed on the back of the credit card) and ask that the transaction be permitted. When the bank confirms it will process correctly, attempt the transaction again.
58	SERV NOT ALLOWED	Transaction not permitted-Terminal	This code will appear if you are attempting a transaction and your merchant processing account is not properly configured. Contact Client Services to make sure your terminal/POS is set up to receive the type of payment you’re attempting.
59	SUSPECTED FRAUD	Suspected fraud	The issuing bank prevented the transaction. If it’s for a one-time transaction, do not run the card again, and don’t provide any more goods or services for the cardholder. If it was a recurring or scheduled transaction, follow up with your customer to make sure your business wasn’t incorrectly flagged as fraudulent. Ask that they follow up with their bank or update their account with a newly provided card.
61	EXC APPR AMT LIM	Exceeds approval amount limit	The customer’s issuing bank has denied the transaction because either the customer is already over their credit limit or that transaction will put the customer’s credit card over the limit. Either ask the customer to call their issuing bank and request a credit limit or request a different form of payment.
62	DECLINE	Invalid service code, restricted	This code will appear if you are attempting a transaction and your customer’s card is not configured for that type of transaction. Have your customer call their issuing bank (the number is typically printed on the back of the credit card) and ask that the transaction be permitted. When the bank confirms it will process correctly, attempt the transaction again.
63	SEC VIOLATION	Security violation	The issuing bank prevented the transaction. If it’s for a one-time transaction, do not run the card again, and don’t provide any more goods or services for the cardholder. If it was a recurring or scheduled transaction, follow up with your customer to make sure your business wasn’t incorrectly flagged as fraudulent. Ask that they follow up with their bank or update their account with a newly provided card.
65	EXC W/D FREQ LIM	Exceeds withdrawal frequency limit	The customer’s issuing bank has denied the transaction because the customer has exceeded the amount of transactions that can take place on their account. Either ask the customer to call their issuing bank and request a credit limit or request a different form of payment.
75	PIN EXCEEDED	Allowable number of PIN-entry tries exceeded	The pin number entered incorrectly too many times. Ask the customer to call the bank to discuss how to resolve.
78	NO ACCOUNT	Blocked, first used transaction from new cardholder, and card not properly unblocked	The issuing bank prevented the transaction. Ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
CV	FAILURE CV	Card Type Verification Error	This usually means that your account is not set up to take that form of payment. Contact Client Services to update your account.
HV	FAILURE HV	Hierarchy Verification Error	This usually means that either your device or account needs to be updated, contact Client Services.
N4	DECLINE	Exceeds issuer withdrawal limit	The customer’s issuing bank has denied the transaction because either the customer is already over their credit limit or that transaction will put the customer’s credit card over the limit. Either ask the customer to call their issuing bank and request a credit limit or request a different form of payment.
N7	CVV2 MISMATCH CVV2	Value supplied is invalid	The issuing bank prevented the transaction because the CVV was not entered or was entered incorrectly. Double-check the information provided and try again. If the transaction declines again, ask for a separate card to complete the transaction and/or ask the customer to call the bank to discuss how to resolve.
V1	FAILURE VM	Daily threshold exceeded	This usually means that you have exceeded your daily Authorization limit. Contact Client Services to resolve.