JUSPAY Unified Dashboard

Batch Card Tokenization

Overview

The Batch Card Tokenization module provides comprehensive bulk card tokenization capabilities for securely tokenizing multiple payment cards simultaneously through CSV file uploads. It offers real-time progress tracking, status monitoring, and detailed reporting for all card tokenization operations processed through the Juspay payment platform with full PCI compliance.

This module is designed for a wide range of users, including:

  • Security Teams: For implementing secure card tokenization at scale and ensuring PCI compliance across all stored card data with comprehensive audit trails.

  • Compliance Teams: For bulk card tokenization processing, regulatory compliance management, and tracking tokenization status across multiple card records with detailed security logs.

  • Payment Processing Teams: To tokenize customer card data in bulk, track tokenization status, and provide secure token-based payment processing for enhanced security.

Accessing the Module

  1. Log in to the Juspay dashboard.

  2. From the main navigation menu on the left, click on Payments.

  3. Select Bulk Operations from the Payments submenu.

  4. Click on the Card Tokenization tab from the bulk operations navigation.

  5. The navigation URL for this module is https://portal.juspay.in/batch/batch-card-tokeniselink icon.

Batch Card Tokenise
Batch Card Tokenise

Step-by-Step Usage Instructions

Creating Batch Card Tokenization

Step 1: Access the Batch Card Tokenization Interface

  1. Navigate to the Batch Card Tokenization module using the steps above.

  2. You will see the main dashboard with a description: "This module helps in creating card tokenization in bulk using a file upload. It provides a holistic view of the files uploaded. Upon clicking the filename in the table below a detailed view of each card tokenization uploaded is displayed."

  3. The interface displays any previously uploaded batch card tokenization files in a table format.

Step 2: Initiate New Batch Card Tokenization Upload

  1. Click the "Create Batch Card Tokenization" button (visible only to users with appropriate permissions).

  2. If maker-checker workflow is enabled for your account, you will first see a description modal:

    • Enter a description for the batch card tokenization request in the text field.

    • Click "Submit" to proceed to the file upload interface.

  3. If maker-checker is not enabled, you will directly access the file upload interface.

Batch Card Tokenise
Batch Card Tokenise

Step 3: Prepare and Upload CSV File

  1. Download Sample File: Click on the sample file link to download the CSV template (batch_card_tokenization_sample.csv).

  2. Prepare Your Data: Fill in your card data following the CSV field specifications (see table below).

  3. File Limitations:

    • Maximum 1000 rows per file

    • CSV format only

    • File size limitations apply

  4. Upload Process:

    • Click "Choose File" or drag and drop your CSV file

    • The system validates the file format and structure

    • Mandatory fields are checked (Card Number, Card Expiry, Customer ID)

    • Column types are validated (Card Number as String, Card Expiry as String in MM/YYYY format, Customer ID as String)

Step 4: File Processing and Validation

  1. File Validation: The system performs the following checks:

    • CSV format validation

    • Mandatory field presence (cardnumber, cardexpiry, customer_id)

    • Data type validation for each column

    • Card number format validation

    • Expiry date format validation (MM/YYYY)

    • Row count validation (maximum 1000 rows)

  2. Error Handling: If validation fails, specific error messages are displayed:

    • Missing mandatory fields

    • Invalid card number format

    • Invalid expiry date format

    • File format errors

    • Row limit exceeded

  3. Successful Upload: Upon successful validation:

    • File is queued for processing

    • Batch ID is generated

    • Initial status is set to processing

    • Card data is securely processed for tokenization

Step 5: Monitor Processing Status

  1. Status Indicators:

    • ACCEPTED: Successfully tokenized cards (Green indicator)

    • FAILED: Failed tokenization attempts (Red indicator)

    • QUEUED: Cards waiting in processing queue (Blue indicator)

Monitoring and Managing Batch Card Tokenization

Viewing Batch Card Tokenization Details

  1. Table View: The main interface displays all uploaded batch files with:

    • File Name: Name of the uploaded CSV file

    • File Upload Status: Current processing status with color-coded labels

    • Total Cards: Number of card tokenization requests in the file

    • Date Created: File upload timestamp

    • Last Modified: Last update timestamp

    • Total Tasks: Number of tokenization requests in the file

    • Tasks Progress: Visual progress bar showing completion status

    • Actions: Sync with Gateway button for manual synchronization

    Batch Card Tokenise - Table View
    Batch Card Tokenise - Table View

  2. Detailed View: Click on any filename to access detailed information:

    • Batch Details Card: Expandable/collapsible interface showing:

      • Batch ID: Unique identifier for the uploaded file

      • Date Created and Date Updated timestamps

      • Total Cards with count formatting

      • Current status with color-coded indicators

    • Progress Statistics: Individual task counts for:

      • Total Accepted Tasks: Successfully tokenized cards

      • Total Rejected Tasks: Failed tokenization attempts

      • Total Queued Tasks: Cards in processing queue

Batch Card Tokenise - Detailed View
Batch Card Tokenise - Detailed View

Search and Filter Capabilities

  1. File Name Search:

    • Use the search input field with search icon

    • Enter filename to filter results

    • Search is case-sensitive and supports partial matches

    • Clear search using the cross icon

  2. Table Sorting:

    • Click column headers to sort data

    • Available sorting for: File Name, Status, Total Cards, Date Created, Total Tasks

    • Toggle between ascending and descending order

Data Export and Download

Downloading Processed Data

  1. Access Download: Click the "Download Data" button in the batch details view.

  2. CSV Export: Downloads include:

    • Serial numbers (S.No column)

    • All processed card tokenization data with the following headers:

      • Customer ID

      • Card Token

      • Tokenization Status

      • Card Type

      • Card Network

      • Last Four Digits

      • Expiry Date

      • Task Status

      • Error Message

      • Created At

      • Updated At

  3. File Format:

    • CSV format with comma-separated values

    • Filename format: batch_card_tokenization.csv

    • Includes header row with column names

    • Security Note: Original card numbers are never included in downloads for PCI compliance

CSV File Upload Specifications

CSV Field Requirements

Scroll inside to view more
Field Name
Mandatory/Optional
Data Type
Description
Sample Value
Validation Rules
card_number
Mandatory
String
Credit/debit card number for tokenization
"4111111111111111"
Must be a valid card number format (13-19 digits), Luhn algorithm validation
card_expiry
Mandatory
String
Card expiry date in MM/YYYY format
"12/2025"
Must be in MM/YYYY format, future date validation
customer_id
Mandatory
String
Unique customer identifier for card association
"CUST_123456789"
Must be a valid string, cannot be empty, alphanumeric characters allowed

Card Number Validation Rules

Supported Card Types:

  • Visa: Cards starting with 4 (13, 16, or 19 digits)

  • Mastercard: Cards starting with 5 or 2 (16 digits)

  • American Express: Cards starting with 34 or 37 (15 digits)

  • Discover: Cards starting with 6 (16 digits)

  • Diners Club: Cards starting with 30, 36, or 38 (14 digits)

  • JCB: Cards starting with 35 (16 digits)

Validation Process:

  1. Length Validation: Card number must be between 13-19 digits

  2. Luhn Algorithm: Mathematical validation for card number authenticity

  3. Format Check: Only numeric characters allowed (spaces and hyphens are automatically removed)

  4. Test Card Detection: Test card numbers are flagged and processed differently

Expiry Date Format Requirements

Format Specification: MM/YYYY

  • MM: Month (01-12)

  • YYYY: Four-digit year

  • Separator: Forward slash (/) required

  • Future Date: Expiry date must be in the future

  • Valid Examples: "01/2025", "12/2030", "06/2027"

  • Invalid Examples: "1/25", "13/2025", "12/2020"

CSV Format Examples

Complete CSV Format with Sample Data:

File Upload Constraints

  • Maximum Rows: 1000 rows per CSV file

  • File Format: CSV (Comma Separated Values) only

  • Encoding: UTF-8 encoding recommended

  • File Size: Standard file size limitations apply

  • Column Order: Must match the specified header format (cardnumber, cardexpiry, customer_id)

  • Empty Values: All fields are mandatory and cannot be empty

  • Security: Files are processed in secure, PCI-compliant environment

Use Cases

PCI Compliance Migration

  1. Export existing card data from legacy systems

  2. Prepare CSV file with card numbers, expiry dates, and customer IDs

  3. Upload file through Batch Card Tokenization interface

  4. Replace original card data with secure tokens

Customer Card Management

  1. Prepare CSV with customer card information for tokenization

  2. Include customer IDs for proper card-customer association

  3. Upload file for automated card tokenization processing

  4. Track individual tokenization status and download token results

Secure Payment Processing Setup

  1. Compile card data from various payment sources

  2. Create CSV with card details and customer references

  3. Process bulk tokenization and export results for secure payment processing

  4. Use downloaded token data for future payment transactions

Troubleshooting

File Upload Validation Errors:

  • "Invalid file format": Ensure file is in CSV format with proper comma separation

  • "Missing mandatory fields": Verify that cardnumber, cardexpiry, and customer_id columns are present and not empty

  • "Row limit exceeded": Reduce file size to maximum 1000 rows per upload

  • "Invalid card number format": Check that card numbers are valid and pass Luhn algorithm validation

  • "Invalid expiry date format": Ensure expiry dates are in MM/YYYY format and represent future dates

Permissions and Roles

Access to the Batch Card Tokenization module is controlled by the following permissions:

  • Card Tokenization Module Access: Required for accessing the batch card tokenization interface (ACL: batch_tokenise)

  • Card Tokenization Write Permission: Required for creating and uploading batch card tokenization files (ACL: batch_tokenise with ReadWrite access)

  • Card Tokenization Read Permission: Needed to view batch tokenization status and download processed data (ACL: batch_tokenise)

Last updated 5 months ago