Token management system

Patent metadata

Field	Value
Publication number	US-12073409-B2
Application number	US-202318197276-A
Country	US
Kind code	B2
Filing date	May 15, 2023
Priority date	Mar 27, 2015
Publication date	Aug 27, 2024
Grant date	Aug 27, 2024

Abstract

A computer system includes a token repository configured to store payment tokens, and a server system. The server system includes a processor and instructions stored in non-transitory machine-readable media, the instructions configured to cause the server system to receive a request to provision a payment token based on a financial product, wherein the request includes information related to the financial product, provision a payment token based on the token request, including authenticating the financial product based on the financial product information and generating the payment token upon authenticating the financial product, wherein the payment token is useable to make a payment via the financial product, and store the payment token in the token repository.

First claim

What is claimed is:

1. A computer system, comprising:
a token database configured to store non-payment tokens; and
a server system comprising a processor and instructions stored in non-transitory machine readable media, the instructions configured to cause the server system to:
receive a request to provision a non-payment token based on non-payment information;
provision the non-payment token based on the request;
store the non-payment token and at least one preference for the non-payment token in the token database;
provide the non-payment token to a first remote third-party system of a first third-party, wherein the first third-party is an intermediary;
receive the non-payment token from the first remote third-party system of the first third-party;
in response to receiving the non-payment token from the first remote third-party system, determine that the first third-party is not allowed to use the non-payment token and refrain from de-tokenizing the non-payment token to determine the non-payment information associated with the non-payment token;
receive a notification that the non-payment token has been sent by the first third-party to a second third-party;
receive the non-payment token from a second remote third-party system of the second third-party;
receive, from the second third-party, identifying information associated with the second third-party and information regarding an intended use of the non-payment information;

determine, based on the identifying information associated with the second third-party and at least one token preference, that the second third-party is an intended party and is authorized to access the non-payment information for the intended use.

2. The computer system of claim 1 , wherein the non-payment information comprises personal information of an account holder.

3. The computer system of claim 2 , wherein the personal information includes one or more of address information or a personal identification number.

4. The computer system of claim 1 , the at least one preference for the non-payment token comprising at least one rule regarding expiration of the non-payment token.

5. The computer system of claim 1 , wherein the stored instructions are further configured to cause the server system to:
receive an access request including the non-payment token, wherein the access request includes a request to allow access to the non-payment information to an intended party system but not allow access to the non-payment information to an intermediary system; and
provide the non-payment information to the intended party system in accordance with the access request.

6. The computer system of claim 1 , wherein the stored instructions are further configured to cause the server system to:
filter, based on an input provided by the second third-party, the non-payment information to omit at least one character from the non-payment information, wherein the non-payment token does not include the omitted at least one character.

7. The computer system of claim 1 , wherein the stored instructions are further configured to cause the server system to:
group non-payment information into a plurality of groups according to a plurality of intended uses; and
automatically generate a plurality of group non-payment tokens, wherein each of the plurality of automatically generated group non-payment tokens is associated with one of the plurality of intended uses based on the grouped non-payment information.

8. The computer system of claim 7 , wherein the non-payment token is one of the plurality of group non-payment tokens, and wherein the stored instructions are further configured to cause the server system to:
in response to determining that a merchant is allowed to use the one of the plurality of group non-payment tokens, de-tokenize the one of the plurality of group non-payment tokens to determine updated group non-payment information associated with the one of the plurality of group non-payment tokens; and
transmit the updated group non-payment information to the merchant in accordance with a corresponding rule specifying information that may be transmitted to the merchant.

9. The computer system of claim 8 , wherein the updated group non-payment information comprises a plurality of information required for the intended use.

10. The computer system of claim 9 , wherein the intended use comprises at least one of purchasing a car, purchasing a home, applying for college, or applying for rental housing.

11. A method of provisioning non-payment tokens, comprising:
receiving, by a token vault computer system, a request to provision a non-payment token based on non-payment information;
provisioning, by the token vault computer system, the non-payment token based on the request;
storing, by the token vault computer system, the non-payment token and at least one preference for the non-payment token in a token database;
providing the non-payment token to a first remote third-party system of a first third-party, wherein the first third-party is an intermediary;
receiving, by the token vault computer system, the non-payment token from the first remote third-party system of the first third-party;
in response to receiving the non-payment token from the first remote third-party system, determining, by the token vault computer system, that the first third-party is not allowed to use the non-payment token;
refraining, based on the determination that the first third party is not allowed to use the non-payment token, from de-tokenizing the non-payment token to determine the non-payment information associated with the non-payment token;
receiving a notification that the non-payment token has been sent by the first third-party to a second third-party;
receiving the non-payment token from a second remote third-party system of the second third-party;
receiving, from the second third-party, identifying information associated with the second third-party and information regarding an intended use of the non-payment information;
determining, based on the identifying information associated with the second third-party and at least one token preference, that the second third-party is an intended party and is authorized to access the non-payment information for the intended use.

12. The method of claim 11 , wherein the non-payment information comprises personal information of an account holder.

13. The method of claim 12 , wherein the personal information includes one or more of address information or a personal identification number.

14. The method of claim 11 , wherein the at least one preference comprises at least one rule regarding expiration of the non-payment token.

15. The method of claim 11 , further comprising:
receiving, by the token vault computer system, an access request including the non-payment token, wherein the access request includes a request to allow access to the non-payment information to an intended party system but not allow access to the non-payment information to an intermediary system; and
providing, by the token vault computer system, the non-payment information to the intended party system in accordance with the access request.

16. The method of claim 11 , further comprising:
grouping, by the token vault computer system, the non-payment information into a plurality of groups according to a plurality of intended uses; and
automatically generating, by the token vault computer system, a plurality of group non-payment tokens, wherein each of the plurality of automatically generated group non-payment tokens is associated with one of the plurality of intended use

Assignees

• Wells Fargo Bank Na

Inventors

• Asefi Azita
• Michirefe Jorge
• Hecht Al
• Puffer Steve
• Ho Peter

Classifications

• G06Q20/3672

  initialising or reloading thereof · CPC title

• G06Q30/02

  Marketing; Price estimation or determination; Fundraising · CPC title

• G06F21/62

  Protecting access to data via a platform, e.g. using keys or access control rules · CPC title

• G06Q20/401

  Transaction verification · CPC title

• G06Q20/367

  involving electronic purses or money safes · CPC title