Tokenization - Payment page merchants

📘

Card Tokenization on Juspay Payment Page SDK

The Juspay Payment Page will provide complete support for Card-on-File tokenisation. Please reach out to your Juspay KAM or write to [email protected] for getting this enabled.

There will be no additional Tech effort required at your (merchant) end. The changes will be fully managed by Juspay Payment Page.

RBI guideline has mandated that from Jan 2022 the only way to store cards is via Tokenization.
Juspay's tokenization platform is integrated with the Major Networks - VISA, MasterCard & Rupay, and is ready to transition you to token based transactions.

Through the document, we will go over the user flows impacted by the guideline. Below are the key mandates by RBI on Tokenization:

• Token should be unique to Customer, Card, Token Requestor and Merchant
• Explicit Consent and AFA is mandatory before Token generation
• Only last 4 digits of a card & issuer name can be stored by Merchants, PA/PGs
• Merchant must give cardholder an option to de-register

Tokenization is the process by which the Card Number is replaced with a surrogate value called Token. This token is scoped to a Merchant, Customer & Token Requestor ensuring a more secure payment experience. Every entity to the left of Network will transact using a token and the entities to the right will have card details. Each token is also unique to the Network provider.

Once enabled, Juspay will automatically manage consent for your customers.

In current transaction flow, user will be asked for tokenization consent on the webpage before the bank page loads. Consent page would support both mobile and web form factors.

The same consent page will be shown for both saved card and new card user journeys.

📘

Enabling Tokenisation

Please contact your Juspay KAM to enable Juspay managed consent and tokenization configurations