Receive "Input parameter INVOICE assigned invalid value" with POS Credit Card Charge

Release Date: 7/23/19
Version: 8.5 & Up

Q - When processing credit card transactions through a point-of-sales terminal (POINT interface), we received the following message:
       Input parameter INVOICE assigned invalid value
And then the credit card transaction was declined. What is causing this?

A - The cause of this problem is because the customer number used in the sales desk is "Alphabetic."  If you change it to "Numeric," then you can avoid this problem.

The nature of the problem is that Elliott passes the customer number as invoice number in our Sales Desk (POS) application. The reason is at the time the credit card is charged, it is before the invoice is printed, so we don’t have the invoice number assigned yet. So we pass the customer number as the invoice number instead. In the previous SIM interface, this was not a problem. With the new POINT interface, it does not like us passing the alphabetic invoice number that’s a duplicate. 

To fix this problem, you will need to create a misc. customer number that’s numeric -- like, for example, 999999, or something similar. If you change the customer# used by POS to a numeric value, then you won’t get this kind of decline problem with the new POINT interface.

The following is sample of XML data in the log file with this error:
<RESPONSE_TEXT>Input parameter INVOICE assigned invalid value</RESPONSE_TEXT>


Credit Card Processing

  1. How to Process a Force Credit Card Transaction?
  2. Credit Card Processing Frequently Asked Questions
  3. Payware PC Server Actively Refuses Credit Card Transaction
  4. Does Elliott Encrypt Credit Card Number in The Database?
  5. How to Reverse Credit Card Sales?
  6. Credit Card Transaction Time Out
  7. Procedure to Process Credit Card by Reference ID
  8. How to Charge a Credit Card If Pre-Authorized for the Wrong Customer
  9. Payware Connect Communication Error
  10. What Happens if Credit Card PreAuth Is Not Followed by Completion?
  11. Credit Card Processing Error: Chk Viawarp For Dupl
  12. What Does Error Code 2029999 Mean in Payware Connect SIMEvent.Log File?
  13. I Receive "A call to SSPI failed, see inner exception" Message During Credit Card Processing
  14. Credit Card Payments in Elliott but Not in Payment Gateway
  15. Feature - Support for Verifone Point Devices with Card Chip Technology
  16. Error with Payware Connect - The remote certificate is invalid according to the validation procedure
  17. How to Find Orders That Have Been Pre-Authorized for Credit Card Charge
  18. Feature - Online Credit Card Interface Level 2 Support
  19. How to Handle and Prevent Credit Card Duplicate Charges
  20. Invalid Tran Counter [99...99] with POINT Interface When Charging a Credit Card
  21. How to Set Up MX915 POS Device for Static Network IP Address
  22. Receive "Input parameter INVOICE assigned invalid value" with POS Credit Card Charge
  23. How to Reprint a Credit Card Receipt
  24. Does Elliott Support Credit Card Pre-Authorization Transactions?
  25. What Is the Credit Card Authorization Member Field for?
  26. Selling Non-Approved Items Can Cause Credit Card Processing TERM ID ERROR

Feedback and Knowledge Base