Procedure to Process Credit Card by Reference ID

There is a feature in Elliott's Credit Card solution to process credit card transactions by using a reference ID. This is a great alternative because then you don't have to store credit card numbers locally, which will make PCI compliance a lot easier to achieve.  You can use this "by reference ID" method to process credit cards if you are using Payware PC or the Payware Connect interface.  Payware PC stores the credit card database in your local server, while Payware PC stores the credit card database in the cloud.  Using Payware PC means you still have to go through the complicated PCI compliance process because credit card numbers are stored in a database locally inside your company's boundary.  On the other hand, using Payware Connect means you don't have to store credit card numbers in your local database.  The credit card data is stored in the cloud by the vendor VeriFone, and it is their responsibility to certify that their system is PCI compliant.

What follows is a sample procedure of how you can charge credit cards by using a reference ID.

When you first process a credit card for a customer, you will have to collect their credit card number.  The following is an example of how to enter a credit card number in our COP Order Billing Screen Payment Window.


However, Elliott does not store this credit card number in its database.  Only the TroutD (reference ID) and the masked credit card number is stored.   If you need to process the credit card for the same customer again in the future, then in the payment window, credit card number field, you can press F8=TrxdID Search.  See sample screen below:


Then you will see the "Select Payware Transaction" window, which shows up like the sample screen below:


You can ask customers which credit card to use by referencing the last 4 digits of the credit card number.  Press Enter on the highlighted transaction, and the system will return the TroutD to the payment window to complete the credit card processing:


Again, this method allow you to charge a credit card the second time even though you did not ask the customer for the credit card number during the second transaction. The credit card number is not stored locally in the Elliott database. You can use this reference ID method to perform the following types of credit card transactions:

  • Sales
  • Pre-Authorization
  • Complete
  • Void
  • Refund
You can process credit cards using a reference ID for up to 6 months.  If you have not processed any credit cards for a customer within a 6-month period, then you will have to ask them for their credit card number the next time they place an order.

If you don't process credit cards through the COP side, you can also collect and process credit cards on the A/R side through AR -> Processing -> Credit Card Transaction Handle.  The procedure is similar to above.

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