This article is to help you identify what different errors you may encounter when taking payments and some steps to take when encountered. This article will have details regarding the most popular error responses that we have seen on LA Pay, but may not cover all of them. For a list of all the errors that we have please view the Limo Anywhere PAY Error Responses article.
Merchant Track will be mentioned in throughout this article, please see this article on how to access Merchant Track
1020 Declines
These declines can happen due to numerous reasons. When a 1020 decline does occur, I would suggest checking Merchant Track directly on how to identify what type of decline has taken place. In any case, if you get this 1020 decline error, DO NOT try the card more than 3 times within 24 hours. Doing so could raise red flags with the processor and card brands which could impact your ability to continue processing transactions.
- Generic Authorization Declines
- This is just a generic decline.
- Suggestion: You should reach out to the cardholder and check if they know or have them check with their card issuer/bank on what the reasoning for the decline may be. We suggest re-entering in the credit card data or sending a request payment link for the customer to enter in the card info themselves.
- Suspected Fraud Declines
- Suggestion: You should reach out to the cardholder and check if they know or have them check with their card issuer/bank on what the reasoning for the decline may be. We suggest re-entering in the credit card data or sending a request payment link for the customer to enter in the card info themselves.
- Exceeds Withdrawal Limit
- This error means that the transaction will bring the customer’s bank balance below the limit set by their bank or they have exceeded their transaction limit for that day.
- Suggestion: You should reach out to the customer and advise them and may need to get another method of payment.
- Insufficient Funds
- This means there were not enough available funds to process the payment.
- Suggestion: You should reach out to the customer and advise them and may need to get another method of payment.
1101 Errors
- 1101 – Processor invalid data response – INVALID CARD INFO
- This means something regarding the card information has been detected as not being valid.
- Suggestion: We suggest re-entering in the credit card data or sending a request payment link for the customer to enter in the card info themselves.
10 Errors
When an error 10 is displayed this can be for many different reasons.
- Error: Payment Gateway Conflict: Error Code – 10. The request did not pass validation and could not be processed.
- Example: The CardNumber field is not a valid credit card number.” “The field CardNumber must be a string with a minimum length of 12 and a maximum length of 19.
- Suggestion: We suggest re-entering in the credit card data or sending a request payment link for the customer to enter in the card info themselves.
1103 Errors
- Error: Payment Gateway Conflict: Error Code – 1103. Fullsteam received an Invalid Request response from the processor.
- This can occur when some data is deemed invalid by the processor.
- Suggestion: Check the credit card data you have entered, including the billing address. This is most commonly an issue with how the billing address has been entered.
- For example:
- The entire address has been entered in on Address Line 1.
- They place the Suite# or Apt# in Address Line 1 when it should be placed in Address Line 2.
- The city is in the Address 1 box.
- If all else fails, we suggest re-entering in the credit card data or sending a request payment link for the customer to enter in the card info themselves.
- For example:
