Mobile Device Tokenization via Local Key Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Tokenization systems are vulnerable to security breaches due to the storage and transmission of mappings between payment tokens and account numbers, which can be exploited for fraudulent purposes.
Innovation Solution
A mobile device generates a unique digital key from the account number of a payment instrument using a transformation function, stores this key securely, and transmits it to an issuance server, eliminating the need for a third-party token service provider to store account numbers, thereby enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a third-party token service provider stores mappings between tokens and account numbers, then tokenization services can be provided, but security vulnerabilities arise from potential theft of these mappings
Solution Approach 1:
The patent extracts the sensitive account number data from the third-party token service provider's storage system. Instead of storing mappings between tokens and account numbers at the TSP, the system generates tokens directly at the mobile device using the account number locally, eliminating the need for centralized storage of sensitive mappings and thereby removing the security vulnerability.
Solution Approach 2:
The mobile device performs self-service by generating its own payment tokens using a transformation function applied to the account number. The device stores the account number and transformation function locally in a secure element, allowing it to autonomously create tokens without relying on a third-party service provider to manage sensitive data mappings.
2Productivity
If account numbers are transmitted to issuers, then payment transactions can be authorized, but transmission vulnerabilities enable interception and fraud
Solution Approach 1:
The system creates a functional copy of the account number through token generation. The mobile device applies a transformation function to the account number to generate a token that represents the account number for transaction purposes. This token can be transmitted instead of the actual account number, maintaining transaction functionality while eliminating the security risk of transmitting sensitive account data.
3Ease of operation
If third-party token service providers are used, then token management is centralized, but security flaws in provider systems compromise all tokens
Solution Approach 1:
The patent segments the tokenization function from the third-party service provider and relocates it to the mobile device. Each device independently generates and manages its own tokens using locally stored account numbers and transformation functions. This segmentation eliminates the single point of failure at the TSP, as each device's tokens are secured independently in its own secure element.
Data Source
AI summary
A method is provided that includes assigning one or more first records of a first table and one or more second records of a second table to corresponding range groups of a plurality of range groups. The method further includes comparing at least one record of the first table with at least one record of the second table, where the at least one record of the first table and the at least one record of the second table are assigned to a first range group of the plurality of range groups. The method also includes, based on the comparing, identifying a parent record and a child record and segmenting the parent record based on the child record. Further, the method includes subsequent to the segmenting the parent record, performing a join operation on the first table and the second table.