Tokenisation of Card Transactions – Enhancements


Quick Summary
The Reserve Bank of India (RBI) has introduced enhancements to its card tokenisation framework. The existing device-based tokenisation system will now apply to Card-on-File (CoFT) services, and card issuers can act as Token Service Providers. This move aims to bolster card data security and user convenience by requiring explicit customer consent with Additional Factor of Authentication (AFA) for tokenisation, reducing the risk of data breaches from stored card details.

Reserve Bank of India

Date : Sep 07, 2021

Tokenisation of Card Transactions – Enhancements

The Reserve Bank of India (RBI) has today announced the following enhancements to the extant framework on card tokenisation services:

  1. the device-based tokenisation framework advised vide circulars of January 2019 and August 2021 has been extended to Card-on-File Tokenisation (CoFT) services as well, and

  2. card issuers have been permitted to offer card tokenisation services as Token Service Providers (TSPs). The tokenisation of card data shall be done with explicit customer consent requiring Additional Factor of Authentication (AFA).

The above enhancements are expected to reinforce the safety and security of card data while continuing the convenience in card transactions.

Citing the convenience and comfort factor for users while undertaking card transactions online, many entities involved in the card payment transaction chain store actual card details [also known as Card-on-File (CoF)]. In fact, some merchants force their customers to store card details. Availability of such details with a large number of merchants substantially increases the risk of card data being stolen. In the recent past, there were incidents where card data stored by some merchants have been compromised / leaked. Any leakage of CoF data can have serious repercussions because many jurisdictions do not require an AFA for card transactions. Stolen card data can also be used to perpetrate frauds within India through social engineering techniques.

Reserve Bank had, therefore, stipulated in March 2020 that authorised payment aggregators and the merchants onboarded by them should not store actual card data. This would minimise vulnerable points in the system. On a request from the industry, the deadline was extended to end-December 2021 (RBI circular CO.DPSS.POLC.No.S33/02-14-008/2020-2021 dated March 31, 2021), as a one-time measure. RBI has been in regular consultation with the industry to facilitate the transition.

It may be noted that introduction of CoFT, while improving customer data security, will offer customers the same degree of convenience as now. Contrary to some concerns expressed in certain sections of the media, there would be no requirement to input card details for every transaction under the tokenisation arrangement. The efforts of Reserve Bank to deepen digital payments in India and make such payments safe and efficient shall continue.

(Yogesh Dayal)     
Chief General Manager

Press Release: 2021-2022/823

FAQ :

The device-based tokenisation framework has been extended to Card-on-File (CoFT) services, and card issuers are now permitted to offer card tokenisation services as Token Service Providers (TSPs). Tokenisation will require explicit customer consent with Additional Factor of Authentication (AFA).

The enhancements are designed to reinforce the safety and security of card data while maintaining the convenience of card transactions, reducing the risk of card data being stolen from merchants.

No, contrary to some concerns, there will be no requirement to input card details for every transaction under the tokenisation arrangement.

Card-on-File (CoF) data refers to actual card details that are stored by entities involved in the card payment transaction chain, often for customer convenience.

The deadline for authorised payment aggregators and merchants to stop storing actual card data was extended to the end of December 2021.

 

Comments



CCI Pro