Token management system

Patent metadata

Field	Value
Publication number	US-12205121-B2
Application number	US-202318392691-A
Country	US
Kind code	B2
Filing date	Dec 21, 2023
Priority date	Mar 27, 2015
Publication date	Jan 21, 2025
Grant date	Jan 21, 2025

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:
one or more processors, independently or collectively configured to:
determine restrictions to be placed on a payment token, wherein the restrictions restrict use of the payment token to payment via a payment mechanism and restrict data fields which a merchant is allowed to access;
generate a limited use key based the restrictions to be placed on the payment token;
provision the payment token and the limited use key based on a corresponding request, wherein the limited use key is separate from the payment token, and wherein the payment token is useable by the merchant to make a payment via the payment mechanism when the payment is in compliance with the limited use key that is transmitted with the payment token;
in response to being presented with the payment token and the limited use key, verify that the merchant is allowed to access a specific data field; and
in response to verifying that the merchant is allowed to access the specific data field, retrieving, the specific data field and transmitting the specific data field to the merchant.

2. The computer system of claim 1 , wherein the limited use key is derived from a master domain key.

3. The computer system of claim 1 , wherein the limited use key establishes a threshold, and wherein satisfaction of the threshold renders the payment token unusable.

4. The computer system of claim 3 , wherein the threshold comprises a threshold time period, and wherein the one or more processors, independently or collectively, are further configured to invalidate the payment token upon expiration of the threshold time period.

5. The computer system of claim 3 , wherein the threshold comprises a threshold speed by which funds are transmitted, and wherein the one or more processors, independently or collectively, are further configured to invalidate the payment token upon violation of the threshold speed by which funds are transmitted.

6. The computer system of claim 3 , wherein the threshold comprises a threshold number of transactions, and wherein the one or more processors, independently or collectively, are further configured to invalidate the payment token upon occurrence of a number of transactions with the payment token that satisfies the threshold number of transactions.

7. The computer system of claim 3 , wherein the one or more processors, independently or collectively, are further configured to selectively refresh an expired limited use key.

8. The computer system of claim 3 , wherein the one or more processors, independently or collectively, are further configured to store one or more expiration thresholds in a token database.

9. The computer system of claim 1 , wherein the one or more processors, independently or collectively, are further configured to determine the restrictions to be placed on the payment token based on the payment mechanism or an account holder of the payment mechanism.

10. A method of managing payment token usage, the method comprising:
determining, by a token vault computer system, restrictions to be placed on a payment token, wherein the restrictions restrict use of the payment token to payment via a payment mechanism and restrict data fields which a merchant is allowed to access;
generating, by the token vault computer system, a limited use key based on the restrictions to be placed on the payment token;
provisioning, by the token vault computer system, the payment token and the limited use key based on a corresponding request, wherein the limited use key is separate from the payment token, and wherein the payment token is useable by the merchant to make a payment via the payment mechanism when the payment is in compliance with the limited use key that is transmitted with the payment token;
in response to being presented with the payment token and the limited use key, verifying that the merchant is allowed to access a specific data field; and
in response to verifying that the merchant is allowed to access the specific data field, retrieving, by the token vault computer system, the specific data field and transmitting, by the token vault computer system, the specific data field to the merchant.

11. The method of claim 10 , wherein generating the limited use key comprises deriving the limited use key from a master domain key.

12. The method of claim 10 , wherein the limited use key establishes a threshold, the method further comprising:
monitoring, by the token vault computer system, a metric of the payment token associated with the threshold; and
rendering, by the token vault computer system, the payment token unusable upon determining that the metric satisfies the threshold.

13. The method of claim 12 , wherein the threshold comprises a threshold time period, and wherein the method further comprises rendering the payment token unusable upon expiration of the threshold time period.

14. The method of claim 12 , wherein the threshold comprises a threshold speed by which funds are transmitted, and wherein the method further comprises rendering the payment token unusable upon violation of the threshold speed by which funds are transmitted.

15. The method of claim 12 , wherein the threshold comprises a threshold number of transactions, and wherein the method further comprises rendering the payment token unusable upon occurrence of a number of transactions with the payment token that meets or exceeds the threshold number of transactions.

16. The method of claim 12 , further comprising selectively refreshing the limited use key for the payment token after the payment token has been rendered unusable.

17. The method of claim 12 , further comprising storing one or more expiration thresholds in a token database.

18. The method of claim 12 , further comprising determining the restrictions to be placed on the payment token based on the payment mechanism or an account holder of the payment mechanism.

19. A non-transitory computer-readable media having computer-executable instructions embodied therein that, when executed by a processor of a computing system, cause the computing system to perform operations comprising:
determining restrictions to be placed on a payment token, wherein the restrictions restrict use of the payment token to payment via a payment mechanism and restrict data fields which a merchant is allowed to access;
generating a limited use key based on the restrictions to be placed on the payment token;
provisioning the payment token and the limited use key based on a corresponding request, wherein the limited use key is separate from the payment token, and wherein the payment token is useable by the merchant to make a payment via the payment mechanism when the payment is in compliance with the limited use key that is transmitted with the payment token;
in response to being presented with the payment token and the limited use key, verifying that the merchant is allowed to access a specific data field; and
in response to verifying that the merchant is allowed to access the specific data field, retrieving the specific data field and transmitting the specific data field to the merchant.

20. The non-transitory computer-readable media of claim 19 , wherein generating the limited use key comprises deriving the limited use key from a master domain key, wherein the limited use key establishes a threshold, and wherein the computer-executable instructions, when executed by the processor of the computing system, cause the computing system to perform operations further comprising:
monitoring

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