To ensure greater security to end customers and lower the risks of cyber-crimes, the Reserve Bank of India (RBI) passed a mandate prohibiting businesses, payment gateways, and payment aggregators from storing customer card details on their servers.
The deadline, which was earlier set to 30 June 2022, has now been extended to 30 Sep 2022, giving businesses more time to make the required changes.
The RBI has only permitted card networks to store card details while all stakeholders, including businesses, payment gateways, and payment aggregators, must adopt the tokenisation guidelines and have compliant solutions in place by the deadline.
With tokenisation, a customer’s card details would be masked behind a token, facilitating transactions only through the token.
Tokenization is the process of replacing sensitive card data into a form of unique identification token that retain all the essential information about the card data without compromising its security.
Tokenization, which seeks to minimize the amount of card data a business needs to keep on hand, has become a popular way for small and midsize businesses to support the security and compliance with industry standards and government regulations.
Device-based tokens are bound with the card and the device, and the card networks generate the token.
A customer with an HDFC credit card gets it enrolled for a token on his mobile’s Amazon app. In this example, the customer can transact on the Amazon app using his mobile phone only.
Device-based tokens are generally used in NFC based phones where the card details are mimicked onto the NFC chip. E.g. Samsung Pay, Apple Pay, etc and for offline use cases.
Account-based tokens are like saved cards on a specific merchant. The customer needs to log in on the merchant’s app/web platform to continue with the transaction and be interoperable and used across devices.
Plural supports only Account Based Tokenisation / Card on File (COF) Tokenisation.
Stakeholders involved in e-commerce card-on-file tokenisation are,
o Token Requestors
o Card Networks
Largely designed to counter online frauds and curb digital payment breaches, tokenisation comes with a slew of benefits. Some of them are:
Tokens generated will be unique to a single card at a specific merchant and this will take up the overall security of making card-based transactions. It eliminates the risk of storing card details online and ensures the uncompromised convenience of storing your token details on the merchant site.
Tokens can be deleted/updated by issuer in real time. Issuer visibility to where tokens are stored
Tokenised card will also allow you the convenience of quick checkouts as you won't need to punch in your card number for each purchase which helps to achieve better Approval Rates. Save your card once and you'll have the ease of transaction at all times.
Many times, your legitimate online payments using your valid cards are declined on the grounds of the transaction looking like a fraud. With tokenisation, this becomes a thing of the past as the usage of tokens for payments confirms security of the highest order.
With tokenisation, unique cryptogram verified for every transaction.
Tokens are issued to merchant for a particular use case. Cannot be used outside domain
‘Tokenization’ might significantly disrupt the existing merchants’ platform since it needs to develop a system that supports tokenised transactions (PCI-DSS merchants only). However, their functionality will remain unchanged for small merchants (redirect model).
Merchant will need to partner with card networks or leverage payment aggregators to have a ‘save card details’ feature for existing and future customers.
According to CII's Media and Entertainment Committee, this could lead to 20-50% of revenue losses for businesses that fail to comply by the deadline.
Not just businesses, an estimated 5 million customers who have stored their card details on ecommerce and online stores could also face difficulties if the online platforms/businesses they frequently visit have not made the changes to their backend.
Imagine that for each purchase customers make, they need to input the card number, name, expiry date, CVV. This hassle may cause customers to abandon cart & drop off if the business has not made the changes on the backend
- Customer saves card details at merchant site or initiate the purchase transaction and provide the consent to save card
- Merchant does penny drop transaction or purchase transaction to authentication and authorization the card.
- Post successful authentication and authorization of the Penny drop transaction or purchase transaction, merchant request to tokenise the card to Plural tokeniser
- Plural initiate the enrolment request to network for card tokenisation
- Network validate the request and create card token and cryptogram and sends back to Plural
- Plural generate the token reference id and map it with token, merchant, customer details
- Plural sends the token reference id back to merchant for repeat transaction to fetch the token, cryptogram (TAVV) and other token details
- Consumer initiates purchase on the merchant platform via saved card.
- Merchant fetches the token, cryptogram (TAVV) and other token details from the Plural Tokenizer to perform authentication.
- Plural Tokenizer fetches the token, cryptogram (TAVV) and other token details from Network and send the details back to merchant
- Merchant initiates the authentication request to Plural PG to process the token payment
- Plural PG forwards the authentication request to Acquirer and network
- Network converts the token to PAN and passes to issuer
- Issuers authenticate or decline the transaction and send the response back to Network
- Network forwards the response back to Acquirer and Acquirer back to Plural
- Plural forwards the response back to Merchant and Merchant forwards the final response back to customer
External Tokeniser for Token Provisioning and Plural as Payment Aggregator for Token Payment Processing
When a consumer initiates purchase on an online transaction with consent to save card, post successful authentication and authorization the external token service integrates with respective network to tokenise the card and notifies the token reference merchant. Payment processing of the tokenised card can be done by plural and merchant will work with the external token service to get the token related information like token, cryptogram, and expiry.
Plural Tokeniser for Token Provisioning and Plural as Payment Aggregator for Token Payment Processing
When a consumer initiates purchase on an online transaction with consent to save card, post successful authentication and authorization Plural Tokenizer integrates with respective network to tokenise the card and notifies the token reference merchant. Payment processing of the Tokenised card can be done by Plural in conjunction with Plural Tokenizer to get the token related information like token, cryptogram, and expiry.
When a consumer initiates purchase on an online transaction with consent to save card, post successful authentication and authorisation, Plural Tokenizer integrates with respective network to tokenise the card and notifies the token reference to merchant. Payment processing of the tokenised card can be done by any of the merchant specific payment aggregator and merchant will work with Plural Tokenizer to get the token related information like token, cryptogram and expiry.
When a consumer saves card at merchant web/app, Plural Tokenizer integrates with respective network directly to the network specific gateways or third-party gateways to tokenise the card and notifies the token reference to merchant.
Updated over 1 year ago