Quantcast StorefrontBacktalk » Blog Archive » The Survey Says: 28 Percent Of Retailers Using Payment Data For Non-Payment Functions
advertisement
advertisement

The Survey Says: 28 Percent Of Retailers Using Payment Data For Non-Payment Functions

Written by Evan Schuman
October 8th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

Officially, Visa and other card brands “discourage” retailers from using card data for non-transaction functions such as CRM or other customer identification programs. But many retailers continue to carry out the forbidden practice and to do so openly. And even Visa won’t say that it will punish a retailer caught blatantly doing it.

“We’d work with the acquirer and work with the merchant to try and rectify the situation,” said Jennifer Fischer, a Visa senior business leader who focuses on payment risk issues.

StorefrontBacktalk surveyed our readers this month to get a sense of how widespread the practice is today. We need to stress the unscientific nature of this survey: participants were self-selected, and we have no accurate way of knowing who was really answering the questions. That caveat made, 28 percent of respondents said that they “currently use payment card data for anything other than payment processing, such as for CRM or other customer identification purposes.” An additional 14 percent said “we used to, but don’t anymore” and 48 percent said “we don’t and never did.”

On top of that, some written-in answers suggested that more chains do it, but they try and protect the data.

One write-in, for example, said “Yes, but only in tokenized form.” Theoretically, the rule banning such usage doesn’t have a tokenization exemption. Another reader said that his chain does it, but in a limited way. “The first 6 digits yes, tokenized card number yes, full card number no,” he wrote in. “The first 6 digits = Bank ID = country where issued, which gets compared to country provided by customer and derived from the IP. Tokenized card number is compared with other card tokens.”


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...