# US 2023/0274277 A1 · Identity management service via a user-level token

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

- Number: US 2023/0274277 A1
- Document ID: US20230274277A1
- Status: Published application
- Kind: A1
- Application number: 18/142,558
- Filed: 2023-05-02
- Published: 2023-08-31
- Earliest claimed: 2017-03-10
- Assignees: Wells Fargo Bank, N.A.
- Applicants: Wells Fargo Bank, N.A.
- Inventors: Ashish B. Kurani; Kristine Ing Kushner; Brian M. Pearce; Steven E. Puffer; Nikolai Stroke; Paul Vittimberga; Young M. Yang
- Web page: https://patentgrep.com/patent/US20230274277A1

## CPC

- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/18: involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q 20/3821: {Electronic credentials}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 30/0609: {Qualifying participants for shopping transactions (payment transaction verification G06Q20/401)}
- 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

## Abstract

A computing system includes an interface configured to communicate with an entity computing system associated with a merchant via a network, an identity database storing verified personal identifying information, a memory, and at least one processor configured to: determine whether an individual is associated with an existing user account; prompt the individual to create a user account; verify an identity of the individual using personal identifying information associated with the individual; receive non-financial information associated with the individual; generate a user-level profile having the non-financial information; generate a user-level token unique to the individual; transmit the user-level token to a device associated with the individual; receive an identity verification request having the user-level token; validate the user-level token; determine that the identity verification request includes contextual data; determine the non-financial information that is relevant to the contextual data; and transmit a verification approval and the non-financial information.

## Claims

### Claim 1

A computing system, comprising:
a network interface configured to communicate with an entity computing system associated with a merchant via a network;
an identity database storing verified personal identifying information;
a memory; and
at least one processor configured to:
determine whether an individual is associated with an existing user account;
in response to determining that the individual is not associated with an existing user account, prompt the individual to create a user account;
verify an identity of the individual using personal identifying information associated with the individual;
receive non-financial information associated with the individual;
generate a user-level profile, wherein the user-level profile comprises the non-financial information;
generate a user-level token unique to the individual, wherein the user-level token is associated with the user-level profile;
transmit the user-level token to a device associated with the individual via the network;
receive an identity verification request comprising the user-level token;
validate the user-level token;
determine that the identity verification request includes contextual data;
determine the non-financial information within the user-level profile that is relevant to the contextual data; and
transmit an identity verification approval and the non-financial information relevant to the contextual data to the entity computing system.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the contextual data includes a merchant type, the merchant type is associated with an airport kiosk, and the non-financial information relevant to the contextual data is a frequent flier account number.

### Claim 3 (depends on 1)

The computing system of claim 1, wherein the contextual data includes a merchant type, the merchant type is associated with an automated teller machine (ATM), and the non-financial information relevant to the contextual data is a photo of the individual.

### Claim 4 (depends on 1)

The computing system of claim 1, wherein:
the identity verification request is structured as a transaction card-originated message; and
the user-level token is inserted into an account number of the transaction card-originated message.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein determining whether the individual is associated with an existing user account includes determining that the individual holds a financial account at a financial institution.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the contextual data includes at least one of an entity computing type or a geo-location of the entity computing system.

### Claim 7 (depends on 1)

The computing system of claim 1, wherein the user-level token includes a bank identification number.

### Claim 8

A computing implemented method performed by an identity verification computing system communicatively coupled to an entity computing system of a merchant, the method comprising:
determining, by the identity verification computing system, whether an individual is associated with an existing user account;
in response to determining that the individual is not associated with an existing user account, prompting, by the identity verification computing system, the individual to create a user account;
verifying, by the identity verification computing system, an identity of the individual using personal identifying information associated with the individual;
receiving, by the identity verification computing system, non-financial information associated with the individual;
generating, by the identity verification computing system, a user-level profile, wherein the user-level profile comprises the non-financial information;
generating, by the identity verification computing system, a user-level token unique to the individual, wherein the user-level token is associated with the user-level profile;
transmitting, by the identity verification computing system, the user-level token to a device associated with the individual via a network;
receiving, by the identity verification computing system, an identity verification request comprising the user-level token;
validating, by the identity verification computing system, the user-level token;
determining, by the identity verification computing system, that the identity verification request includes contextual data;
determining, by the identity verification computing system, the non-financial information within the user-level profile that is relevant to the contextual data; and
transmitting, by the identity verification computing system to the entity computing system, an identity verification approval and the non-financial information relevant to the contextual data.

### Claim 9 (depends on 8)

The method of claim 8, wherein the contextual data includes a merchant type, the merchant type is associated with an airport kiosk, and the non-financial information relevant to the contextual data is a frequent flier account number.

### Claim 10 (depends on 8)

The method of claim 8, wherein the contextual data includes a merchant type, the merchant type is associated with an automated teller machine (ATM), and the non-financial information relevant to the contextual data is a photo of the individual.

### Claim 11 (depends on 8)

The method of claim 8, wherein:
the identity verification request is structured as a transaction card-originated message; and
the user-level token is inserted into an account number of the transaction card-originated message.

### Claim 12 (depends on 8)

The method of claim 8, wherein determining whether the individual is associated with an existing user account includes determining, by the identity verification computing system, that the individual holds a financial account at a financial institution associated with the identity verification computing system.

### Claim 13 (depends on 8)

The method of claim 8, wherein the contextual data includes at least one of an entity computing type or a geo-location of the entity computing system.

### Claim 14 (depends on 8)

The method of claim 8, wherein the user-level token includes a bank identification number.

### Claim 15

A non-transitory computer-readable medium having processor-readable instructions stored thereon such that, when executed by one or more processors, cause the one or more processors to perform the steps of:
determining whether an individual is associated with an existing user account;
in response to determining that the individual is not associated with an existing user account, prompting the individual to create a user account;
verifying an identity of the individual using personal identifying information associated with the individual;
receiving non-financial information associated with the individual;
generating a user-level profile, wherein the user-level profile comprises the non-financial information;
generating a user-level token unique to the individual, wherein the user-level token is associated with the user-level profile;
transmitting the user-level token to a device associated with the individual via a network;
receiving an identity verification request comprising the user-level token;
validating the user-level token;
determining that the identity verification request includes contextual data;
determining the non-financial information within the user-level profile that is relevant to the contextual data; and
transmitting an identity verification approval and the non-financial information relevant to the contextual data to an entity computing system associated with a merchant.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the contextual data includes a merchant type, the merchant type is associated with an airport kiosk, and the non-financial information relevant to the contextual data is a frequent flier account number.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the contextual data includes a merchant type, the merchant type is associated with an automated teller machine (ATM), and the non-financial information relevant to the contextual data is a photo of the individual.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein:
the identity verification request is structured as a transaction card-originated message; and
the user-level token is inserted into an account number of the transaction card-originated message.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein determining whether the individual is associated with an existing user account includes determining that the individual holds a financial account at a financial institution.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the contextual data includes at least one of an entity computing type or a geo-location of the entity computing system.
