Patent Application
20100274698
1. Technical Field
This invention relates to a method and system for management of credit limits in a financial transaction. More specifically, the invention relates to employing and managing a soft credit limit for an underlying financial account for management of one or more financial transactions.
2. Description of the Prior Art
A credit limit is the maximum amount of credit that a bank or other lender will extend to a customer, or the maximum that a credit card company will allow a card holder to borrow on a single card. More specifically, a credit limit is the explicit borrowing ceiling set by a lender for a particular customer. The credit facility having a credit limit can take many forms, both secured and unsecured. The line of credit, letter of credit, and credit card all have a credit limit. An example of secured debt would be the home equity line of credit, where the credit limit decision would take into account the amount of home equity accumulated. On the other hand, the credit limit on a credit card, which is unsecured, would be based entirely upon creditworthiness.
Credit limits are employed by financial institutions as a tool to control borrowing and lending of money. Based upon available funds and historical usage of funds, the financial institution will employ a mathematical formula to determine the credit limit for an individual or business entity. It is the responsibility of the individual or business entity to properly manage the credit limit to ensure that they do not borrow money in excess of the credit limit. However, there are circumstances when the credit limit is exceeded and this is out of the control of the individual or business entity. For example, in the case of a credit card that is stolen or used by an unauthorized person, the credit limit may be exceeded because the user of the card is not aware of the credit limit.
To enforce the theory of the credit limits, the financial institution underwriting the credit limit may apply a surcharge for one or more transactions that exceed the credit limit. This enforcement is a tool to mitigate abuse of exceeding the credit limit. At the same time, the financial institution may not approve any transaction that will cause the credit limit to be exceeded. Accordingly, the credit limit may be an actual monetary ceiling which the financial institution will not allow to be exceeded.
The credit limit described above is a hard limit in that once this value is exceeded there is no credit remaining. However, there is no warning system that informs an account holder that they are nearing the credit limit. The account holder may have a plurality of accounts with each account having different credit limit. Therefore, the account holder may not be aware that a transaction will cause the account to exceed the credit limit as they are submitting a transaction to the financial institution.
There is a need to apply a tool in the credit market to ensure that a credit limit is not attained or exceeded for either a specific transaction or a combination of transactions. The tool should inform an authorized account holder that the credit limit is nearing prior to execution of the transaction. In addition, there is a need to apply a tool in the credit market to maintain control of the account by limiting credit authorization on a transaction basis. The credit limits applied with the tool are an added layer of security to the prior art hard credit limit, and function in conjunction therewith.
This invention comprises a method, system, and article for creation and management of a soft credit limit for an underlying financial account.
In one aspect of the invention, a method is provided for management of an underlying financial account. A hard credit limit is established for the underlying account. Additionally, a soft credit limit is employed for the underlying financial account. The soft credit limit is any credit amount this is less than or equal to the hard credit limit. A value for the soft credit limit is set, and one or more transactions on the account are monitored. The process of monitoring the account includes both the hard and soft credit limits. Authorization of the transaction is declined in response to the transaction exceeding the soft credit limit, and the transaction is allowed in response to the transaction being less than both of the credit limits. A declined transaction includes prevention of completion of the transaction. Similarly, allowance of the transaction includes completion of the transaction.
In another aspect of the invention, a computer system is provided with a processor in communication with memory. A financial account is provided on a remote server with a hard credit limit. A transaction on the account that exceeds the hard credit limit is considered a fraudulent activity. Similarly, a soft credit limit is established by a user manager in communication with the account. The soft credit limit is any credit amount less than or equal to the hard credit limit. A transaction manager is provided local to the server and in communication with the user manager to monitor a transaction to the account. The transaction manager oversees both the hard and soft credit limits. More specifically, the transaction manager declines authorization of the transaction in response to the transaction exceeding at least one of the credit limits, and the transaction manager allows the transaction in response to the transaction being less than both of the credit limits.
In yet another aspect of the invention, an article is provided with a computer-readable carrier including computer program instructions configured to manage an underlying financial account. Instructions are provided to establish a hard credit limit for the underlying account, and to employ a soft credit limit for the underlying financial account. The soft credit limit is any credit amount this is less than or equal to the hard credit limit. In addition, instructions are provided to set a value for the soft credit limit, and to monitor a transaction to the account. The monitoring instructions oversee both the hard and soft credit limits set for the account. Authorization of the transaction is declined in response to the transaction exceeding the soft credit limit, and allowed in response to the transaction being less than both of the credit limits.
Other features and advantages of this invention will become apparent from the following detailed description of the presently preferred embodiment of the invention, taken in conjunction with the accompanying drawings.
The drawings referenced herein form a part of the specification. Features shown in the drawing are meant as illustrative of only some embodiments of the invention, and not of all embodiments of the invention unless otherwise explicitly indicated. Implications to the contrary are otherwise not to be made.
It will be readily understood that the components of the present invention, as generally described and illustrated in the Figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the apparatus, system, and method of the present invention, as presented in the Figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention.
The functional units described in this specification have been labeled as a manager. A manager may be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. The manager may also be implemented in software for execution by various types of processors. An identified manager of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, function, or other construct. Nevertheless, the executables of an identified manager need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the manager and achieve the stated purpose of the manager.
Indeed, a manager of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different applications, and across several memory devices. Similarly, operational data may be identified and illustrated herein within the manager, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, as electronic signals on a system or network.
Reference throughout this specification to “a select embodiment,” “one embodiment,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “a select embodiment,” “in one embodiment,” or “in an embodiment” in various places throughout this specification are not necessarily referring to the same embodiment.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of recovery manager, authentication module, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The illustrated embodiments of the invention will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. The following description is intended only by way of example, and simply illustrates certain selected embodiments of devices, systems, and processes that are consistent with the invention as claimed herein.
A soft limit is a user implemented tool for managing usage of credit with a financial institution. The soft limit is employed to ensure that the hard limit is not exceeded, and/or that an individual transaction does not exceed a set value. Once the soft credit is established with a financial account, it may be adjusted and/or evaluated to ascertain pattern of usage.
In the following description of the embodiments, reference is made to the accompanying drawings that form a part hereof, and which shows by way of illustration the specific embodiment in which the invention may be practiced. It is to be understood that other embodiments may be utilized because structural changes may be made without departing form the scope of the present invention.
As noted above, there are different parameters that may be invoked for establishing and defining the soft credit limit.
The soft credit limit may be employed by the user to facilitate management of their financial account, and at the same time, may be employed as a fraud prevention tool by both the account user and the underlying financial institution.
Once the soft credit limit is applied to the underlying account, it affects all transactions on the account. If a transaction exceeds a parameter of the soft credit limit, the transaction will be rejected. The establishment of the soft credit limit is as effective as a hard credit limit. However, one significant distinction is that the soft credit limit is established by the user of the account, and not by the underlying financial institution. If the user wants to proceed with a transaction that does not abide by the established parameters of the soft credit limits, they can change the selected parameters for the transaction, and then re-establish the prior parameters for the account.
As shown in
A user manager (450) is provided local to the computer system (402) and in communication with a transaction manager (460) local to the remote server (420). The user manager functions to establish a soft credit limit for an underlying financial account. The soft credit limits is any credit amount less than or equal to the hard credit limit. The transaction manager (460) functions to monitor a transaction with the account, including both the hard and soft credit limits. More specifically, the transaction manager (460) declines authorization of the transaction in response to the transaction exceeding at least one of the credit limits, and the transaction manager (460) allows the transaction in response to the transaction being less than both of the credit limits. An additional manager is provided in the form of a fraud manager (470). As shown, the fraud manager (470) is local to the remote server and is responsible for monitoring transactions declined in violation of the soft credit limit and evaluating a pattern associated with the declined transactions.
In one embodiment, user manager (450) may reside in memory (406) local to the computer system (402). Similarly, the transaction and fraud managers (460) and (470), respectively, may reside in memory (426) local to the remote server (420). However, the invention should not be limited to this embodiment. For example, in one embodiment, each of the managers (450), (460), and/or (470) may reside as hardware tools external to local memory of the respective computer system (402) and remote server (420), or they may be implemented as a combination of hardware and software. Similarly, in one embodiment, the managers (450), (460), and (470) may reside on a remote system in communication with the storage media (422). Accordingly, the managers may be implemented as a software tool or a hardware tool to employ and manage soft credit limits of a financial account.
In one embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc. The invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
Embodiments within the scope of the present invention also include articles of manufacture comprising program storage means having encoded therein program code. Such program storage means can be any available media which can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such program storage means can include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired program code means and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included in the scope of the program storage means.
The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, random access memory (RAM), read-only memory (ROM), a rigid magnetic disk, and an optical disk. Current examples of optical disks include compact disk B read only (CD-ROM), compact disk B read/write (CD-R/W) and DVD.
A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks.
The software implementation can take the form of a computer program product accessible from a computer-useable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system.
Soft credit limits are employed with respect to a financial account as a tool for management thereof by both the user and an associated fraud prevention tool or manager. The soft credit limit functions in conjunction with the hard credit limit that is an innate characteristic of the underlying account. More specifically, the soft credit limit functions as a veneer over the hard credit limit to provide a granular management of the account on an interval basis, a transaction basis, or a combination of both bases. The soft credit limits can be enforced and operated at two levels, at one level the soft credit limits can be applied on a per transaction basis, and at a second level the soft credit limits can be applied on a time interval basis. For example, in one embodiment both levels can co-exist where there can be a hard limit amount, a soft limit monthly amount, and a limit per transaction. A transaction that violates any of the co-existing levels can be rejected. Accordingly, the soft credit limits may be applied in a tiered manner for control on a specified account.
It will be appreciated that, although specific embodiments of the invention have been described herein for purposes of illustration, various modifications may be made without departing from the spirit and scope of the invention. In particular, the user manager may be employed from a variety of mediums including telephone, electronic mail, electronic connection to a computer network, etc. Similarly, the underlying account may be in the form of a credit card. However, the invention should not be limited to this form of a financial account. Examples of other forms of financial accounts that may employ the soft credit limits and its associated parameters include, but are not limited to, a line of credit, a checking account, a savings account, etc. Regardless of the form of the account, the application of the soft credit limit functions as both a fraud detection tool and as a fraud prevention tool. In one embodiment, the soft credit limit may be set to zero when the holder of the subject account does not anticipate any transactions on the account. Accordingly, the scope of protection of this invention is limited only by the following claims and their equivalents.
