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 can pre-authorize the new credit card for $0.01 or $0.00 depending on your credit card processor.  If your credit card processor supports $0.00 pre-auth (e.g., TSYS, Paymentech, Elavon), then you should use this option.  If your credit card processor (e.g., First Data North/Cardnet) does not support $0.00 pre-auth, then you should pre-auth for $0.01 instead.  In that case, you should go to Global Setup ->  Add-on -> On-Line Credit Card Processing, and change the flag "14. Change $0.00 PreAuth to $0.01?" to "Y." Then the system will convert $0.00 pre-auth to $0.01 automatically.

Q - How long with the pre-authorized transaction stay valid before the transaction is completed?

A - This depends on your credit card processor.  Some credit card processors keep it valid for 30 days, and some keep it valid only for 7 days.  This is something you should find out from your credit card processor.

Q - What if we process a CC order for a customer and the CC is used only one time, not on any future orders. In the past we would go in and delete that CC information. With the new system, since we cannot delete, how do we know not to use that CC on the next order? In the past we would use the most recent CC that had been processed.

A - You should verify with your customer if they wish to charge to their credit card ending with ****1234 …etc.

Q - When processing a CC and entering F8 to pull up the CC info to use on a new order, I noticed that when the CC info. appears on the screen, the Sec# does not appear. Is this for security reasons? How do we know that the sec code has actually been stored?

A - EMK: It is against security protocol to store the 3- or 4-digit security (CVV2) code. Credit card companies specifically ask us not to store that information in the database. From the fraud prevention point of view, you only need the CVV2 to verify if the credit card is legit when you process the card for the first time. Once that transaction is successful, it means this credit card is good. Therefore, you don’t need the CVV2 to determine if the card legit for future charges when you reference by TroutD.

Q - When processing a CC order on the COP side the payment is attached to the order, unlike when processing a CC order on the A/R side. Is there a simple process for attaching the payment to the order on the A/R side?

A - It is simpler to process a credit card payment on the COP side directly. But in some situations you may consider processing a credit card on the A/R side: (1) Security concern – you want to limit the number of employees in your company who can process credit cards; (2) Sometimes you may need to charge a credit card before you even get the order; (3) Sometimes a credit card payment is not for a specific order or invoice.

Q - When entering CC information on the COP side, the system does not prompt you for the address, as it does when you enter the info. in A/R. I was told that if the address was not entered you get charged a higher CC fee. Is this true? Is there a way to enter the address on the COP side?

A - By default, the COP side assumes the order ship-to address is the credit card address. You should verify with the customer if the credit card address matches the ship-to address.  If that is not so, you could override it after you enter the credit card number. When the cursor is at “Exp” field, you may press F5 to modify credit card defaults. See attached sample screens.


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