What Is the Credit Card Authorization Member Field for?

Release Date: 07/21/20
Version: 7.5 & above

Q - We don't know what this field means or if we should do something with it when running credit cards. In the screenshot below, that name in the Member field does not match the name of the credit card holder as show in the "reference" field. What does the "Member" field mean and where does that value come from?

AThere are a few areas that may affect the “Member” information:
1. If you are doing POS (Point of Sales) and swipe or chip the credit card, the member information comes from the credit card. This scenario may not apply to you.
2. For non-POS scenarios, if you use the F7 key at the credit card number field to look up a stored credit card in eContact, then that information is the eContact credit card billing information which defaults to the eContact name.
3. At credit card number field, if you manually enter the credit card number, at the expiration date field you can press the F5 key to modify the credit card parameters. In that screen, there’s a “Card Holder Name.” It defaults to the customer’s contact. But you can override it, and it will become the “Member.” See sample screen below:

4. If you did not use the F5 key to modify credit card defaults, then by default the member is equal to the customer contact when you manually enter the credit card number.
5. If you were using the F8 key at the credit card number field to look up any previous credit card transaction history (sales, pre-authorized, etc.), the system will use the credit card holder stored in the corresponding record in Credit Card Log History (using the same principle noted above in 1-4). In that case, the member defaults to the last history transaction record.

Generally speaking, the "Member" or "Card Holder Name" is not being validated by the credit card processor.  The information we display and store under the "Member" is based on the  above assumptions and is not guaranteed to be the true credit card holder name.


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