	US 11,868,973 B2
	Automated multi-party event and transaction decisioning system
Vijay Sahebgouda Bantanur, Gaithersburg, MD (US); Muralidharan Balasubramanian, Gaithersburg, MD (US); and Julie Dallen, Vienna, VA (US)
Assigned to Capital One Services, LLC, McLean, VA (US)
Filed by Capital One Services, LLC, McLean, VA (US)
Filed on Aug. 19, 2021, as Appl. No. 17/406,688.
Prior Publication US 2023/0061296 A1, Mar. 2, 2023
Int. Cl. G06Q 20/04 (2012.01); G06Q 20/12 (2012.01); G06Q 20/34 (2012.01); G06Q 20/40 (2012.01)

CPC G06Q 20/047 (2020.05) [G06Q 20/123 (2013.01); G06Q 20/347 (2013.01); G06Q 20/40155 (2020.05)]

20 Claims

1. A computer-implemented method comprising:

receiving, by a computing device, first data comprising a plurality of first transactions associated with a first user;

detecting, in the first data, a first transaction, of the plurality of first transactions, associated with one or more merchant types associated with multi-party events;

retrieving, in response to detecting the first transaction and from a first device associated with the first user, second data comprising correspondence data or calendar data associated with the first user;

analyzing the second data to identify at least one correspondence or at least one calendar entry associated with the first transaction;

identifying, based on scanning the at least one correspondence or the at least one calendar entry, a location and a time associated with the first transaction, and a second user associated with the first transaction;

generating, by the computing device, based on identifying the location and the time associated with the first transaction and using a first machine learning model, a multi-party event comprising information identifying the identified location and the identified time, wherein the first machine learning model is trained based on training data comprising:

pre-labeled transactions indicating whether a training transaction record is a multi-party transaction or an individual transaction,

a transaction amount of the training transaction record,

a date and time associated with the training transaction record,

a type of merchant associated with the training transaction record,

a class of merchant associated with the training transaction record, and

a location of merchant associated with the training transaction record;

generating, by the computing device, a payment token for the multi-party event, wherein the payment token comprises a URL link to a script configured to access information on one or more delegation requests associated with the multi-party event;

storing, in a database, the multi-party event and the payment token;

associating, in the database, the first transaction with the multi-party event;

associating, in the database, the first user as a first party to the multi-party event and the second user as a second party to the multi-party event;

transmitting, to the first device associated with the first user, a notification indicating identification of the multi-party event; and

transmitting, to a second device associated with the second user, a delegation message comprising the payment token in an encrypted format.