The cardholder name field isn't utilized in any reporting within Clover. The only field that shows up in exported reports is the Customer Name field, which pulls from the created customer profile in Clover. For Virtual Terminal merchants, the problem is, it's quite a few extra steps for a merchant to create and save a customer profile, when the name is already also being typed in the cardholder name field. So, within Clover, if the merchant wants to see a customer name on the receipt, or in the exported transaction listings, they're typing the cardholder name info and they create a new customer profile each time, so the customer name DOES show up on reports. We'd like Clover to look at adding the cardholder name to Clover reporting, for example - the exportable transaction report.
Erin Davis
supported this idea
·
The cardholder name field isn't utilized in any reporting within Clover. The only field that shows up in exported reports is the Customer Name field, which pulls from the created customer profile in Clover. For Virtual Terminal merchants, the problem is, it's quite a few extra steps for a merchant to create and save a customer profile, when the name is already also being typed in the cardholder name field. So, within Clover, if the merchant wants to see a customer name on the receipt, or in the exported transaction listings, they're typing the cardholder name info and they create a new customer profile each time, so the customer name DOES show up on reports. We'd like Clover to look at adding the cardholder name to Clover reporting, for example - the exportable transaction report.