Card token payment process
Customer
Customer initates a purchase on a website/app via the Saved Card feature
Plural Tokeniser
Encrypts the sensitive card details into a ‘Token’ that is mapped to a business and the actual saved card network.
Business
Collects the token and Token authentication verification value (TAVV) from the Token Requestor as per customer's request for authorisation
Acquiring bank
Processes token to the card network
Card network
Converts token to PAN and passes it to the issuing bank
Issuing bank
Authorises the request and sends a response to the card network
RBI - compliant card tokenisation solution for zero business disruptions
As per RBI guidelines, businesses and payment aggregators are prohibited from storing customer card details. Plural's card tokenisation solution replaces sensitive customer data with a token, making businesses 100% RBI compliant.
Saved cards feature for faster
customer checkout
Offer repeat customers the option to save card details for faster checkout and seamless customer experience.
Our Library

Plural Tokeniser Demystified: Everything you need to Know about tokenisation!
RBI recently published a mandate that Merchants, Payment Gateways(PGs) and Payment Aggregators(PAs)

RBI guidelines and Tokenisation: All you need to know
RED ALERT! Cart abandonment rates in India are as high as 75% in some industries! That’s a HUGE loss for..

Payment gateway security: 7 ways to secure your payments
A report by Business Standard stated that, on average, 100 million online transactions are conducted
Frequently asked questions
What is the RBI guideline regarding card tokenisation?
What is tokenisation?
How does card tokenisation work?
Who can save cards as per RBI guideline?
Is customer consent required for saving cards?