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

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?

Feedback and Knowledge Base