Does Elliott Support Credit Card Pre-Authorization Transactions?

Release Date: 07/17/2020
Version: 8.0 & up

QWe are doing more and more credit card charges lately, which is also increasing the amount of adjustments that need to be made to order totals. Do you have a way to "pre-charge" a card for a number of days but do the actual charge later for a totaled order amount?

For example, we have an order for $100 that gets charged on Monday for a shipment on Wednesday. As we load the shipment on Wednesday, we have to short ship the order by $20 due to inadequate inventory. We go into Elliott and modify the order total to be $80. Does an easy way exist to update the credit card to only charge the $80?

A - The short answer is “YES.

In Elliott Credit Card Processing, we support the following transaction types:
  • Sales
  • Refund
  • Void
  • PreAuth
  • Complete
  • Force
You have been using “S=Sales” transaction in the past.  The "Pre-Charge"  transaction you refer to is called “Pre-Auth.” To perform Pre-Authorization, in whatever credit card processing screen where it prompts you for “Trx Type,” you will choose “P=PreAuth.” See sample screen below:

This is like charging a credit card, but it just allocates the amount of that credit card. You will get an approval number back. The transaction does not create any accounting record in Elliott Business Software. But it will create a record in Credit Card Log History for future reference.

When you are about to charge the final amount to this credit card, where the system prompts you for the credit card number, you can use the “F8” key. See sample screen below:

The credit card log history will then be displayed:

Select the corresponding Pre-Authorized transaction, and the transaction type will default to “C=Complete.”  Accept it.  Then you can change the credit card amount if it turns out to be  different.  Please see also see the following KB article for more details:

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