Granted Patent B2

US 12,333,551 · App. 18/514,996 · Granted Jun 17, 2025

Inventors: Azita Asefi (Vacaville, CA); Jorge Michirefe (Phoenix, AZ); Al Hecht (Chanhassen, MN); Steve Puffer (Champlin, MN); Peter Ho (Walnut Creek, CA)

Assignee: Wells Fargo Bank, N.A.

G06Q20/405G06F21/62G06Q20/34G06Q20/367G06Q20/3672G06Q20/401G06Q30/02

Abstract

Claims (52)

1. A computer system, comprising:

one or more servers configured to, independently or collectively:

provision a payment token based on a token request for a financial product, the token request including financial product information comprising account information that is to be tokenized and identity information of an account holder, comprising:

verifying that the financial product is associated with the account holder, and determining that the financial product is eligible for tokenization based on the financial product information, wherein determining that the financial product is eligible for tokenization comprises:

determining a type of the financial product; and

determining that the financial product is eligible in response to determining that eligibility rules indicate that the type of the financial product is eligible for tokenization;

generate the payment token in response to the determination that the financial product is eligible;

determine, based on preferences of the account holder associated with the financial product, merchants that are allowed to receive the payment token;

encrypt the payment token;

transmit the encrypted payment token and a decryption key for decrypting the encrypted payment token to a token requestor;

receive the payment token and a request for personal identifying information of the account holder from a first merchant; and

provide access to particular data fields of the account holder to the first merchant based on associated rules governing access to data fields associated with the account holder, the particular data fields including the personal identifying information of the account holder requested by the first merchant.

2. The computer system of claim 1 , wherein to provision the payment token, the one or more servers are further configured to:

filter the financial product information to exclude words or characters based on filter settings; and

generate rules for the payment token based on the preferences of the account holder associated with the financial product.

3. The computer system of claim 1 , wherein generating the payment token further comprises generating the payment token in response to filtering of the financial product information to remove selected content based on filter settings.

4. The computer system of claim 1 , wherein the one or more servers are further configured to determine the associated rules comprising instructions to provide access to the particular data fields based on the preferences.

5. The computer system of claim 1 , wherein provisioning the payment token further includes, upon generating the payment token, activating the payment token for use as a payment credential.

6. The computer system of claim 1 , wherein the financial product is unrelated to a payment card, and wherein the payment token is useable to make a payment via the financial product.

7. The computer system of claim 1 , wherein the payment token is generated by encrypting at least a portion of the financial product information.

8. The computer system of claim 1 , wherein the one or more servers are further configured to:

receive a request to authorize a transaction involving the payment token; and

authorize the transaction based on the payment token.

9. The computer system of claim 8 , wherein the one or more servers are further configured to update a status of the payment token based on the transaction.

10. The computer system of claim 1 , wherein the associated rules comprise merchant rules that vary between different merchants.

11. The computer system of claim 1 , wherein provisioning the payment token includes filtering words or characters from the payment token based on inputs received from a merchant computer system of the first merchant.

12. The computer system of claim 1 , wherein determining the type of the financial product comprises determining that the financial product is one of a payment card-type or a bank account-type, and wherein the eligibility rules indicate that a financial product of the payment card-type or the bank account-type is eligible for tokenization.

13. The computer system of claim 1 , wherein determining the type of the financial product comprises determining that the financial product is one of a credit card, a debit card, or a bank account, and wherein the eligibility rules indicate that credit cards, debit cards, and bank accounts are eligible for tokenization.

14. The computer system of claim 1 , wherein the one or more servers are further configured to verify an identity of the first merchant as an intended party by cross-referencing a merchant identifier of the request from the first merchant with the associated rules.

15. A method, comprising:

provisioning, by a token vault computer system, a payment token based on a token request for a financial product, the token request including financial product information comprising account information that is to be tokenized and identity information of an account holder, comprising:

verifying that the financial product is associated with the account holder, and determining that the financial product is eligible for tokenization based on the financial product information, wherein determining that the financial product is eligible for tokenization comprises:

determining a type of the financial product; and

determining that the financial product is eligible in response to determining that eligibility rules indicate that the type of the financial product is eligible for tokenization;

generating, by the token vault computer system, the payment token in response to the determination that the financial product is eligible;

determining, based on preferences of the account holder associated with the financial product, merchants that are allowed to receive the payment token; and

encrypting the payment token;

transmitting the encrypted payment token and a decryption key for decrypting the encrypted payment token to a token requestor;

receiving, by the token vault computer system, the payment token and a request for personal identifying information of the account holder from a first merchant; and

providing, by the token vault computer system, access to particular data fields of the account holder to the first merchant based on associated rules governing access to data fields associated with the account holder, the data fields including the personal identifying information of the account holder requested by the first merchant.

16. The method of claim 15 , wherein the payment token is generated by encrypting at least a portion of the financial product information.

17. The method of claim 15 , further comprising:

receiving, by the token vault computer system, a request to authorize a transaction involving the payment token;

authorizing, by the token vault computer system, the transaction based on the payment token; and

updating, by the token vault computer system, a status of the payment token based on the transaction.

18. The method of claim 15 , further comprising, prior to generating the payment token:

selecting, by the token vault computer system, a unique identifier for use as the payment token; and

determining, by the token vault computer system, that the unique identifier is available for use.

19. The method of claim 15 , further comprising:

transmitting, by the token vault computer system, a token eligibility request to a financial product issuer system; and

confirming, by the token vault computer system, that the financial product is eligible for tokenization based on a response to the token eligibility request received from the financial product issuer system.

20. The method of claim 15 , further comprising storing the encrypted payment token in a token repository of the token vault computer system.

Assignments (1)

Continuity (4)

References Cited (400)