# US 2023/0410170 A1 · Optimized management of transaction requests

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

- Number: US 2023/0410170 A1
- Document ID: US20230410170A1
- Status: Published application
- Kind: A1
- Application number: 17/840,872
- Filed: 2022-06-15
- Published: 2023-12-21
- Earliest claimed: 2022-06-15
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Bharath CHEKURI; Isha MEHTA; Esmeralda CERVANTES; Swati SARAF; Poojitha PONUGOTI
- Web page: https://patentgrep.com/patent/US20230410170A1

## CPC

- G06Q 30/0613: {using intermediate agents}
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- G06Q 30/0641: {utilising user interfaces specially adapted for shopping}
- 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 device (e.g., a server, a cloud-based device, a request management device, etc.), for example, such as a computing device associated with a vehicle dealership and/or the like, may receive a plurality of transaction requests, such as requests to purchase, lease, and/or finance a vehicle. Each transaction request may include user information associated with the transaction, such as a phone number, a home/mailing address, email address, a credit score, vehicle trade-in information, and/or any other data elements. For each transaction request, the computing device may invoke one or more microservices to verify data elements of user information and use responses from the microservices to rank each transaction requests on its potential to progress to a completed transaction.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving a plurality of transaction requests, wherein each transaction request comprises respective user information, wherein the respective user information comprises data elements associated with the transaction request;
for each transaction request of the plurality of transaction requests:
determining, based on the data elements associated with the transaction request, respective microservices, wherein each microservice of the respective microservices is tasked to verify a respective data element of the data elements,
sending to a microservice component of each microservice of the respective microservices, a request to verify the respective data element, and
determining, based on a number of responses from the microservice components for each of the respective microservices indicating that the respective data elements are verified, a rank for the transaction request; and
determining, based on the rank for each transaction request of the plurality of transaction requests, a highest ranked transaction request.

### Claim 2 (depends on 1)

The method of claim 1, wherein the receiving the plurality transaction requests comprises receiving the plurality transaction requests via at least one of a user interface or a merchant webpage.

### Claim 3 (depends on 1)

The method of claim 1, wherein, for each transaction request of the plurality of transaction requests, the data elements comprises at least one of an email address, a phone number, credit history information, an indication of a value of an asset, or transaction history information.

### Claim 4 (depends on 1)

The method of claim 1, wherein, for each transaction request of the plurality of transaction requests, determining the respective microservices comprises:
determining a type for each of the data elements; and
determining that each microservice of the respective microservices is associated with at least one type of the types of the data elements.

### Claim 5 (depends on 1)

The method of claim 1, further comprising sending, to a user device, at least one of an indication of the highest-ranked transaction request or the respective user information for the highest-ranked transaction request.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
determining, based on the rank for each transaction request of the plurality of transaction requests, a portion of the plurality of transaction requests, wherein the rank for each transaction request of the portion of transaction requests satisfy a ranking threshold; and
sending, to a user device, at least one of an indication of the portion of transaction requests that satisfy the ranking threshold or the respective user information for the portion of transaction requests that satisfy the ranking threshold.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
determining, based on the rank for each transaction request of the plurality of transaction requests, a portion of the plurality of transaction requests, wherein the rank for each transaction request of the portion of transaction requests is less than a ranking threshold; and
sending a request for additional data elements to a respective user device associated with each transaction request of the portion of transaction requests.

### Claim 8

A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:
receiving a plurality of transaction requests, wherein each transaction request comprises respective user information, wherein the respective user information comprises data elements associated with the transaction request;
for each transaction request of the plurality of transaction requests:
determining, based on the data elements associated with the transaction request, respective microservices, wherein each microservice of the respective microservices is tasked to verify a respective data element of the data elements,
sending to a microservice component of each microservice of the respective microservices, a request to verify the respective data element, and
determining, based on a number of responses from the microservice components for each of the respective microservices indicating that the respective data elements are verified, a rank for the transaction request; and
determining, based on the rank for each transaction request of the plurality of transaction requests, a highest ranked transaction request.

### Claim 9 (depends on 8)

The non-transitory computer-readable device of claim 8, wherein the receiving the plurality transaction requests comprises receiving the plurality transaction requests via at least one of a user interface or a merchant webpage.

### Claim 10 (depends on 8)

The non-transitory computer-readable device of claim 8, wherein, for each transaction request of the plurality of transaction requests, the data elements comprises at least one of an email address, a phone number, credit history information, an indication of a value of an asset, or transaction history information.

### Claim 11 (depends on 8)

The non-transitory computer-readable device of claim 8, wherein, for each transaction request of the plurality of transaction requests, the determining the respective microservices comprises:
determining a type for each of the data elements; and
determining that each microservice of the respective microservices is associated with at least one type of the types of the data elements.

### Claim 12 (depends on 8)

The non-transitory computer-readable device of claim 8, further comprising sending, to a user device, at least one of an indication of the highest-ranked transaction request or the respective user information for the highest-ranked transaction request.

### Claim 13 (depends on 8)

The non-transitory computer-readable device of claim 8, further comprising:
determining, based on the rank for each transaction request of the plurality of transaction requests, a portion of the plurality of transaction requests, wherein the rank for each transaction request of the portion of transaction requests satisfy a ranking threshold; and
sending, to a user device, at least one of an indication of the portion of transaction requests that satisfy the ranking threshold or the respective user information for the portion of transaction requests that satisfy the ranking threshold.

### Claim 14 (depends on 8)

The non-transitory computer-readable device of claim 8, further comprising:
determining, based on the rank for each transaction request of the plurality of transaction requests, a portion of the plurality of transaction requests, wherein the rank for each transaction request of the portion of transaction requests is less than a ranking threshold; and
sending a request for additional data elements to a respective user device associated with each transaction request of the portion of transaction requests.

### Claim 15

A system comprising:
a memory; and
at least one processor coupled to the memory and configured to:
receive a plurality of transaction requests, wherein each transaction request comprises respective user information, wherein the respective user information comprises data elements associated with the transaction request;
for each transaction request of the plurality of transaction requests:
determine, based on the data elements associated with the transaction request, respective microservices, wherein each microservice of the respective microservices is tasked to verify a respective data element of the data elements,
sending to a microservice component of each microservice of the respective microservices, a request to verify the respective data element, and
determining, based on a number of responses from the microservice components for each of the respective microservices indicating that the respective data elements are verified, a rank for the transaction request; and
determining, based on the rank for each transaction request of the plurality of transaction requests, a highest ranked transaction request.

### Claim 16 (depends on 15)

The system of claim 15, wherein the at least one processor configured to receive the plurality transaction requests is further configured to receive the plurality transaction requests via at least one of a user interface or a merchant webpage.

### Claim 17 (depends on 15)

The system of claim 15, wherein, for each transaction request of the plurality of transaction requests, the data elements comprises at least one of an email address, a phone number, credit history information, an indication of a value of an asset, or transaction history information.

### Claim 18 (depends on 15)

The system of claim 15, wherein, for each transaction request of the plurality of transaction requests, the at least one processor configured to determine the respective microservices is further configured to:
determine a type for each of the data elements; and
determine that each microservice of the respective microservices is associated with at least one type of the types of the data elements.

### Claim 19 (depends on 15)

The system of claim 15, wherein the at least one processor is further configured to send, to a user device, at least one of an indication of the highest-ranked transaction request or the respective user information for the highest-ranked transaction request.

### Claim 20 (depends on 15)

The system of claim 15, wherein the at least one processor is further configured to:
determine, based on the rank for each transaction request of the plurality of transaction requests, a portion of the plurality of transaction requests, wherein the rank for each transaction request of the portion of transaction requests satisfy a ranking threshold; and
send, to a user device, at least one of an indication of the portion of transaction requests that satisfy the ranking threshold or the respective user information for the portion of transaction requests that satisfy the ranking threshold.
