Derived unique token per transaction
Example implementations include a method for using tokens between two entities including a client device and a server, by generating, by a first one-way function of the client device, a first intermediate value from a transaction count corresponding to a number of transactions involving an original data, the first intermediate value being unique to a first verification transaction at a server, generating, by a second one-way function of the client device, a second intermediate value from the first intermediate value, the second intermediate value being unique to a second verification transaction at the server, sending, by the client device, a first token based on the first intermediate value to the server to execute the first verification transaction, and sending, by the client device, a second token based on the second intermediate value to the server to execute the second verification transaction.
1. A method for using tokens between two entities comprising a client device and a server, the method comprising:
generating, by a first one-way function of a client device, a first intermediate value from a number of transactions, the first intermediate value corresponding to a first verification transaction at a server;
generating, by a second one-way function of the client device, a second intermediate value from the first intermediate value, the second intermediate value corresponding to a second verification transaction at the server;
causing, by the client device and based on the first intermediate value, the server to execute the first verification transaction; and
causing, by the client device and based on the second intermediate value, the server to execute the second verification transaction.
2. The method of claim 1 , further comprising:
generating, by a first verification function of the client device, a first token from the first intermediate value.
3. The method of claim 2 , further comprising:
encrypting the first token.
4. The method of claim 3 , further comprising:
deleting, by the client device, the first intermediate value after the generating the second intermediate value.
5. The method of claim 2 , further comprising:
generating, by the client device, a first digital signature associated with the first token from a private key associated with the client device.
6. The method of claim 1 , further comprising:
generating, by a second verification function of the client device, a second token from the second intermediate value.
7. The method of claim 6 , further comprising:
encrypting the second token.
8. The method of claim 6 , further comprising:
generating, by the client device, a second digital signature associated with the second token from the private key.
9. The method of claim 1 , wherein the number of transactions corresponds to an original data that comprises one or more of a payment card number, a financial account number, a password, a social security number, a name, an address, an email address, any Personally Identifiable Information (PII), a security object, and a seed for key-generation.
10. The method of claim 9 , further comprising:
deleting, by the client device, the original data after the generating the first intermediate value.
11. The method of claim 1 , wherein the number of transactions corresponds to an original data that comprises one or more of a payment card number, a financial account number, a password, a social security number, a name, an address, an email address, any Personally Identifiable Information (PII), a security object, and a seed for key-generation.
12. A client device, comprising:
a network interface; and
a processing circuit configured to:
generate, by a first one-way function of a client device, a first intermediate value from a number of transactions, the first intermediate value corresponding to a first verification transaction at a server;
generate, by a second one-way function of the client device, a second intermediate value from the first intermediate value, the second intermediate value corresponding to a second verification transaction at the server;
cause, by the client device and based on the first intermediate value, the server to execute the first verification transaction; and
cause, by the client device and based on the second intermediate value, the server to execute the second verification transaction.
13. The device of claim 12 , wherein the processing circuit is further configured to:
generate, by a first verification function of the client device, a first token from the first intermediate value.
14. The device of claim 13 , wherein the processing circuit is further configured to:
encrypt the first token.
15. The device of claim 13 , wherein the processing circuit is further configured to:
generate, by the client device, a first digital signature associated with the first token from a private key associated with the client device.
16. The device of claim 12 , wherein the processing circuit is further configured to:
generate, by a second verification function of the client device, a second token from the second intermediate value.
17. The device of claim 16 , wherein the processing circuit is further configured to:
encrypt the second token.
18. The device of claim 16 , wherein the processing circuit is further configured to:
generate, by the client device, a second digital signature associated with the second token from the private key.
19. A server, comprising:
a network interface; and
a processing circuit configured to:
receive, at the server, a first token based on a first intermediate value, the first intermediate value being based on a number of transactions, the first intermediate value corresponding to a first verification transaction at the server, and the first intermediate value being generated by a first one-way function of the client device;
receive, at the server, a second token based on the second intermediate value, the second intermediate value being based on the first intermediate value, the second intermediate value corresponding to a second verification transaction at the server, and the second intermediate value being generated by a second one-way function of the client device;
execute a first verification transaction based on the first token; and
execute a second verification transaction based on the second token.
20. The server of claim 19 , wherein the number of transactions corresponds to an original data that comprises one or more of a payment card number, a financial account number, a password, a social security number, a name, an address, an email address, any Personally Identifiable Information (PII), a security object, and a seed for key-generation.