This application relates generally to financial service systems. More particularly, the present invention relates to a method for depositing negotiable instruments.
Negotiable instrument (NI) cashers, such as check cashers, are typically plagued by a bad reputation in the banking world. Because an NI casher's clientele is diverse and frequently changes, banks are often unwilling to do business with him. Banks are also reluctant to accept deposits from an NI casher because the sources of his deposits are uncertain, leaving a bank vulnerable to loss from various types of fraud, such as money laundering, NI forgery, fake check scams, etc. Therefore, NI cashers typically have difficulty finding a bank that will accept their deposits, because banks are reluctant to do business with them due to the nature of their business. In addition, NI cashers are continually looking for faster and more efficient ways to practice their business. In the case of a check casher, the process of depositing checks cashed is particularly time consuming because check cashers must physically deliver the checks to their bank. This process forces the check casher to leave his business either to deposit cashed checks at the bank before it closes or to entrust a clerk to do so. Often, the check casher or a clerk might need to leave the business during the middle of the day in order to meet bank deposit deadlines. What is needed are more efficient and more secure methods of depositing NIs.
The present invention addresses the aforementioned needs by providing a system and method enabling NI cashers to electronically deposit the NIs they cash.
In order to describe the manner in which the above-recited and other advantages and features of the invention can be obtained, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments thereof that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Additional features and advantages of the invention will be set forth in the description that follows, and in part will become more fully apparent from the following description and appended claims, or may be learned by practice of the invention as set forth herein.
The following description often illustrates the invention in terms of checks and check cashers; however, the invention may be implemented for handling all types of negotiable NIs. In regards to the present application, a user is an individual or entity presenting an NI for cashing and an NI operator (also referred to as a check cashing operator) refers to an NI casher and/or his employees that provide and/or facilitate a business for cashing NIs.
Two challenges NI operators face in running their businesses include finding a bank that will accept the regular depositing of multiple third-party NIs and delivering these third party NIs to the bank for deposit. NI operators typically encounter difficulty finding a bank that will accept their deposits because banks are reluctant to do business with them due to the nature of their business. Government regulations, such as “Know Your Customer,” require banks to determine a bank customer's sources of funds for transactions involving the bank, and they emphasize the security risks of receiving deposits from NI operators. The depository bank typically has no knowledge of the persons presenting the NIs that an NI operator submits for deposit into his banking account. However, the present system allows banks to comply with such regulations when doing business with NI operators by either verifying identity of the NI presenter, associating NI presenter personal information with an NI presented for deposit or certifying that the NI presenter's identity has been verified by a trusted entity.
If an NI operator is able to establish a relationship with a bank, an additional hurdle is the time-consuming process of physically depositing the NIs cashed. Because NI cashing businesses are typically small entities, an NI operator might have to close his business early in order to deposit the NIs he has cashed that day. Additionally, if the NI operator wants to ensure same day deposit of funds, he must meet bank deposit deadlines. For example, some banks will deposit an NI value on the day it is received only if the NI is delivered to the bank before 2:00 P.M. that day.
Regardless of when these NIs are delivered for deposit, the NI operator must either deliver them personally or entrust a clerk to do so. If an NI operator elects to have a clerk deliver the NIs, he runs the risk of the clerk accidentally or fraudulently losing NIs from those to be deposited.
In accordance with the principles of the present invention, NI operators can electronically deposit the NIs they cash into their bank accounts. This form of NI deposit minimizes the above problems by identifying the NI presenter and allowing NI operators to deposit NIs into their depository bank via electronic transmission of NI information rather than the NI operator having to transport the NIs to the bank physically. With the benefit of electronic deposit, the present invention also provides NI operators with other deposit conveniences, such as automating the deposit process, setting auto-deposit schedules, increasing risk management reliability via automatic NI logging features, and the like.
The current system and method for electronically depositing NIs allows NI operators to save time and add security to their current methods of deposit by minimizing the component of deposit via physical NI delivery and associating biometrics with their procedures. This electronic method of NI deposit might also prove beneficial to banks desiring to increase business, because it allows them to minimize their size and/or geographic limitations. For example, a small chain of banks local to Fairfax, Va. might be willing to take the risk of doing business with a NI operator in order to increase business nationwide. Via the electronic method of deposit, the present system and method may potentially link these banks in need of business with NI operators in need of a depository bank.
The current system and method for electronically depositing NIs also allows NI operators to conduct more secure NI cashing transactions by validating NIs for deposit and/or NI presenters via biometric authorization. Such features afford banks doing business with NI operators an added level of security. Methods of validating NIs and/or NI presenters with biometric data include those illustrated in co-pending application Ser. No. 10/142,687, filed May 10, 2002, which is hereby incorporated by reference in its entirety. In such a method, NI presenters enroll in a verification system, wherein their personal information typically taken in cashing an NI is stored in association with their biometric data and any other information an NI operator might request. This system might be utilized by the current invention in various manners. For example, upon deposit the system might provide the depository bank with certification that it has successfully verified the identity of each NI presenter of the NIs presented for deposit. Alternatively, the system might certify each NI separately by marking it in some manner or marking each NI, physically or electronically, with its NI presenter's biometric and/or personal data. Although it might be less secure, the invention might implement a non-biometric certification procedure, in which an NI is certified via a non-biometric identification of the NI presenter or the NI operator collects NI presenter information that is included with the deposit and/or stored for later retrieval if necessary.
In general, a biometric authorization refers to an authorization in which an individual provides biometric data to be matched against a biometric record in a database. As would be appreciated, the location of the database as well as the specific mechanism by which the biometric data is matched to a particular biometric record would be implementation dependent and would not be limiting on the scope of the present invention. Thus, in a biometric authorization, the biometric data taken during the authorization can be matched against registered biometric data at a location where the registered biometric data is stored or where the authorization biometric data is gathered. In addition, biometric data received during an authorization may be tested for liveness to prevent system fraud.
Additionally, it is envisioned that the system would not be limited to using one form of biometric. For example, the biometric data referred to throughout this description can represent a biometric image (or sample) and/or a mathematical representation of the biometric image, often referred to as a biometric “template”. In one example, a biometric template can represent any data format that includes feature, positional, or other representing information of characteristics of biometric data. Alternatively, a template may be a mathematical representation of more than one biometric. For example, an individual's template may be generated from biometric data acquired from two individual fingers, such as a thumb and index finger, or from a finger and an iris scan. The biometric data may include a fingerprint scan, an iris scan, a facial scan, a voice scan, a retinal scan, hand architecture, a DNA sample, or any other physical measurement pertaining to an individual's person.
The system also enables an NI operator to validate NIs presented for deposit by registering his personal information, a personal code and/or biometric data with the system. Depending on the embodiment of the system, an NI operator might validate a single NI or batch of NIs by presenting registered information. In the most secure example, the NI operator presents biometric data for NI validation; however, the system might alternately be configured to accept an NI operator's personal code or simply select a “validate” button or menu selection on a system device. The system might also be configured to validate automatically based upon an NI operator being “logged in” to the system. For example, an NI operator might first need to enter identifying information into a system device before he may operate it. This logging in process might effectively track and/or validate all transactions which occur while the particular NI operator is logged in to the system device. Again, such a function might be additionally protected by requesting the NI operator present a personal code and/or biometric data periodically or upon specific action requests.
At step 204, the NI presenter is verified. An NI presenter may be verified in various ways. For example, if the system incorporates the services of a biometric authorization system, then the NI presenter enters his biometric data, which is used to verify the identification of the NI presenter and/or certify his trustworthiness. Alternately, this system might also request NI presenter biometric data in an effort to locate additional NI presenter data stored in the system database and associate that data with the presented NI. For example, the NI presenter data might identify one of the NI presenter's identification numbers and that number might be printed on the presented NI or electronically associated with the electronic NI file for deposit.
At step 206, NI data is stored in database 104. In an additional embodiment, other information might be stored with the NI data. For example, if the NI operator is using a biometrically authorized NI cashing transaction system, the NI presenter's biometric data and/or other NI presenter identifying information might also be stored in association with the NI data. This particular system configuration might also allow NDB 106 to later obtain additional information about the NI presenter from the biometric authorization entity should it encounter a problem in processing a particular NI.
At step 208, NI data is transmitted to NDB 106 for deposit. Additional information might be transmitted along with the NI. For example, the NI data might be accompanied by an electronic deposit slip, an electronic packet of NI presenter information, NI certifications originated from the biometric authorization entity and the like. NIs accompanied by NI presenter information especially benefit NDB 106 by allowing the institution to comply with government regulations such as the “Know Your Customer” policies in the “Patriot Act” and by reducing the risk associated with doing business with the NI operator.
Depending on the system embodiment, step 208 may occur automatically or may be prompted by the action of an NI operator. In one embodiment of the system, an NI operator prompts deposit of received NIs by providing biometric data. Once the NI operator is biometrically authorized, he may initiate the deposit. This biometric authorization might be associated with deposit data as record of the NI operator performing the deposit. Such methods would allow NI operators to track depositing activity and would be especially useful in instances where more than one NI operator initiates deposits at one or more NI cashing locations.
While NI data transmission may occur immediately upon imaging, in an additional embodiment NI data might be stored in database 104 for a pre-set period before deposit. For example, an NI operator might wish to store the NI data of multiple NI cashing transactions before submitting a batch deposit to NDB 106. In such an embodiment, pre-set deposit instructions might instruct transmission of batched NI information to NDB 106 before the NI operator's bank deposit deadline every day. In an additional embodiment, NI data stored at database 104 might be reviewed for determination of when and how to deposit the NI. For example, an NI operator may have instructed database 104 to collect a batch of NIs to be processed by his bank's deposit deadline each day; however, he might also want to set a parameter that will immediately deposit any NI received that is worth one thousand dollars or more. Other examples of parameters an NI operator might set include batch value parameters, in which the value amount of a deposit batch is tracked, and the batch is automatically deposited once it reaches a pre-set amount. An additional example of parameters an NI operator might set is allowing an NI operator that has more than one bank account to divide his deposits into his one or more accounts. For example, an NI operator might want his first five thousand dollars of deposits to go to one bank but want the rest of his deposits for the day going to another bank. To further illustrate the control the system provides NI operators over their deposits, if the NI operator is accepting NIs on the East Coast and he has multiple banks, including one in the East and one on the West Coast, the NI operator may set parameters that specify all large NIs accepted after 2:00 P.M. on the East Coast be deposited into the bank on the West coast, so that they are deposited before the West Coast Bank's deposit deadline.
In instances where retrieving funds from NDB 106 is inconvenient for an NI operator, he may wish to employ the services of DB 110 because its location might be more convenient for him. The NI operator might be able to more easily form a banking relationship with DB 110 because DB 110 would not function as the NI operator's depository bank and therefore would not assume the same risks as NDB 106 in doing business with the NI operator. The NI operator may wish to employ the services of DB 110 for the purpose of receiving fund transfers from his NDB 106 account. The system might enable the NI operator to set parameters that automatically implement funds transfers from NDB 106 to DB 110 and/or may allow him to submit funds transfer requests. In another embodiment, the NI operator may wish to implement a cash delivery service so that the cash from the NI operator's deposit is delivered directly to him. This feature might also be one that he may automatically implement through the system. Depending on the NI operator's preferences, he might wish to utilize the services of both DB 110 and a cash delivery service.
Whether it is maintained by an NI operator or an NI cashing service, database 104 may keep a log of NIs cashed and a log of deposits. This feature would allow an NI operator to run log reports on NI cashing and/or NI depositing activity. In an alternate embodiment, this feature might also enable risk management reporting, such as alerting NI operators if their NI cashing statistics and/or deposit amounts are outside of a range predicted by their previous NI cashing and/or deposit history. For example, if an NI operator typically deposits thirty thousand dollars every Friday but then deposits only ten thousand dollars one Friday, the merchant might be notified of the discrepancy.
Once an NI has been electronically deposited, the NI operator might store the physical NI for a period of time (e.g. until its deposit clears, in accordance with NI processing regulations, etc.) or may dispose of the NI immediately. As an added measure of security, the system might request the NI operator disposing of NIs to present his biometric data in an effort to verify that the NIs were destroyed. In such an embodiment, the system might request the NI operator run the NIs through a scanner to identify the NIs he intends to destroy before destroying them. In yet an additionally embodiment, a NI operator might be provided with a combined imager/scanner that images an NI before it is shredded. Creating a record of NI shredding might be an important security feature of the system, assuring all parties affiliated with NI handling/depositing dispose of the NIs properly to minimize the risk of attempted duplicate deposits. Alternatively, if the NI operator subscribes to an NI cashing service that handles his electronic deposits, the service might request that he store the NIs for a specific amount of time, during which the NI cashing service might contact the NI operator in an effort to verify that he still has the NIs in his possession. The service might do this by asking the NI operator to pull a specific NI and read information from the NI. Additionally, the service might ask the NI operator to pull multiple NIs and scan them with a NI scanner and transmit that information to the service, assuring the service that the NI operator is holding the NIs as specified. The service might also request that the NI operator forward the NIs to a service storage facility, where the NIs might be stored for a period of time.
Should an NI operator subscribe to an NI cashing service, the service may additionally provide the NI operator with a depository bank locating service which would locate NDB 106 for the NI operator. Such a feature would not only aid the NI operator in locating a bank that is willing to do business with him but would also help small or geographically challenged banks to expand their business.
Generally, information transferred in the electronic deposit system is encrypted in an effort to increase system security. For example, information may be encrypted at one point and sent across a non-secure connection between points or not encrypted at a point of communication and sent to the other point of communication across a secure connection. Encryption and decryption of these messages may be monitored by services provided by a security company such as VeriSign. In one scenario, as an added level of security, information internal to a terminal and which is never transmitted may also be encrypted. This prevents retrieval of sensitive information (e.g., NI data) from a stolen terminal. In an additional embodiment, the system incorporates one or more anti-tampering methods by which to recognize authentic and non-authentic system requests.
A system and method for electronically depositing NIs has been illustrated. It will thus be appreciated by those skilled in the art that other variations of the present invention will be possible without departing from the scope of the invention disclosed.
These and other aspects of the present invention will become apparent to those skilled in the art by a review of the preceding detailed description. Although a number of salient features of the present invention have been described above, the invention is capable of other embodiments and of being practiced and carried out in various ways that would be apparent to one of ordinary skill in the art after reading the disclosed invention. Therefore, the above description should not be considered to be exclusive of these other embodiments. Also, it is to be understood that the phraseology and terminology employed herein are for the purposes of description and should not be regarded as limiting.
This application is a continuation-in-part of application Ser. No. 10/142,687, filed May 10, 2002, now U.S. Pat. No. 6,957,770. The above-identified application is incorporated by reference herein, in its entirety, for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
4109238 | Creekmore | Aug 1978 | A |
4187498 | Creekmore | Feb 1980 | A |
4580040 | Granzow et al. | Apr 1986 | A |
4617457 | Granzow et al. | Oct 1986 | A |
4672377 | Murphy et al. | Jun 1987 | A |
4975969 | Tal | Dec 1990 | A |
4993068 | Piosenka et al. | Feb 1991 | A |
4995086 | Lilley et al. | Feb 1991 | A |
5053607 | Carlson et al. | Oct 1991 | A |
5095194 | Barbanell | Mar 1992 | A |
5144680 | Kobayashi et al. | Sep 1992 | A |
5327508 | Deaton et al. | Jul 1994 | A |
5341428 | Schatz | Aug 1994 | A |
5386103 | DeBan et al. | Jan 1995 | A |
5448471 | Deaton et al. | Sep 1995 | A |
5469506 | Berson et al. | Nov 1995 | A |
5513272 | Bogosian, Jr. | Apr 1996 | A |
5581630 | Bonneau, Jr. | Dec 1996 | A |
5592377 | Lipkin | Jan 1997 | A |
5592560 | Deaton et al. | Jan 1997 | A |
5613012 | Hoffman et al. | Mar 1997 | A |
5620061 | Fraser | Apr 1997 | A |
5621812 | Deaton et al. | Apr 1997 | A |
5638457 | Deaton et al. | Jun 1997 | A |
5642485 | Deaton et al. | Jun 1997 | A |
5644723 | Deaton et al. | Jul 1997 | A |
5649114 | Deaton et al. | Jul 1997 | A |
5659469 | Deaton et al. | Aug 1997 | A |
5679938 | Templeton et al. | Oct 1997 | A |
5687322 | Deaton et al. | Nov 1997 | A |
5748780 | Stolfo | May 1998 | A |
5802199 | Pare, Jr. et al. | Sep 1998 | A |
5838812 | Pare et al. | Nov 1998 | A |
5897625 | Gustin et al. | Apr 1999 | A |
5910988 | Ballard | Jun 1999 | A |
6009411 | Kepecs | Dec 1999 | A |
6012039 | Hoffman et al. | Jan 2000 | A |
6023688 | Ramachandran et al. | Feb 2000 | A |
6032137 | Ballard | Feb 2000 | A |
6036344 | Goldenberg | Mar 2000 | A |
6045039 | Stinson et al. | Apr 2000 | A |
6067524 | Byerly et al. | May 2000 | A |
6129273 | Shah | Oct 2000 | A |
6145738 | Stinson et al. | Nov 2000 | A |
6149056 | Stinson et al. | Nov 2000 | A |
6164528 | Hills et al. | Dec 2000 | A |
6202055 | Houvener et al. | Mar 2001 | B1 |
6222914 | McMullin | Apr 2001 | B1 |
6230148 | Pare, Jr. et al. | May 2001 | B1 |
6240394 | Uecker et al. | May 2001 | B1 |
6282523 | Tedesco et al. | Aug 2001 | B1 |
6283366 | Hills et al. | Sep 2001 | B1 |
6286756 | Stinson et al. | Sep 2001 | B1 |
6292786 | Deaton et al. | Sep 2001 | B1 |
6307958 | Deaton et al. | Oct 2001 | B1 |
6310966 | Dulude et al. | Oct 2001 | B1 |
6327573 | Walker et al. | Dec 2001 | B1 |
6328207 | Gregoire et al. | Dec 2001 | B1 |
6330543 | Kepecs | Dec 2001 | B1 |
6334108 | Deaton et al. | Dec 2001 | B1 |
6334109 | Kanevsky et al. | Dec 2001 | B1 |
6345491 | Moran et al. | Feb 2002 | B1 |
6351735 | Deaton et al. | Feb 2002 | B1 |
6377935 | Deaton et al. | Apr 2002 | B1 |
6389401 | Kepecs | May 2002 | B1 |
6415262 | Walker et al. | Jul 2002 | B1 |
6424949 | Deaton et al. | Jul 2002 | B1 |
6456981 | Dejaeger et al. | Sep 2002 | B1 |
6464134 | Page | Oct 2002 | B1 |
6507279 | Loof | Jan 2003 | B2 |
6516302 | Deaton et al. | Feb 2003 | B1 |
6547129 | Nichols et al. | Apr 2003 | B2 |
6578760 | Otto | Jun 2003 | B1 |
6592029 | Brikho | Jul 2003 | B2 |
6609104 | Deaton et al. | Aug 2003 | B1 |
6611811 | Deaton et al. | Aug 2003 | B1 |
6647372 | Brady et al. | Nov 2003 | B1 |
6659341 | Wang | Dec 2003 | B1 |
6669086 | Abdi et al. | Dec 2003 | B2 |
6684195 | Deaton et al. | Jan 2004 | B1 |
6694300 | Walker et al. | Feb 2004 | B1 |
6695204 | Stinson et al. | Feb 2004 | B1 |
6728397 | McNeal | Apr 2004 | B2 |
6754640 | Bozeman | Jun 2004 | B2 |
6758394 | Maskatiya et al. | Jul 2004 | B2 |
6786398 | Stinson et al. | Sep 2004 | B1 |
6808109 | Page | Oct 2004 | B2 |
6810385 | Brady et al. | Oct 2004 | B1 |
6856965 | Stinson et al. | Feb 2005 | B1 |
6882641 | Gallick et al. | Apr 2005 | B1 |
6886743 | Brikho | May 2005 | B2 |
6934277 | Werve et al. | Aug 2005 | B1 |
6957770 | Robinson | Oct 2005 | B1 |
20020062249 | Iannacci | May 2002 | A1 |
20020077890 | LaPointe et al. | Jun 2002 | A1 |
20020112177 | Voltmer et al. | Aug 2002 | A1 |
20020113122 | Brikho | Aug 2002 | A1 |
20020174009 | Myers et al. | Nov 2002 | A1 |
20030009382 | D'Arbeloff et al. | Jan 2003 | A1 |
20030015583 | Abdi et al. | Jan 2003 | A1 |
20030023555 | Rees | Jan 2003 | A1 |
20030037012 | Mersky et al. | Feb 2003 | A1 |
20030065595 | Anglum | Apr 2003 | A1 |
20030089768 | Page | May 2003 | A1 |
20030120562 | Clark et al. | Jun 2003 | A1 |
20030179290 | Frazzitta et al. | Sep 2003 | A1 |
20030195800 | Peters | Oct 2003 | A1 |
20030236704 | Antonucci | Dec 2003 | A1 |
20040026500 | Brikho | Feb 2004 | A1 |
20040054587 | Dev et al. | Mar 2004 | A1 |
20040088295 | Glazer et al. | May 2004 | A1 |
20040189472 | Acosta et al. | Sep 2004 | A1 |
20040193522 | Binet et al. | Sep 2004 | A1 |
20040234117 | Tibor | Nov 2004 | A1 |
20040243665 | Markki et al. | Dec 2004 | A1 |
20040258281 | DelGrosso et al. | Dec 2004 | A1 |
20050035193 | Gustin et al. | Feb 2005 | A1 |
20050068901 | Nurminen et al. | Mar 2005 | A1 |
20050125295 | Tidwell et al. | Jun 2005 | A1 |
20050125296 | Tidwell et al. | Jun 2005 | A1 |
20050125337 | Tidwell et al. | Jun 2005 | A1 |
20050125338 | Tidwell et al. | Jun 2005 | A1 |
20050125339 | Tidwell et al. | Jun 2005 | A1 |
20050125350 | Tidwell et al. | Jun 2005 | A1 |
20050125351 | Tidwell et al. | Jun 2005 | A1 |
20050125360 | Tidwell et al. | Jun 2005 | A1 |
20050133587 | Michelassi et al. | Jun 2005 | A1 |
20050137982 | Michelassi et al. | Jun 2005 | A1 |
20050144133 | Hoffman et al. | Jun 2005 | A1 |
Number | Date | Country |
---|---|---|
0991006 | Apr 2000 | EP |
WO 0199072 | Oct 2002 | WO |
WO 03029928 | Apr 2003 | WO |
Number | Date | Country | |
---|---|---|---|
Parent | 10142687 | May 2002 | US |
Child | 11034051 | US |