Feature - Online Credit Card Interface Level 2 Support

Feature - Online Credit Card Interface Level 2 Support

Release Date: 9/12/2018

In Elliott V8.28.912, we started to support online credit card interface with Level 2 support.  This will result in better credit card merchant rates for qualified transactions.  In order to do that, Elliott needs to send the following information to the credit card  processing payment gateway:
  • TAX_AMOUNT
  • CUSTOMER_CODE
  • PURCHASE_ID
  • INVOICE
  • TICKET_NUM
You can find this information in the following log file <ElliottRoot>\Log\<CompanyNo>\XML2PWC.LOG. The following is a sample of this file:

2018/08/01 10:11:04.158 Connect : https://prod1.ipcharge2.net/ipchapi/rh.aspx
2018/08/01 10:11:04.159 Request : <TRANSACTION><FUNCTION_TYPE>PAYMENT</FUNCTION_TYPE><PAYMENT_TYPE>CREDIT</PAYMENT_TYPE><COMMAND>SALE</COMMAND><USER_ID>APIuser</USER_ID><USER_PW>********</USER_PW><CLIENT_ID>18940800010001</CLIENT_ID><MERCHANTKEY>*****************</MERCHANTKEY><TRANS_AMOUNT>600.00</TRANS_AMOUNT><TAX_AMOUNT>0.60</TAX_AMOUNT><CUSTOMER_CODE>KELLY</CUSTOMER_CODE><PURCHASE_ID>KELLY</PURCHASE_ID><CARDHOLDER>KELLY YU</CARDHOLDER><INVOICE>B0556</INVOICE><TICKET_NUM>B0556</TICKET_NUM><ACCT_NUM>480213*******2338</ACCT_NUM><EXP_MONTH>**</EXP_MONTH><EXP_YEAR>**</EXP_YEAR><CVV2>***</CVV2><CUSTOMER_STREET>505 S. Yorbita Rd.</CUSTOMER_STREET><CUSTOMER_ZIP>91744</CUSTOMER_ZIP></TRANSACTION>

We implemented Level 2 support by always sending these fields regardless of whether you enter the information through the Elliott user interface or not.  In some situations, when the information for the field is not available, Elliott will assume and pass something to the payment gateway anyway to ensure qualifying for the Level 2 transaction rate.

TAX_AMOUNT: This is calculated. For many reasons, this may not be the final tax amount. If there is no sales tax for the transaction, we calculate the tax amount as 0.1% of the transaction amount. This is necessary in order to qualify Level 2 merchant rate. If we should send tax amount as $0.00 for sales tax exempt transaction, then that transaction will not qualify for Level 2 merchant rate.  This is a strange rule made by Visa and Master.  Keep in mind that TAX_AMOUNT field is used for reference purposes only and at this moment, we are not aware any negative issue associate with this special logic.  

If for any reason, you should like to turn off this feature, you can go to Elliott Global Setup -> Add-Ons -> On-Line Credit Card Processing, and answer "N" to the following flag:
    15. Send Min 0.1% Tax to Qualify Level 2?


CUSTOMER_CODE: If a PO# is available (entered), that will be passed in this field. Otherwise, Customer Number will be used.

PURCHASE_ID: If a PO# is available (entered), that will be passed in this field.  Otherwise, Customer Number will be used.

INVOICE: If a TicketNo is available (entered), that will be passed in this field.  Otherwise, Customer Number will be used.

TICKET_NUM: If a TicketNo is available (entered), that will be passed in this field.  Otherwise, Customer Number will be used.

This change does not apply to Elliott 7.5.  If you want to qualify for better credit card merchant rates, you should update to Elliott 8.2 or after.


EMK


    • Related Articles

    • Feature - Online Credit Card Interface Level 3 Support

      Release Date: 4/21/23 Revised Date: 12/20/23 Version: 8.5 and Above Introduction Elliott currently supports credit card level 2 transactions. This means, in addition of passing the credit card number, expiration number info when charge a credit card, ...
    • Credit Card Processing Error: Chk Viawarp For Dupl

      Q - In A/R -> Processing -> Credit Card Trx Handle, at field "21. Approval No," I press F4 to interface with the credit card payment gateway server, then I receive the message "Credit: AP Error: Chk Viawarp For Dupl." See examples below: When I go to ...
    • Credit Card Transaction Time Out

      Q - When I process a credit card transaction in Elliott, I receive a message window with the title "Finished Transaction Status" and the detail message like followings: E:System.Net.WebException: The underlying connection was closed: A connection ...
    • Avalara Attribute Support

      Release Date: 4/28/23 Updated: 1/26/28 Version: 8.6 and Above For Elliott to work with the Avalara Sales Tax Interface, there are additional data to be stored on the Elliott side. Our implementation chooses to store these data in the following ...
    • Credit Card Processing Frequently Asked Questions

      Q - If a customer wants to give us new CC information for their next order or a new Expiration date and Sec # for a CC that has been used recently, is there a way to enter that information at that time if we do not have an order to process? A - You ...