This document provides frequently asked questions regarding the RBI mandate on Card on File Tokenisation (CoFT) effective from October 1, 2022. It explains that merchants can no longer store sensitive card details like card numbers and CVVs, requiring tokenisation for online transactions. Customers can provide consent for tokenisation through merchant apps or websites using an additional factor of authentication. The document clarifies that tokenisation is optional, free of charge, and allows customers to manage tokens via SBI Quick. It also details the differences between suspending and deleting tokens and confirms that tokenisation is secure and unique to each merchant-card combination.

This document provides frequently asked questions regarding the RBI mandate on Card on File Tokenisation (CoFT) effective from October 1, 2022. It explains that merchants can no longer store sensitive card details like card numbers and CVVs, requiring tokenisation for online transactions. Customers can provide consent for tokenisation through merchant apps or websites using an additional factor of authentication. The document clarifies that tokenisation is optional, free of charge, and allows customers to manage tokens via SBI Quick. It also details the differences between suspending and deleting tokens and confirms that tokenisation is secure and unique to each merchant-card combination.