Format-Preserving Tokenization

Databunker Pro features two tokenization engines. The original open-source version supported only tokenization for PII, PHI, and KYC records. The professional version adds a new secure format-preserving tokenization engine.

For instance, Databunker Pro can now tokenize credit card numbers. Unlike other solutions on the market, Databunker Pro was built with the latest data privacy requirements in mind, such as data minimization.

The product was built to handle millions of data tokenization requests, and the Databunker Pro API has been extended to support bulk tokenization requests.

What Problems Does It Solve?

1. Data Privacy & Compliance

• ✅ Meets GDPR data minimization requirements
• ✅ Protects sensitive data while maintaining format
• ✅ Ensures regulatory compliance without sacrificing functionality
• ✅ Reduces scope of PCI DSS compliance

2. Enterprise Scalability

• ✅ Handles millions of records through data partitioning
• ✅ Provides high-performance tokenization operations
• ✅ Supports multiple data formats and types
• ✅ Enables efficient data processing at scale

3. Format Compatibility

• ✅ Preserves data format for legacy system compatibility
• ✅ Maintains data validation rules (e.g., Luhn algorithm for credit cards)
• ✅ Enables analytics while protecting actual data
• ✅ Supports seamless integration with existing workflows

🔄 Supported Data Types

🛠️ Key Features

Databunker Pro has a number of unique features:

Automatic Expiration

In Databunker Pro, expiration allows you to set a lifespan for sensitive data tokens, ensuring they automatically expire after a defined period.

1
2
3
4
5

// Set expiration for tokenized records
{
    "record": "4532015112830366",
    "expiration": "30d"  // 30 days
}

Unique Record Support

This unique flag is used for data deduplication. It ensures that each record is saved only once, and the same token value is returned for identical records. If the original record has an expiration flag set, its expiration countdown will be reset from the beginning.

1
2
3
4
5

// Same input generates same token when enabled
{
    "record": "4532015112830366",
    "unique": true
}

Dual Token Generation

By default, Databunker Pro generates two tokens: one in UUID format and another in a format-preserving manner.

1
2
3
4
5
6

// Example response for credit card tokenization
{
  "status": "ok",
  "tokenuuid": "550e8400-e29b-41d4-a716-446655440000",
  "tokenbase": "4532015112830366"  // Format-preserving token
}

🚀 Getting Started

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

# Example API call for tokenization
curl -X POST https://databunker.pro/api/v1/tokenize \
  -H "X-Bunker-Token: <access-tone>" \
  -H "X-Bunker-Tenant: <tenant-name>" \
  -d '{
    "record": "4532015112830366",
    "type": "creditcard",
    "expiration": "30d"
    "unique": true,
  }'

Output:

1
2
3
4
5

{
  "status": "ok",
  "tokenuuid": "550e8400-e29b-41d4-a716-446655440000",
  "tokenbase": "4532015112830366"  // Format-preserving token
}

📈 Benefits

• Compliance: Built-in GDPR data minimization
• Security: Protected sensitive data storage
• Compatibility: Format preservation for legacy systems
• Scalability: Enterprise-grade performance
• Flexibility: Multiple token format support