# US 2020/0265406 A1 · Systems and methods for transaction management

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

- Number: US 2020/0265406 A1
- Document ID: US20200265406A1
- Status: Published application
- Kind: A1
- Application number: 16/681,794
- Filed: 2019-11-12
- Published: 2020-08-20
- Earliest claimed: 2019-02-20
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Walter Avery Miller; Jason E. Ferrell; Troy Alan Dye; Robert A. Martin; Jordan Fischer
- Web page: https://patentgrep.com/patent/US20200265406A1

## CPC

- G06Q 30/0236: {Incentive or reward received by requiring registration or ID from user}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06N 20/00: Machine learning
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 20/108: {Remote banking, e.g. home banking}
- G06Q 20/223: {based on the use of peer-to-peer networks}
- G06Q 20/34: using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q 20/3674: {involving authentication}
- G06Q 20/3676: {Balancing accounts}
- G06Q 20/382: {insuring higher security of transaction}
- G06Q 20/387: {Payment using discounts or coupons (relating to marketing G06Q30/02)}
- G06Q 20/4037: {Remote solvency checks}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q 30/0215: {Including financial accounts}
- G06Q 30/0233: {Method of redeeming a frequent usage reward}
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/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)}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04L 63/10: {for controlling access to devices or network resources}
- G06N 3/08: Learning methods
- G06Q 2220/00: Business processing using cryptography
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for P2P transaction functionality include transaction management. A system includes at least one processor and a storage medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations including identifying possible trigger transactions and creating a transaction bucket associated with the identified one or more participants. The operations also include performing calculations of amounts currently owed by each of the one or more participants, receiving a trigger event from the cardholder device. and sending notifications to the P2P service system asking for repayment based on the calculated amounts.

## Claims

### Claim 1

A financial service provider system for transaction management of a cardholder of a card issued by the financial service provider system, the system comprising:
at least one processor; and
a storage medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
receiving transaction information from a first vendor where the card of the cardholder was used;
analyzing the transaction information on the card;
identifying, based on the analysis, possible trigger transactions;
sending a notification based on the identification of at least one of the possible trigger transactions to a cardholder device of the cardholder based on the identification as the possible trigger transaction;
receiving a confirmation of the possible trigger transaction from the cardholder device;
based on the confirmation, sending to the cardholder device a request for additional information from the cardholder including identification of one or more participants in the possible trigger transaction and a P2P service system account identifier;
receiving, from the cardholder device, the identifications of one or more participants and the P2P service system account identifier;
creating a transaction bucket based on the confirmation and associated with the identified one or more participants;
receiving information regarding an additional transaction from a second vendor;
analyzing the additional transaction information;
based on the analysis of the additional transaction, associating the additional transaction with the transaction bucket;
performing calculations of amounts currently owed by each of the one or more participants;
receiving at least one cardholder trigger event from the cardholder device, wherein the at least one cardholder trigger event includes at least a date of repayment;
sending notifications to a P2P service system based on the cardholder trigger event asking for a repayment based on the calculated amounts; and
closing the transaction bucket after receiving an instruction from the cardholder.

### Claim 2 (depends on 1)

The system of claim 1, wherein analysis of the transaction information is performed using machine learning, neural networks, or a categorical approach.

### Claim 3 (depends on 1)

The system of claim 1, wherein the identification of one or more participants is a list.

### Claim 4 (depends on 3)

The system of claim 3, the operations further comprising:
including one or more secondary spenders from the list of participants based on a request from the one or more participants.

### Claim 5 (depends on 4)

The system of claim 4, the operations further comprising:
enabling the one or more secondary spenders to join the transaction bucket.

### Claim 6 (depends on 5)

The system of claim 5, the operations further comprising:
adding one or more secondary spender's transactions to the transaction bucket.

### Claim 7 (depends on 6)

The system of claim 6, the operations further comprising:
tagging the one or more secondary spender's transactions with identifying information.

### Claim 8 (depends on 1)

The system of claim 1, wherein the transaction bucket is recorded on to a blockchain.

### Claim 9 (depends on 8)

The system of claim 8, wherein the blockchain is shared between financial service provider system and P2P service system.

### Claim 10 (depends on 8)

The system of claim 8, wherein the blockchain comprises all the transactions associated with an event and is split into blocks based on the P2P service systems used for repayment associated with the one or more participants.

### Claim 11 (depends on 8)

The system of claim 8, wherein the blockchain comprises all the transactions associated with an event and is split into blocks based on individual transactions including tracking repayment by each of the one or more participants.

### Claim 12 (depends on 1)

The system of claim 1, wherein the repayment is requested automatically based on closing the transaction bucket.

### Claim 13 (depends on 1)

The system of claim 1, wherein the repayment is requested periodically based on preconfigured trigger events.

### Claim 14

A P2P service provider system for a system for transaction management of a cardholder of a card issued by a financial service provider system, the system comprising:
at least one processor; and
a storage medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
initiating a link with the financial service provider system to enable data communication;
receiving from the financial service provider system one or more requests for payment;
based on the received one or more requests, identifying one or more secondary users of the P2P service provider system associated with the requests for payment;
receiving from the financial service provider system identities of one or more trigger events for payments;
sending, based on the one or more trigger events for payments, the one or more requests for payment to the one or more secondary users of the P2P service provider system;
receiving payment in response to at least one of the sent requests for payment from at least one of the secondary users of the P2P service provider system; and
sending the received payment to the financial service provider system.

### Claim 15 (depends on 14)

The system of claim 14, wherein initiating the link with the financial service provider system systems comprises establishing a deep link.

### Claim 16 (depends on 14)

The system of claim 14, wherein initiating the link with the financial service provider system systems comprises establishing an API link.

### Claim 17 (depends on 14)

The system of claim 14, wherein initiating the link comprises validation based on public and private shared information.

### Claim 18 (depends on 14)

The system of claim 14, the operations further comprising:
performing calculations of amounts currently owed by each of the one or more secondary users.

### Claim 19 (depends on 18)

The system of claim 18, wherein the one or more requests for payment is based on the performed calculations.

### Claim 20

A cardholder system of a cardholder device of a cardholder of a card issued by the financial service provider system, the system comprising:
at least one processor; and
a storage medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
executing an integrated solution to social trip management and planning, wherein the integrated solution comprises a P2P application connected via deep-linking to a financial service provider system and a P2P service system;
receiving a notification from a financial service provider system that a transaction is a possible event type;
prompting the cardholder to provide information required for creation of a transaction bucket;
sending the information to the financial service provider system;
receiving one or more automatic transaction tags associated with the transaction bucket from the financial service provider system;
enabling the cardholder to modify the automatic transaction tags within the transaction bucket;
receiving identification of specific trigger events, based on cardholder input;
transmitting the trigger event identifications to the financial service provider system; and
initiating closure of the bucket, based on cardholder input, by sending a request to the financial service provider system.
