IP Library Granted Patent US 11,876,905
Granted Patent B2
US 11,876,905 · App. 17/752,708 · Granted Jan 16, 2024

System and method for generating trust tokens

Inventors: Quan Wang (Foster City, CA); Weiyi Zhou (Foster City, CA)
Assignee: VISA INTERNATIONAL SERVICE ASSOCIATION
H04L9/3213H04L9/006H04L9/0827H04L9/3247G06Q20/204G06Q20/227G06Q20/327G06Q20/389G06Q20/3825G06Q20/3829H04L9/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,876,905
App. No.
17/752,708
Granted
Jan 16, 2024
Kind
B2
Abstract

A trust token may be created including authentication data for a user and his or her associated communication device. The trust token may be transmitted by the communication device to one or more recipients, such as a token server. The recipients may interpret the trust token and verify it against data written to one or more nodes of a blockchain when the user and the communication device registered for the trust token. Once the trust token is verified, the token server may be configured to generate, maintain, and provision account tokens representing sensitive data. The token server may push one or multiple account tokens to the communication device, thereby allowing the communication device to perform transactions with the account tokens. In other words, the implementation of a trust token may allow the communication device to be provisioned with multiple account tokens, without requiring multiple logins or transmissions of sensitive data.

Claims (42)

1. A computer-implemented method, comprising:

receiving, by one or more nodes comprising a blockchain, a first public key from a first server computer, the first public key being associated with a communication device of a user;

generating, by the one or more nodes comprising the blockchain, a second public key and a second private key associated with the user of the communication device;

signing, by the one or more nodes comprising the blockchain, the first public key with the second private key to generate a digital signature for the user;

recording, by the one or more nodes comprising the blockchain, the digital signature on the blockchain on the one or more nodes;

transmitting, by the one or more nodes comprising the blockchain, the digital signature to the first server computer;

receiving, by the one or more nodes comprising the blockchain from a second server computer, a request comprising the digital signature;

verifying, by the one or more nodes comprising the blockchain, the digital signature received from the second server computer in the request against the digital signature recorded on the blockchain; and

transmitting, by the one or more nodes comprising the blockchain to the second server computer, an indication that the digital signature has been verified, wherein the second server computer thereafter processes a transaction corresponding to the request.

2. The computer-implemented method of claim 1 , wherein the first public key is one of a public-private key pair generated by the communication device.

3. The computer-implemented method of claim 1 , wherein receiving the first public key from the first server computer further comprises receiving, from the first server computer, a corresponding indication that account data corresponding to the user has been verified by the first server computer.

4. The computer-implemented method of claim 1 , wherein the second public key and the second private key is applicable to all devices operated by or associated with the user.

5. The computer-implemented method of claim 1 , wherein the one or more nodes comprising the blockchain assigns a transaction identifier or hash a block record of the blockchain corresponding to the digital signature.

6. The computer-implemented method of claim 1 , wherein transmitting the digital signature to the first server computer causes the first server computer to generate a trust token for the user.

7. The computer-implemented method of claim 6 , wherein the trust token comprises data corresponding to at least one of: a transaction identifier, a nonce, identity data, a source identifier, or a destination identifier.

8. The computer-implemented method of claim 7 , wherein at least a portion of the data of the trust token was generated by the communication device.

9. A blockchain node, comprising:

one or more processors; and

one or more memories storing executable-instructions that, when executed by the one or more processors, cause the blockchain node to:

receive a first public key from a first server computer, the first public key being associated with a communication device of a user;

generate a second public key and a second private key associated with the user of the communication device;

sign the first public key with the second private key to generate a digital signature for the user;

record the digital signature on a blockchain stored on one or more blockchain nodes comprising the blockchain node;

transmit the digital signature to the first server computer;

receive, from a second server computer, a request comprising the digital signature;

verify the digital signature received in the request against the digital signature recorded on the blockchain; and

transmit, to the second server computer, an indication that the digital signature has been verified, wherein the second server computer thereafter processes a transaction corresponding to the request.

10. The blockchain node of claim 9 , wherein the blockchain node further records the first public key.

11. The blockchain node of claim 9 , wherein the first public key is associated with the communication device and the second private key is associated with the user.

12. The blockchain node of claim 9 , wherein the first server computer is an authorizing entity computer.

13. The blockchain node of claim 9 , wherein the first server computer, in response to receiving the digital signature, generates a trust token using the digital signature and transmits the trust token to the communication device.

14. The blockchain node of claim 13 , wherein the communication device subsequently provides the trust token to a token server to request an account token to replace sensitive data in the transaction.

15. The blockchain node of claim 9 , wherein

the second server computer is a token server.

16. The blockchain node of claim 15 , wherein transmitting, to the token server, the indication that the digital signature has been verified, causes the token server to generate an account token for the communication device to replace sensitive information in one or more subsequent transactions.

17. The blockchain node of claim 16 , wherein the communication device utilizes the account token for a plurality of subsequent transactions.

18. The blockchain node of claim 9 , wherein or more blockchain nodes, including the blockchain node, maintain multiple blocks comprising respective digital signatures of a plurality of communication devices comprising the communication device.

19. The blockchain node of claim 9 , wherein the communication device is a first communication device, and the digital signature is a first digital signature, and wherein executing the executable-instructions further causes the blockchain node to:

receive a third public key with the first public key, the third public key being associated with a second communication device of the user;

sign the third public key with the second private key generated by the blockchain node to generate a second digital signature for the user;

record the second digital signature with the first digital signature on the blockchain; and

transmit the second digital signature with the first digital signature to the first server computer causing the first server computer to generate a first trust token for the first communication device and a second trust token for the second communication device for one or more subsequent transactions.

Continuity (2)
Continuation 16641616
Related Publication 20220286287A1 · Sep 8, 2022
Cited By (2)
US 12,572,686 US 12,712,753