Quantcast StorefrontBacktalk » Blog Archive » Tokenization, Meet Account Updater
advertisement
advertisement

Tokenization, Meet Account Updater

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

Some six years after both MasterCard and Visa enabled retailers to automatically update credit card information—a capability that many chains never opted to use—Cybersource on Monday (Oct. 19) said that it is automating that process for its customers but added a nice twist: It would automatically update the tokens that replaced the changed cards.

This approach isn’t much of a technological innovation. All the vendor is doing is adding a script that leverages the data the brands have been offering for years. But it’s a script that no one else has yet bothered to create. That said, given the number of retailers that never chose to use the original services, it’s unclear how many will jump at this new feature.

The original card brand programs—the Visa Account Updater (VAU) and MasterCard’s Automatic Billing Updater (ABU)—were set up so that when an expiration date changed or a card number was replaced, the retailer could be automatically notified so that the customer—especially those on recurring billings—didn’t have to be bothered or disrupted.

Todd Ablowitz, president of the Double Diamond Group and a payment consultant (who has no ties to Cybersource—at least none that we could find), said he thinks the move is logical and has strong potential.

“My favorite type of product release is the ‘a-ha’ product release, like this one. All the ingredients have been here for years. Consumers hate getting that nasty-gram from a recurrent biller saying that their card—which was probably cancelled due to fraud, a lost card or a data breach—was declined,” Ablowitz said. “The card brands rolled out updater services years ago, allowing retailers to avoid that awful customer experience. The only problem is that it appeared no one was using them. Now there’s a service that not only includes the account update service and automates it, but it’s integrated into their tokenization process. That means the retailer never needs to see the differences in their card info. To me, that’s powerful.”

What the vendor is stressing is the tokenization integration. Cybersource is arguing that other services would likely force retailers to detokenize (is that a word?) their tokens before they could be updated, which would briefly create a security problem because the full card data would again be in the clear.

Of course, this approach only works if the customer is already paying for Cybersource tokens. Also, even Cybersource officials are not suggesting that this is rocket science, so it’s likely that others will follow if this program gets any traction.


advertisement

2 Comments | Read Tokenization, Meet Account Updater

  1. Toby Galino Says:

    You neglected to mention that hefty charge you got hit with for having a late recurring payment – even if it was just an expiration date change. That use to steam me up, it was an annual phone call for my club memberships.

  2. Cecille Soriano Says:

    It would really be good if they’ll do it as added service not another way of cashing in on customers like me.

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...