Offline Payment Token Verification via Generation Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face difficulties in transferring funds using payment tokens between devices when they are offline and not connected to a remote server, as it is challenging to verify the origin and validity of the tokens in such scenarios.

Innovation Solution

A method and system for generating and provisioning a second payment token from a first token, which includes obtaining a first token, generating a second token linked to the first token with unique generation data, and provisioning this second token and data to a second device, allowing verification of the token's origin and validity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If tokens are used instead of real information for transactions, then data security is improved, but the ability to transfer funds between offline devices is worsened

Engineering Contradiction:
Improvedata securityVSAvoidfund transfer capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system segments the token verification process into two parts: the token itself and the generation data. The token can be transferred offline between devices, while the generation data (which proves the token's origin) is stored separately on the server. This segmentation allows offline transfers to proceed smoothly while maintaining security through the separate verification mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary verification mechanism using generation data that links tokens to their source device. When a token is transferred offline, the receiving device can later verify its authenticity by checking the generation data on the server, without requiring the server to be online during the actual transfer. This intermediary data structure enables offline operation while maintaining centralized verification capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If tokens are transferred between offline devices without server connection, then operational flexibility is improved, but token origin verification becomes difficult

Engineering Contradiction:
Improveoffline operation capabilityVSAvoidtoken origin verification
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system performs preliminary action by embedding generation data with the token at the time of token creation. This generation data contains information about the source device and is stored both locally on the transferring device and on the server. When the token is later transferred offline and needs verification, the preliminary recorded generation data enables authentication without requiring real-time server connection during the transfer moment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a local copy of the generation data on the transferring device that mirrors the server's record. This local copy allows the device to verify token origin independently when offline. The copying mechanism ensures that the verification capability is replicated across devices without requiring continuous server connectivity, thus enabling offline operation while maintaining verification integrity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11250391B2Token check offline
Publication Date: 2022.02.15 VISA INTERNATIONAL SERVICE ASSOCIATION
  • US11250391B2 patent drawing
  • US11250391B2 patent drawing
  • US11250391B2 patent drawing

AI summary

Embodiments are directed to a method comprising, obtaining, by a first device, a first token, the first token associated with an amount of funds and a funds availability starting date. After the first token is obtained by the first device, the first device generates a second token linked to the first token and second token generation data. The second token generation data may include evidence that the second token was generated by the first device, and not another device. The second token generation data could be a first device identifier and the second token generation details, or could be a hashed value of the first device identifier and the second token generation details. The method also includes provisioning, by the first device, the second token and the second token generation data to the second device.