US 11,797,962 B2
Configuring data transfers based on electronic messages
Christopher Mark Jones, Villanova, PA (US); Marc Chalifoux, Toronto (CA); and Sara Knechtel, Philadelphia, PA (US)
Assigned to The Toronto-Dominion Bank, Toronto (CA)
Filed by The Toronto-Dominion Bank, Toronto (CA)
Filed on Jun. 10, 2019, as Appl. No. 16/435,967.
Prior Publication US 2020/0387878 A1, Dec. 10, 2020
Int. Cl. G06Q 20/14 (2012.01); G06Q 40/02 (2023.01); G06F 21/31 (2013.01); G06Q 30/04 (2012.01); G06Q 10/107 (2023.01)
CPC G06Q 20/14 (2013.01) [G06F 21/31 (2013.01); G06Q 10/107 (2013.01); G06Q 30/04 (2013.01); G06Q 40/02 (2013.01)] 9 Claims
OG exemplary drawing
 
1. A resource server comprising:
a communication module;
a processor coupled to the communication module; and
a memory coupled to the processor, the memory storing instructions that, when executed, configure the processor for:
receiving, from a client device, an authentication credential including an OAuth token for querying keywords or expressions within a plurality of messages of a message account associated with a user of the client device;
associating the authentication credential with a client record of the user of the client device;
regulating frequencies of performing message scan operations for different recipients by prioritizing message scan operations to identify, by conducting optical character recognition and based on delegated access to query the message account at a message server using the authentication credential including the OAuth token, a first resource request message from a frequently paid recipient and corresponding to a bill payment notification among a plurality of messages associated with the message account using a defined keyword or expression criteria based on a list of domain names sorted by payment frequency, wherein a new domain name associated with the first resource request message is added to the list of domain names associated with the client record when not in the list of domain names, wherein a time stamp is recorded in the client record in relation to the frequently paid recipient when identifying the first resource request message and the recorded time stamp establishes a baseline threshold for a future message scan corresponding to the frequently paid recipient;
obtaining, by the optical character recognition and based on the first resource request message, a resource parameter to define a proposed resource transfer to a recipient entity;
generating and transmitting, to the client device, a first transfer request alert based on the defined proposed resource transfer for display on a non-messaging application interface at the client device, wherein the first transfer request alert includes the obtained resource parameter and a selectable option that includes a user interface element for confirming the defined proposed resource transfer;
receiving, from the client device, an authentication indication of the user via the non-messaging application;
in response to receiving, from the client device, a selection of the selectable option to confirm the defined proposed resource transfer and after receiving the authentication indication, allocating a resource associated with the resource parameter from the client record to a data record associated with the recipient entity,
wherein the allocating of the resource includes delaying, for cash flow planning, and based on a scheduling criteria defined by a cash threshold availability preference included in the client record, allocation of the resource until a date nearer to a due date associated with the first resource request message; and
after a period of time, conducting a subsequent message scan operation to identify a second resource request message from a next less frequently paid recipient.