US 12,008,639 B1Granted

System and method for closing financial accounts using event driven architecture

AssigneeUnited Services Automobile Association (USAA)

InventorsJason Paul Hendry, Rodney Kalich, Randall Martin Brandt, Marco Aldo Jimenez, David Perry

Life of this patent

Estimating the term…

Loading patent…

Abstract

A system and method of providing real time account information for financial accounts is disclosed. The system includes an event based architecture including an event stream. Financial transaction processing systems publish transaction events to the event stream. A transaction service listening to the event stream detects new transaction events. The transaction service takes action to enrich transaction data. A middleware system reconciles existing transactions and persists transaction records in long term storage. Prior to closing financial accounts, the system can retrieve a list of all scheduled and pending transactions and request that these transactions are canceled before closing the account.

Claims20

Dependent claims

A method for closing a financial account, comprising:

using an event stream system to provide an event driven architecture in a system for generating and using real time enriched financial transaction data;
detecting a transaction event for a financial transaction, the transaction event being published by a financial transaction processing system to an event stream in the system for generating and using real time enriched financial transaction data for subsequent use by event consumers, the transaction event being associated with transaction data;
sending a request to the system for generating and using real time enriched financial transaction data to enrich the transaction data, the enriching occurring in near real time immediately after the detection of the transaction event and being performed by a data enrichment Application Programming Interface;
receiving enriched transaction data from the data enrichment Application Programming Interface and publishing an enriched data event by an event producer to the event stream for use by the event consumers;
reconciling scheduled, manual, and pending transactions using a reconciliation Application Programming Interface to find completed and expired transactions received by a middleware for use when closing the financial account;
aggregating, by a data aggregator, enriched manual and scheduled transaction data from the financial transaction processing system and enriched pending and processed transaction data from the middleware to generate maintained enriched transaction data;
receiving an account closing request;
looking up a list of scheduled and pending transactions in enriched transaction records using the maintained enriched transaction data provided by the data aggregator;
determining sources of the scheduled and pending transactions from source data fields in the enriched transaction records;
using the maintained enriched transaction data and a source of the financial transaction to determine that the financial transaction has not posted, such that the financial transaction is a scheduled transaction, a manual transaction, or a pending transaction;
sending a request to the financial transaction processing system to cancel the financial transaction;
closing the financial account;
and
deactivating a credit card associated with the financial account.

11 more elements

A method for closing a financial account, comprising:

using an event stream system to provide an event driven architecture in a system for generating and using real time enriched financial transaction data;
detecting a transaction event for a financial transaction, the transaction event being published by a financial transaction processing system to an event stream in the system for generating and using real time enriched financial transaction data for subsequent use by event consumers, the transaction event being associated with transaction data;
sending a request to the system for generating and using real time enriched financial transaction data to enrich the transaction data, the enriching occurring in near real time immediately after the detection of the transaction event and being performed by a data enrichment Application Programming Interface;
receiving enriched transaction data from the data enrichment Application Programming Interface and publishing an enriched data event by an event producer to the event stream for use by the event consumers;
reconciling scheduled, manual, and pending transactions using a reconciliation Application Programming Interface to find completed and expired transactions received by a middleware for use when closing the financial account;
aggregating, by a data aggregator, enriched manual and scheduled transaction data from the financial transaction processing system and enriched pending and processed transaction data from the middleware to generate maintained enriched transaction data;
receiving an account closing request;
looking up a list of scheduled and pending transactions in enriched transaction records using the maintained enriched transaction data provided by the data aggregator;
determining sources of the scheduled and pending transactions from source data fields in the enriched transaction records;
using the maintained enriched transaction data and a source of the financial transaction to determine that the financial transaction has not posted, such that the financial transaction is a scheduled transaction, a manual transaction, or a pending transaction;
sending a request to the financial transaction processing system to cancel the financial transaction;
receiving a confirmation that the financial transaction has been canceled;
and
closing the financial account.

11 more elements

A method for closing a financial account, comprising:

using an event stream system to provide an event driven architecture in a system for generating and using real time enriched financial transaction data;
listening for transaction events published to an event stream;
detecting a transaction event for a financial transaction, the transaction event being published by a financial transaction processing system to an event stream in the system for generating and using real time enriched financial transaction data for subsequent use by event consumers, the transaction event being associated with transaction data;
sending a request to the system for generating and using real time enriched financial transaction data to enrich the transaction data, the enriching occurring in near real time immediately after the detection of the transaction event and being performed by a data enrichment Application Programming Interface;
receiving enriched transaction data from the data enrichment Application Programming Interface and publishing an enriched data event by an event producer to the event stream for use by the event consumers;
reconciling scheduled, manual, and pending transactions using a reconciliation Application Programming Interface to find completed and expired transactions received by a middleware for use when closing the financial account;
aggregating, by a data aggregator, enriched manual and scheduled transaction data from the financial transaction processing system and enriched pending and processed transaction data from the middleware to generate maintained enriched transaction data;
receiving an account closing request;
looking up a list of scheduled and pending transactions in enriched transaction records using the maintained enriched transaction data provided by the data aggregator;
determining sources of the scheduled and pending transactions from source data fields in the enriched transaction records;
using the maintained enriched transaction data and a source of the financial transaction to determine that the financial transaction has not posted, such that the financial transaction is a scheduled transaction, a manual transaction, or a pending transaction;
sending a request to the financial transaction processing system to cancel the financial transaction;
and
closing the financial account.

11 more elements

Dependencies are inferred from the claim text.

Facts

Application: 17/652,298Filed 24 Feb 2022 · continuation
Priority: 31 May 2019
Granted: 11 Jun 2024
Term ends: Not estimatedThe source records don’t support an estimate.

Classification5 codes

G06Q 40/02
Finance; Insurance; Tax strategies; Processing of corporate or income taxes: banking, e.g. interest calculation or account maintenance
G06Q 20/108
Specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems: remote banking, e.g. home banking
G06Q 20/389
Payment protocols; Details thereof: keeping log of transactions for guaranteeing non-repudiation of a transaction
G06Q 20/4016
Transaction verification: involving fraud or risk level assessment in transaction processing

Family

Application16/428,798Parent of this continuation · filed 31 May 2019
US 11,301,929 B1Parent of this continuation
US 12,008,639 B1This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key