Tokenization in 2022?

 Our credit card details get stored in more and more places (digital and physical). And periodically we hear of hackings e.g. Domino’s India (1 million card details) and Marriott hotel (exposed 500 million guest records worldwide). But what alternative do we have? In theory, we could key in the card details for each transaction (and turn off the “save card details” option), but that’s too painful…

 

In India, the RBI has come up with a solution - “tokenization”. Setting aside the delay (from 1-Jan to 30-Jun), let’s look at what tokenization means, and how it would help with the data hacks risk.

 

Here is how tokenization would work:

  1. You install the app for the site e.g. Amazon, Myntra, whatever.
  2. When it comes to making the payment, you do not enter your card details. Instead, when you click the payment button, the app places a request to the credit card company (VISA, MasterCard etc) to initiate the payment.
  3. The card company then generates a one-time, unique “token” ID, based on a combo of your card details (which the card company anyway knows) + merchant (Amazon, Myntra) + amount, that is sent to the site.
  4. An OTP is sent to your phone to confirm the payment.

 

With this method, the site doesn’t need your credit card details; and won’t be allowed to ask for them either. How about sites where the card details were already saved? They have to erase the card details from their records. The net result? If the site doesn’t have your card details, there’s no risk to you even if that site gets hacked.

 

Operationalizing this though needs a few steps. First, we would need to link our credit card details to Aadhar (this is to allow the phone to link to the card number, the same way GPay or PayTM links to the bank a/c). Second, this system can only work via the phone and/or tablet, as per RBI guidelines (But this doesn’t seem like anything new to me. After all, even today, the OTP for your online transactions comes to the phone). Third, the credit card companies need to implement this capability (This is something the government can force since it would be the law). Lastly, the various websites need to implement the software to send and receive the “token” from the credit card company.

 

It is the last step which has caused the delay. Not all sites, esp. the smaller players, find it practical or affordable to implement such a software capability. But I am guessing (and hoping) this won’t be insurmountable – it could be solved by the creation of an intermediary who can provide this service (for a fee, probably) to all sites that can’t implement it on their own.

 

Even if the rollout has gotten delayed, this sure sounds like a good step in addressing the risks and concerns of sharing one’s credit card details.

Comments

Popular posts from this blog

Student of the Year

Animal Senses #7: Touch and Remote Touch

The Retort of the "Luxury Person"