System and method for enabling multiple auxiliary use of an access token of a user by another entity to facilitate an action of the user

Patent metadata

Field	Value
Publication number	US-12301575-B2
Application number	US-202318322535-A
Country	US
Kind code	B2
Filing date	May 23, 2023
Priority date	May 3, 2022
Publication date	May 13, 2025
Grant date	May 13, 2025

Abstract

A computing system may receive a request of the user for a first action of the user with an entity. In connection with granting the request of the user, the computing system may configure a token for use by the user and the entity such that (i) the entity is added as an approved entity, and (ii) the token is configured with a resource amount of the first action as a usage threshold of the token. The computing system may receive a request of the entity to use the token. The computing system may determine whether granting the request of the entity would cumulatively exceed the usage threshold of the token. Based on a determination that granting the request of the entity would not cumulatively exceed the resource usage of the token, the computing system may grant the request of the entity to use the token.

First claim

What is claimed is:

1. A system for enabling multiple third-party auxiliary to use a token to facilitate a token-owner-initiated network operation with a third party, the system comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause operations comprising:
in response to detecting a token-owner-initiated request to use a token for a transaction associated with a token owner user with a third-party entity, configuring the token for multiple auxiliary uses by the third-party entity for the transaction, wherein configuring the token comprises configuring the token as a single-use virtual token for multiple auxiliary uses by the third-party entity for the transaction, wherein (i) the third-party entity is added as an auxiliary entity that is approved to use the token to complete the transaction associated with the token owner user, and (ii) the token is configured with a resource amount as a resource amount usage threshold associated with the transaction;
after granting a first third-party request of the third-party entity to use the token for a first subpart of the transaction, receiving a second third-party request of the third-party entity to continue use of the token for a second subpart of the transaction, the first subpart of the transaction corresponding to a first amount of resources, the second subpart corresponding to a second amount of resources;
determining whether a sum comprising the first amount and the second amount would exceed the resource amount usage threshold of the token;
granting the second third-party request to use the token based on a determination that the sum would not exceed the token's resource amount usage threshold associated with the transaction;
after granting the first and second third-party requests of the third-party entity, receiving at least one other third-party request of the third-party entity to use the token for at least one other subpart of the transaction; and
denying the at least one other third-party request based on at least one other resource amount of the at least one other third-party request cumulatively exceeding the resource amount usage threshold of the token.

2. The system of claim 1 , the operations further comprising:
receiving at least one third-party request of a second third-party entity to use the token;
in response to receiving the at least one third-party request of the second third-party entity, determining whether the token has been configured with the second third-party entity as the auxiliary entity; and
in response to determining that the token has not been configured with the second third-party entity as the auxiliary entity, denying the at least one third-party request of the second third-party entity.

3. The system of claim 1 , wherein granting the second third-party request to use the token comprises:
determining whether the second third-party request is received before a threshold date associated with the transaction; and
granting the second third-party request in response to (i) determining that the resource amount would not cumulatively exceed the resource amount usage threshold of the token, and (ii) determining that the second third-party request is received before the threshold date associated with the transaction.

4. A method comprising:
detecting a token-owner-initiated request to use a token for a transaction associated with a token owner user with a third-party entity;
configuring the token for multiple auxiliary uses by the third-party entity for the transaction, wherein configuring the token comprises configuring the token as a single-use virtual token for multiple auxiliary uses by the third-party entity for the transaction, wherein (i) the third-party entity is added as an auxiliary entity that is approved to use the token to complete the transaction associated with the token owner user, and (ii) the token is configured with a resource amount as a resource amount usage threshold associated with the transaction;
after granting a first third-party request of the third-party entity to use the token for a first subpart of the transaction, receiving a second third-party request of the third-party entity to continue use of the token for a second subpart of the transaction, the first subpart of the transaction corresponding to a first amount of resources, the second subpart corresponding to a second amount of resources;
determining that a sum comprising the first amount and the second amount would not exceed the resource amount usage threshold of the token;
granting the second third-party request to use the token based on the determination that the sum would not exceed the token's resource amount usage threshold associated with the transaction;
after granting the first and second third-party requests of the third-party entity, receiving at least one other third-party request of the third-party entity to use the token for at least one other subpart of the transaction; and
denying the at least one other third-party request based on at least one other resource amount of the at least one other third-party request cumulatively exceeding the resource amount usage threshold of the token.

5. The method of claim 4 , further comprising:
after configuring the token for use by the third-party entity for the transaction associated with the token owner user, receiving at least one additional third-party request of the third-party entity to use the token for at least one other transaction associated with the token owner user, the at least one other transaction being independent of the transaction associated with the token owner user;
determining that the token has not been configured for use with the at least one other transaction associated with the token owner user; and
denying the at least one other third-party request based on the determination that the token has not been configured for use with the at least one other transaction.

6. The method of claim 4 , further comprising:
receiving at least one third-party request of a second third-party entity to use the token;
determining that the token has not been configured with the second third-party entity as the auxiliary entity; and
denying the at least one third-party request of the second third-party entity based on the determination that the token has not been configured with the second third-party entity as the auxiliary entity.

7. The method of claim 4 , wherein granting the second third-party request to use the token comprises:
determining that the second third-party request is received before a threshold date related to the transaction; and
granting the second third-party request based on (i) the determination that the resource amount would not cumulatively exceed the resource amount usage threshold of the token, and (ii) the determination that the second third-party request is received before the threshold date.

8. The method of claim 4 , wherein configuring the token for use by the third-party entity comprises:
determining, for the resource amount usage threshold of the token, the resource amount based on input from the token owner user indicating a total amount of resources to be used by the third-party entity for the transaction.

9. The method of claim 4 , further comprising:
receiving a second user request of the token owner user to use the token for the transaction; and
granting the second user request of the token owner user to use the token for the transaction.

10. The method of claim 4 , wherein the token comprises a virtual card number, and wherein the token is configured with an overall transaction amount of the transaction as the resource amount usage threshold associated with the

Assignees

• Capital One Services Llc

Inventors

• Douglas Lawrence

Classifications

• H04L9/0894

  Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage · CPC title

• H04L63/108

  when the policy decisions are valid for a limited amount of time · CPC title

• H04L9/3228

  One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key · CPC title

• H04L9/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) · CPC title

• H04L2209/56

  Financial cryptography, e.g. electronic payment or e-cash · CPC title