Derived unique token per transaction
AssigneeWells Fargo Bank, N.A.
InventorsPhillip H. Griffin, Jeffrey J. Stapleton
Life of this patent
Estimating the term…
Abstract
Examples described herein relate to systems, apparatuses, and methods for using tokens between two entities comprising a client device and a server, including receiving, by the server, a token from the client device, wherein the token is unique to a transaction, deriving, by the server, a server-derived token from the original data based on a transaction count, wherein the transaction count corresponds to a number of times that the original data is involved in transactions, comparing, by the server, the received token with the server-derived token, and responsive to determining that the received token and the server-derived token are same, sending, by the server, a verification message.
Claims17
A method for using tokens between two entities comprising a client device and a server, the method comprising:
- initiating, by the client device, a transaction involving original data, wherein the original data needs to be verified by the server;
- , generating, by a first one-way function of the client device, a first intermediate value based on a transaction count as input, wherein the first intermediate value replaces the transaction count as input to a second one-way function of the client device;
- generating, based on the first intermediate value, a first token for the transaction from the original data, wherein the first token is unique to the transaction, and the transaction count corresponds to a number of times that the original data is involved in transactions;
- and
- sending, by the client device, the first token to the server for verification.
A client device, comprising:
- a network interface;
- and
- a processing circuit configured to:
- initiate, by the client device, a transaction involving original data, wherein the original data needs to be verified by the server;
- run, generate, by a first one-way function of the client device, a first intermediate value based on a transaction count, and to generate count as input, wherein the first intermediate value replaces the transaction count as input to a second one-way function of the client device;
- generate, based on the first intermediate value, a first token for the transaction from the original data, wherein the first token is unique to the transaction, and the transaction count corresponds to a number of times that the original data is involved in transactions;
- and
- send, by the client device, the first token to the server for verification.
A method for using tokens between a client device and a server, the method comprising:
- receiving, by the server, a client token and a transaction count from the client device, wherein the client token is based on a client intermediate value generated by a first one-way function of the client device by using the transaction count as input, wherein the client token is unique to a transaction, and wherein the client intermediate value replaces the transaction count as input to a second one-way function of the client device;
- generating by a first one-way function of the server, a first intermediate value by running a first number of iterations of the first one-way function with original data as input wherein the number of iterations equals the transaction count;
- generating, based on the first intermediate value, a server-derived token from the original data and the transaction count, wherein the transaction count corresponds to a number of times that the original data is involved in transactions;
- comparing, by the server, the received client token with the server-derived token;
- and
- responsive to determining that the received client token and the server-derived token are same, sending, by the server, a verification message.
A server, comprising:
- a network interface;
- and
- a processing circuit configured to:
- receive a client token and a transaction count from the client device, wherein the client token is based on a client intermediate value generated by a first one-way function of the client device by using the transaction count as input, wherein the client token is unique to a transaction, and wherein the client intermediate value replaces the transaction count as input to a second one-way function of the client device;
- generate a first intermediate value by running a first number of iterations of a first one-way function of the server with original data as input to determine a first intermediate value, wherein the number of iterations equals the transaction count;
- generate, based on the first intermediate value, a server-derived token from the original data and the transaction count, wherein the transaction count corresponds to a number of times that the original data is involved in transactions;
- compare the received client token with the server-derived token;
- and
- responsive to determining that the received client token and the server-derived token are same, send a verification message.
Dependencies are inferred from the claim text.