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

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:
<INVOICE>SOCOMP</INVOICE>
<PAYMENT_MEDIA>VISA</PAYMENT_MEDIA>
<RESPONSE_TEXT>Input parameter INVOICE assigned invalid value</RESPONSE_TEXT>


EMK

    • Related Articles

    • Invalid Tran Counter [99...99] with POINT Interface When Charging a Credit Card

      Release Date: 6/20/19 Version 8.5 Q: I received the following error when processing credit card transactions on a POINT POS device: Sales: FIELD_ERROR Invalid Tran Counter [194] See sample screen below: What do I do? A: Typically, when you receive an ...
    • How to Charge a Credit Card If Pre-Authorized for the Wrong Customer

      Q - We tried to complete a credit card charge with a pre-authorization for the wrong customer. Since we don't keep the credit card number when we do the pre-authorization, how do we go about completing the credit card charge for the correct customer? ...
    • How to Process a Force Credit Card Transaction

      In Elliott, we support the following types of credit card transactions: Sales Refund Void PreAuth Complete Force Force is a special transaction in credit card processing. You will use the force credit card transaction when you can't get authorization ...
    • How to Handle and Prevent Credit Card Duplicate Charges

      Release Date: 08/31/2018 How Did Credit Card Duplicate Charges Happen? Most of the time, duplicate credit card charges are caused by network (Internet) error. Elliott online credit card processing utilizes Payware Connect as the payment gateway. If ...
    • Feature - HTML Credit Card Email Receipt Using PDF PostOffice

      Release Date: 2/27/2023 Version: V8.5 (partial support), V8.6 & Up (full support) Background Before this update, credit card receipts were text-only documents, like the one here, that could be printed on paper, sent to disk. While the receipt can be ...