Vaultless Payment Tokenization Using iFrame Data Capture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data tokenization solutions are computationally inefficient due to vaulted tokenization techniques that require extensive indexing and processing, leading to increased computational workloads and security risks, especially when handling sensitive data.

Innovation Solution

A system utilizing iframe and tokenization services that vaultlessly tokenize and encrypt data, storing tokens in a cache and using format-preserving obfuscation parameters, allowing data to be collected and processed without passing through servers, and enabling secure detokenization and decryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If vaulted tokenization techniques are used to store encrypted data in a vault, then data security is improved, but computational efficiency deteriorates due to extensive indexing and processing requirements

Engineering Contradiction:
Improvedata securityVSAvoidcomputational efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the core tokenization function from the vaulted tokenization system, eliminating the need for a centralized data vault. Tokens are generated and processed without requiring storage in a secure vault, thereby removing the computational overhead associated with indexing and searching through millions of data entries while maintaining security through the tokenization process itself

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the tokenization process into distinct components: token generation, token processing, and token validation. This segmentation allows each component to operate independently without requiring access to a centralized vault, reducing computational complexity and improving processing efficiency while maintaining data security through distributed token management

Inventive Principle:
Principle #1Segmentation

2Duration of action of stationary object

If data is stored in a vault with millions of entries, then data retention is improved, but processing speed deteriorates due to computationally intensive indexing processes

Engineering Contradiction:
Improvedata retentionVSAvoidprocessing time
Core Design Contradiction:
Duration of action of stationary objectVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-generating and caching tokens before they are needed for processing. Tokens are created in advance and stored in a token cache with associated metadata, allowing rapid retrieval and processing without requiring time-consuming indexing operations when actual data processing occurs, thus reducing processing time while maintaining data retention capabilities

Inventive Principle:
Principle #10Preliminary action

3Reliability

If client systems process and transmit sensitive data through secondary processors, then data authentication is improved, but computing complexity increases

Engineering Contradiction:
Improvedata authenticationVSAvoidcomputing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary tokenization service that acts as a mediator between client systems and secondary processors. Sensitive data is tokenized before transmission, and the tokenization service handles authentication and validation processes, thereby simplifying the computing complexity for client systems while maintaining robust data authentication through the intermediary layer

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12506720B2Systems and processes for vaultless tokenization and encryption
Publication Date: 2025.12.23 BLUEFIN PAYMENT SYSTEMS LLC
  • US12506720B2 patent drawing
  • US12506720B2 patent drawing
  • US12506720B2 patent drawing

AI summary

A computing device can generate an iFrame on a particular website hosted on a server. The computing device can receive payment data from the iFrame corresponding to a transaction on the particular website. The computing device can generate an eToken corresponding to the received payment data. The computing device can transmit the eToken to the server. The computing device can receive transaction data comprising the eToken and non-sensitive payment data corresponding to the transaction from the server. The computing device can determine the received payment data based on authenticating the eToken. The computing device can process the transaction.