# US 2022/0286287 A1 · System And Method For Generating Trust Tokens

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0286287 A1
- Document ID: US20220286287A1
- Status: Published application
- Kind: A1
- Application number: 17/752,708
- Filed: 2022-05-24
- Published: 2022-09-08
- Earliest claimed: 2020-02-24
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Quan Wang; Weiyi Zhou
- Web page: https://patentgrep.com/patent/US20220286287A1

## CPC

- G06Q 20/3821: {Electronic credentials}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/006: {involving public key infrastructure [PKI] trust models (network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/0827: {involving distinctive intermediate devices or communication paths (network architectures or network communication protocols using different networks H04L63/18)}
- H04L 9/3247: {involving digital signatures}
- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer}
- G06Q 20/327: {Short range or proximity payments by means of M-devices}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## 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

### Claim at position 1

1-20. (canceled)

### Claim 21

A computer-implemented method, comprising:
receiving, by one or more nodes of 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 of 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 of 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 of the blockchain, the digital signature on the blockchain on the one or more nodes;
transmitting, by the one or more nodes of the blockchain, the digital signature to the first server computer; and
verifying, by the one or more nodes of the blockchain, the digital signature for the user for a subsequent transaction.

### Claim 22 (depends on 21)

The computer-implemented method of claim 21, wherein verifying the digital signature further comprises:
receiving, by the one or more nodes of the blockchain, the digital signature from a second server computer in a request for a transaction;
verifying, by the one or more nodes of the blockchain, the digital signature received from the second server computer against the digital signature recorded at the one or more nodes of the blockchain; and
transmitting, by the one or more nodes of the blockchain to the second server computer, an indication that the digital signature has been verified, wherein the second server computer thereafter processes the request for the transaction.

### Claim 23 (depends on 21)

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

### Claim 24 (depends on 21)

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

### Claim 25 (depends on 21)

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

### Claim 26 (depends on 21)

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

### Claim 27 (depends on 21)

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

### Claim 28 (depends on 27)

The computer-implemented method of claim 27, 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.

### Claim 29 (depends on 28)

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

### Claim 30

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 comprising one or more nodes;
transmit the digital signature to the first server computer; and
verify the digital signature for the user for a subsequent transaction involving the user.

### Claim 31 (depends on 30)

The blockchain node of claim 30, wherein the one or more nodes of the blockchain further records the first public key.

### Claim 32 (depends on 30)

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

### Claim 33 (depends on 30)

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

### Claim 34 (depends on 30)

The blockchain node of claim 30, 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.

### Claim 35 (depends on 34)

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

### Claim 36 (depends on 30)

The blockchain node of claim 30, wherein verifying the digital signature further causes the blockchain node to:
receive the digital signature from a second server computer, the second server computer being a token server; and
transmit, to the token server, an indication that the digital signature has been verified.

### Claim 37 (depends on 36)

The blockchain node of claim 36, 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.

### Claim 38 (depends on 37)

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

### Claim 39 (depends on 30)

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

### Claim 40 (depends on 30)

The blockchain node of claim 30, 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.
