Method and apparatus for managing transactions

• US 8,229,850 B2
• Filed: 11/30/2007
• Issued: 07/24/2012
• Est. Priority Date: 09/20/2000
• Status: Expired due to Fees

• Current Assignee: CashEdge Incorporated (Fiserv Incorporated)
• Original Assignee: CashEdge Incorporated (Fiserv Incorporated)
• Inventors: Dilip, Venkatachari, Dheer, Sanjeev, Sunderji, Amir, Singh, Param
• Primary Examiner(s): Patel, Jagdish
• Assistant Examiner(s): POE, KEVIN T
• Application Number:
  US11/949,012
• Publication Number:
  US 20080086403A1
• Time in Patent Office: 1,698 Days
• Field of Search: 705/40, 705/35, 705/42, 705/44
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/023 the neutral party being a clearing house
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

A system receives account access information from a user. The account is then accessed using the received access information. Data is harvested from a web page associated with the account or received from another financial data source. The user'"'"'s ability to access the account is authenticated based on the obtained information.

Claims

1. A computer-implemented method, comprising:

collecting, by a third-party financial management system comprising at least one computer, electronic user data comprising user identification (ID) information related to a user of the third-party financial system;

collecting, by the third-party financial management system, electronic user financial account information related to one or more accounts owned by the user, the data comprising account ID information, wherein the third-party financial management system communicates with the user, and with one or more financial institutions via at least one network;

collecting, by the third-party financial management system, electronic financial institution data comprising information about the one or more financial institutions;

defining, by the third-party financial management system, a set of one or more authentication rules to authenticate the user, wherein the set of authentication rules comprises one or more logic rules and one or more procedures;

receiving, by the third-party financial management system, electronic data comprising a request from the user to access one of the one or more accounts, wherein the request includes authentication information from the user comprising a user address, a user driver'"'"'s license number, and a user social security number, and wherein the request further comprises a user request to execute a financial transaction;

applying, by the third-party financial management system, the authentication rules to determine whether to authenticate the user;

when the user is successfully authenticated, retrieving, by the third-party financial management system, risk information related to the user, and to a requested transaction, wherein risk information comprises historical data related to user transactions, the historical data comprising dollar amounts and movement of funds between user accounts, including the overall behavior of the user as it relates to transfer of funds, success rate of transactions, and types of failure;

determining, by the third-party financial management system, whether a risk associated with the user and a risk associated with the requested financial transaction are acceptable; and

when the user is successfully authenticated, and the risk associated with the requested financial transaction is determined to be acceptable, determining, by the third-party financial management system, whether to allow access to the user account, wherein access includes the third-party financial management system executing the requested financial transaction on behalf of the user.

2. The method of claim 1 wherein risk information further comprises:

previous transaction history;

previous session history, including duration of account access;

account set-up history;

time elapsed since last transaction;

time elapsed since account added;

affiliations of an account with other users;

comparison of a geographic location of the request and geographic locations of previous requests, including determining distance between geographic locations, times of transactions executed from particular geographic locations, and types of connections used at particular geographic locations.

3. The method of claim 1, wherein determining whether to allow access to the user account comprises allowing conditional access to the user account, comprising imposing conditions including:

changing a dollar amount limit on a transaction;

changing a settlement period for a transaction; and

requiring additional authentication procedures.

4. The method of claim 1, further comprising updating the risk information based on requested user transactions and updated user information.

5. The method of claim 1, wherein the third-party financial management system collects user financial account information from the one or more financial institutions.

6. The method of claim 1, wherein the user information is collected in one or more manners selected from a group comprising, collecting directly from the user, collecting from an agency that holds user information, collecting from one of the one or more financial institutions, and screen-scraping the user information via one of the at least one networks.

7. A financial management system, comprising:

at least one computer, comprising,

a communication interface through which the financial management system communicates via at least one network with one or more financial institutions and with a user device;

a transaction execution module configurable to execute user-requested transactions with the one or more financial institutions on behalf of a user; and

an authentication and risk analysis module configured to automatically collect risk information comprising historical data related to user-requested transactions, the historical data comprising dollar amounts and movement of funds between user accounts, including the overall behavior of the user as it relates to transfer of funds, success rate of transactions, and types of failure, the module further configured to determine whether a risk associated with the user and a risk associated with the requested financial transaction are acceptable, and further configured to authenticate the user when the user requests a transaction.

8. The system of claim 7, wherein the authentication and risk analysis module is further configured to define a set of authentication rules to authenticate the user, and wherein authenticating the user comprises applying the authentication rules to determine whether to authenticate the user.

9. The system of claim 8, wherein application of the authentication rules results in one or more of initiation of an additional authentication process and issuance of a one-time useable password.

11. The system of claim 8, wherein determining whether to authenticate the user comprises conditionally authenticating the user, comprising imposing conditions on the transaction, including:

changing a dollar amount limit on the transaction;

changing a settlement period for the transaction;

requiring additional authentication procedures; and

rerouting the transaction through another channel.

12. The system of claim 7, further comprising updating the risk information based on requested user transactions and updated user information.

13. The system of claim 7, wherein the authentication and risk analysis module collects user financial account information from the one or more financial institutions.

14. The system of claim 7, wherein the authentication and risk analysis module collects the user information in one or more manners selected from a group comprising, collecting directly from the user, collecting from an agency that holds user information, collecting from one of the plurality of financial institutions, and screen-scraping the user information via one of the at least one networks.

15. The system of claim 7, wherein executing the user-requested transaction comprises:

in a first part of the transaction, the financial management system executing a transaction with a first financial institution;

the financial management system holding the funds from the transaction in an intermediate account owned by the financial management system at a third financial institution; and

in a second part of the transaction, the financial management system executing a transaction with a second financial institution to deposit the funds in an account at the second financial institution.

16. The system of claim 7, wherein the authentication and risk analysis module comprises:

an authentication and risk analysis engine; and

a user account information collection module coupled to the authentication and risk analysis engine, wherein the authentication and risk analysis engine is configurable to apply authentication rules and to determine a level of risk associate with a user-requested transaction.

17. The system of claim 16, wherein determining the level of risk includes computing a probability of risk.

18. The system of claim 7, wherein the authentication and risk analysis module further comprises a user an authentication analysis logic module coupled to the authentication and risk analysis engine, wherein the user authentication analysis module is configurable to develop authentication rules.

19. The system of claim 7, wherein the authentication and risk analysis module further comprises a risk analysis logic module coupled to the authentication and risk analysis engine, wherein the risk analysis module is configurable to analyze risk information.

20. The system of claim 7, wherein the authentication and risk analysis module further comprises a financial institution and market data collection module coupled to the authentication and risk analysis engine.

10. The system of 9, wherein the risk information further comprises:

previous transaction history;

previous session history, including duration of account access;

account set-up history;

time elapsed since last transaction;

time elapsed since account added;

affiliations of an account with other users;

comparison of a geographic location of the request and geographic locations of previous requests, including determining distance between geographic locations, times of transactions executed from particular geographic locations, and types of connections used at particular geographic locations.

21. A non-transitory computer-readable medium having stored thereon instructions, that when executed, cause method to be performed by at least one processor, the method comprising:

collecting, by a third-party financial management system, user information comprising user identification (ID) information related to a user of the third-party financial system;

collecting, by the third-party financial management system, user financial account information related to one or more accounts owned by the user, wherein the third-party financial management system communicates with the user and one or more financial institutions via at least one network;

collecting, by the third-party financial management system, information about the one or more financial institutions;

defining, by the third-party financial management system, a set of one or more authentication rules to authenticate the user, wherein the set of authentication rules comprises one or more logic rules and one or more procedures;

receiving, by the third-party financial management system, a request from the user to access one of the one or more accounts, wherein the request includes authentication information from the user comprising a user address, a user driver'"'"'s license number, and a user social security number, and wherein the request further comprises a user request to execute a financial transaction;

applying, by the third-party financial management system, the authentication rules to determine whether to authenticate the user;

when the user is successfully authenticated, retrieving, by the third-party financial management system, risk information related to the user, wherein risk information comprises historical data related to user transactions a transaction execution module configurable to execute user-requested transactions with the one or more financial institutions on behalf of the user;

automatically collecting, by an authentication and risk analysis module of the third-party financial management system, risk information comprising historical data related to user-requested transactions, the historical data comprising dollar amounts and movement of funds between user accounts, including the overall behavior of the user as it relates to transfer of funds, success rate of transactions, and types of failure, the module further configured to determine whether a risk associated with the user and a risk associated with the requested financial transaction are acceptable; and

when the user is successfully authenticated, the third-party financial management system determining whether to allow access to the user account, wherein access includes the third-party financial management system executing a requested transaction on behalf of the user.

22. The computer-readable medium of claim 21, wherein determining whether to allow access to the user account comprises allowing conditional access to the user account, comprising imposing conditions including:

changing a dollar amount limit on a transaction;

changing a settlement period for a transaction;

requiring additional authentication procedures; and

rerouting the transaction through another channel.

23. The computer-readable medium of claim 21, wherein the method further comprises updating the risk information based on requested user transactions and updated user information.

24. The computer-readable medium of claim 21, wherein the third-party financial management system collects user financial account information from the one or more financial institutions.

25. The computer-readable medium of claim 21, wherein the user information is collected in one or more manners selected from a group comprising, collecting directly from the user, collecting from an agency that holds user information, collecting from one of the one or more financial institutions, and screen-scraping the user information via one of the at least one networks.