Financial institutions often receive large quantities of checks related to financial transactions. Typically, these checks are processed electronically by scanning an image of the check. Due to the varied period of time that these checks are stored after the transaction has been processed, organizing, categorizing, and analyzing the checks can be difficult. There is a need for a system to process a set of information associated with a check image using one or more disposition parameters to determine an automated disposition of the check associated with the check image.
The following presents a simplified summary of one or more embodiments of the present invention, in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments of the present invention in a simplified form as a prelude to the more detailed description that is presented later.
In one aspect, a system for processing a set of information associated with a check image file using one or more disposition parameters to determine an automated disposition of the check associated with the check image file is presented. The system comprising at least one memory; at least one processor; and at least one module stored in the at least one memory and comprising instruction code that is executable by the at least one processor and configured to cause the at least one processor to: receive a set of information associated with a check image file, wherein the set of information associated with the check image file comprises information extracted from a scanned image of a check and metadata associated with the check; receive one or more disposition parameters associated with a financial institution; apply the one or more disposition parameters to the set of information associated with the check image file; and determine automated disposition of the check based on at least applying the one or more disposition parameters to the set of information associated with the check image file; and execute the automated disposition of the check, wherein executing the automated disposition further comprises physical placement of the check in a check repository associated with the financial institution.
In some embodiments, the module is configured to execute computer-readable program code further to: identify one or more issues associated with the check based on at least applying the one or more disposition parameters to the set of information associated with the check image file associated with the check; and determine automated disposition of the check based on at least the one or more identified issues associated with the check.
In some embodiments, the module is configured to execute computer-readable program code further to: determine that the automated disposition of the check comprises determining that the check has been processed successfully and can be disposed permanently.
In some embodiments, the module is configured to execute computer-readable program code further to: determine that the automated disposition of the check comprises placing the check on hold in the check repository for a predetermined period of time based on at least the one or more issues identified.
In some embodiments, the module is configured to execute computer-readable program code further to: determine that the one or more issues comprises an indication that the check is to be returned to a financial institution customer; determine that the automated disposition of the check comprises placing the check on hold to be returned to the customer based on at least the one or more issues identified.
In some embodiments, the module is configured to execute computer-readable program code further to: receive a set of information associated with one or more check image files, wherein the set of information associated with the one or more check image files comprises information extracted from a scanned image of one or more checks and metadata associated with the one or more checks; and initiate a batch processing for the one or more checks, wherein initiating further comprises aggregating the set of information associated with the one or more check image files into one or more batches.
In some embodiments, the module is configured to execute computer-readable program code further to: identify one or more issues associated with a batch of checks based on at least aggregating the set of information associated with the one or more checks; and determine and automated disposition of the batch of checks based on at least the one or more identified issues associated with the one or more checks in the batch.
In some embodiments, the module is configured to execute computer-readable program code further to: receive one or more disposition parameters, wherein the one or more disposition parameters are associated with a method of processing of the check, wherein the method of processing of the check further comprises an automated check processing and a manual check processing.
In another aspect, a computerized method for processing a set of information associated with a check image using one or more disposition parameters to determine an automated disposition of the check associated with the check image is presented. The method comprises receiving a set of information associated with a check image, wherein the set of information associated with the check image comprises information extracted from a scanned image of a check and metadata associated with the check; receiving one or more disposition parameters associated with a financial institution; applying the one or more disposition parameters to the set of information associated with the check image; and determining automated disposition of the check based on at least applying the one or more disposition parameters to the set of information associated with the check image; and executing the automated disposition of the check, wherein executing the automated disposition further comprises physical placement of the check in a check repository associated with the financial institution.
In another aspect, a computer program product for processing a set of information associated with a check image using one or more disposition parameters to determine an automated disposition of the check associated with the check image is presented. The computer program product comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising computer readable code configured to receive a set of information associated with a check image, wherein the set of information associated with the check image comprises information extracted from a scanned image of a check and metadata associated with the check; computer readable code configured to receive one or more disposition parameters associated with a financial institution; computer readable code configured to apply the one or more disposition parameters to the set of information associated with the check image; and computer readable code configured to determine automated disposition of the check based on at least applying the one or more disposition parameters to the set of information associated with the check image; and computer readable code configured to execute the automated disposition of the check, wherein executing the automated disposition further comprises physical placement of the check in a check repository associated with the financial institution
Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, where:
Embodiments of the invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more embodiments. It may be evident; however, that such embodiment(s) may be practiced without these specific details. Like numbers refer to like elements throughout.
In some embodiments, an “entity” as used herein may be a financial institution. A “facility” may be physical premises associated with the entity. For the purposes of this invention, a “financial institution” may be defined as any organization, entity, or the like in the business of moving, investing, or lending money, dealing in financial instruments, or providing financial services. This may include commercial banks, thrifts, federal and state savings banks, savings and loan associations, credit unions, investment companies, insurance companies and the like. In some embodiments, the entity may allow a user to establish an account with the entity. An “account” may be the relationship that the user has with the entity. Examples of accounts include a deposit account, such as a transactional account (e.g., a banking account), a savings account, an investment account, a money market account, a time deposit, a demand deposit, a pre-paid account, a credit account, a non-monetary user profile that includes only personal information associated with the user, etc. The account is associated with and/or maintained by the entity. In other embodiments, an “entity” may not be a financial institution. In other embodiments, an entity may or may not allow the user to establish an account associated with the entity.
In some embodiments, the “user” may be a customer (e.g., an account holder or a person who has an account (e.g., banking account, credit account, etc.) at the entity) or potential customer (e.g., a person who has submitted an application for an account, a person who is the target of marketing materials that are distributed by the entity, a person who applies for a loan that not yet been funded). In some embodiments, an “employee” may be a financial institution employee (e.g., an underwriter, a project manager, an IT specialist, a manager, an administrator, an internal operations analyst, bank teller, or the like).
As shown in
The check repository 120 may refer to a document management system for managing the checks and/or any other financial institution documents from a time they are received for storage to their eventual disposal. This includes identifying, classifying, storing, securing, retrieving, tracking, and destroying or permanently preserving checks. The purpose of the check repository 120 is part of an entity's broader function of governance, risk, and compliance and is primarily concerned with managing the evidence of an entity's activities associated with the check as well as the reduction or mitigation of misappropriation associated with the check. Typically, the system described herein is configured to process the checks received from a user via the user input system 140 and after the processing of the check, transmit control signals via the network 110 to execute actions that enable the physical paper check to be placed within the check repository 120 for either additional processing or secure disposal.
The user input system 140 may include any computerized apparatus that can be configured to perform any one or more of the functions of the user input system 140 described and/or contemplated herein. For example, the user may use the user input system 140 to transmit and/or receive information or commands to and from the system 130. In this regard, the system 130 may be configured to establish a communication link with the user input system 140, whereby the communication link establishes a data channel (wired or wireless) to facilitate the transfer of data between the user input system 140 and the system 130. In doing so, the system 130 may be configured to access one or more aspects of the user input system 140, such as, a transaction device, GPS device, an image capturing component (e.g., camera), a microphone, a speaker, or the like. In some embodiments, for example, the user input system 140 may include a personal computer system (e.g. a non-mobile or non-portable computing system, or the like), a mobile computing device, a personal digital assistant, a mobile phone, a tablet computing device, a network device, a transaction terminal, and/or the like. As illustrated in
Each communication interface described herein, including the communication interface 142, generally includes hardware, and, in some instances, software, that enables the user input system 140, to transport, send, receive, and/or otherwise communicate information to and/or from the communication interface of one or more other systems on the network 110. For example, the communication interface 142 of the user input system 140 may include a wireless transceiver, modem, server, electrical connection, and/or other electronic device that operatively connects the user input system 140 to another system such as the system 130. The wireless transceiver may include a radio circuit to enable wireless transmission and reception of information. Additionally, the user input system 140 may include a positioning system. The positioning system (e.g. a global positioning system (GPS), a network address (IP address) positioning system, a positioning system based on the nearest cell tower location, or the like) may enable at least the user input system 140 or an external server or computing device in communication with the user input system 140 to determine the location (e.g. location coordinates) of the user input system 140.
Each processor described herein, including the processor 144, generally includes circuitry for implementing the audio, visual, and/or logic functions of the user input system 140. For example, the processor may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits. Control and signal processing functions of the system in which the processor resides may be allocated between these devices according to their respective capabilities. The processor may also include functionality to operate one or more software programs based at least partially on computer-executable program code portions thereof, which may be stored, for example, in a memory device, such as in the user application 147 of the memory 146 of the user input system 140.
Each memory device described herein, including the memory 146 for storing the user application 147 and other information, may include any computer-readable medium. For example, memory may include volatile memory, such as volatile random access memory (RAM) having a cache area for the temporary storage of information. Memory may also include non-volatile memory, which may be embedded and/or may be removable. The non-volatile memory may additionally or alternatively include an EEPROM, flash memory, and/or the like. The memory may store any one or more of pieces of information and data used by the system in which it resides to implement the functions of that system. In this regard, the system may dynamically utilize the volatile memory over the non-volatile memory by storing multiple pieces of information in the volatile memory, thereby reducing the load on the system and increasing the processing speed.
As shown in
Also shown in
It will be understood that the system application 137 may be configured to implement any one or more portions of the various user interfaces and/or process flow described herein. The system application 137 may interact with the user application 147. It will also be understood that, in some embodiments, the memory includes other applications. It will also be understood that, in some embodiments, the system application 137 is configured to communicate with the structured database 138, the user input system 140, or the like.
It will be further understood that, in some embodiments, the system application 137 includes computer-executable program code portions for instructing the processor 134 to perform any one or more of the functions of the system application 137 described and/or contemplated herein. In some embodiments, the system application 137 may include and/or use one or more network and/or system communication protocols.
In addition to the system application 137, the memory 136 also includes the structured database 138. As used herein, the structured database 138 may be one or more distinct and/or remote databases. In some embodiments, the structured database 138 is not located within the system and is instead located remotely from the system. In some embodiments, the structured database 138 stores information or data described herein.
It will be understood that the structured database 138 may include any one or more storage devices, including, but not limited to, datastores, databases, and/or any of the other storage devices typically associated with a computer system. It will also be understood that the structured database 138 may store information in any known way, such as, for example, by using one or more computer codes and/or languages, alphanumeric character strings, data sets, figures, tables, charts, links, documents, and/or the like. Further, in some embodiments, the structured database 138 may include information associated with one or more applications, such as, for example, the system application 137. It will also be understood that, in some embodiments, the structured database 138 provides a substantially real-time representation of the information stored therein, so that, for example, when the processor 134 accesses the structured database 138, the information stored therein is current or substantially current.
It will be understood that the embodiment of the system environment illustrated in
In addition, the various portions of the system environment 100 may be maintained for and/or by the same or separate parties. It will also be understood that the system 130 may include and/or implement any embodiment of the present invention described and/or contemplated herein. For example, in some embodiments, the system 130 is configured to implement any one or more of the embodiments of the process flows described and/or contemplated herein in connection any process flow described herein. Additionally, the system 130 or the user input system 140 is configured to initiate presentation of any of the user interfaces described herein. In some embodiments, the one or more devices performing the steps are associated with a financial institution. In other embodiments, the one or more devices performing the steps are associated with a merchant, business, partner, third party, credit agency, account holder, and/or user.
Typically, when a user deposits a check using the user input system 140, the system may be configured to receive one or more check images. The check images comprise at least a portion of the front of the check, at least a portion of the back of the check, or any other portions of the check. In cases where there are several checks piled into a stack, the multiple check images may include, for example, at least portion of each of the four sides of the check stack. In this way, a text, numbers, or other data provided on the site of the check stack may also be used in processing the checks. All the check images are described in the process flows below, it will be understood that any type of financial record/document image or non-financial record/document image may be included in the process.
In some embodiments, each check image comprises financial record data. The financial record data includes dates of issuance of financial record, terms of the financial record, time period that the financial record is in effect, identification of parties associated with the financial record, payee information, payor information, obligations of parties to a contract, purchase amount, loan amount, consideration for a contract, representations and warranties, product return policies, product descriptions, check numbers, document identifiers, account numbers, merchant codes, file identifiers, source identifiers, and the like. In other embodiments, the check images comprise markings. The markings include, for example, text, numbers, symbols, other characters, lines, shadows, shapes, ink blots, stains, logos, paper tears, smudges, watermarks, any visible marking on the paper check, any visible marking applied electronically to the check image, or any pixel/texel quantity thereof.
Although check images are illustrated in process flow below, it will be understood that any type of image (e.g., PDF files, scanned documents, digital photographs with or without letters, numbers, and the like) or financial record may be received in accordance with the embodiments of the invention. At least a portion of each of the check images, in some embodiments, is received from a financial institution, a merchant, a signatory of the financial record (e.g., the entity having authority to endorse or issue a financial record), and/or a party to a financial record. In other embodiments, the check images are received from image owners, account holders, joint account holder, agents of account holders, family members of account holders, financial institution customers, payors, payees, third parties, and the like. In some embodiments, the source of at least one of the checks includes an authorized source such as an account holder or a third party financial institution. In other embodiments, the source of at least one of the checks includes an unauthorized source such as an entity that intentionally or unintentionally deposits or provides a check image to the system.
The check image may then be processed using optical character recognition (OCR) processes that enable the system to convert handwritten or printed text and other symbols in the check image to machine encoded text such as text based files that can be edited and searched. The set of information in the check images is then extracted from the scanned image of the check which can then be used and incorporated into a variety of applications, documents, and processes. In some embodiments, the set of information includes but is not limited to, a payee, a payor, a date, a memo line data, a payment amount, a check number, and endorsement, a signature, and/or the like.
However, the accuracy of the process depends on the quality of the check image, the quality of the identified check data extracted from the check image, whether or not the check data can be verified, and/or the like. If the check image includes blurred text or has a low pixel count, the text produced by OCR may not be accurate. In some embodiments, the source of the check image may be responsible for the quality of the check image itself. In this regard, the transaction terminals capable of accepting the checks and processing the checks to retrieve the check image may be malfunctioning, causing a particular group/batch of checks to be misrepresenting the check information. In some cases, the quality of the physical check may be questionable prior to being deposited at a facility or a transaction terminal. This may cause the check image to be representative of the quality of the physical check, thereby creating questionable check data. In one exemplary situation, the system may determine that handwritten portions of a check image should not undergo OCR processing due to the difficulty in identifying such handwritten portions. Exemplary unrecognized data includes handwritten text, blurred text, faded text, misspelled data, any data not recognized by the OCR processes or other data recognition techniques, and the like.
Typically, the checks are processed based on a confidence level associated with the check data. This includes transmitting the check data to a clearinghouse that sorts checks to send them to financial institutions against which the checks are drawn. Once the check data is verified and the funds transfer confirmed, the checks are cleared. The financial institution may then hold the original check anywhere from a few weeks to a few months based on one or more disposition parameters before disposing the check. However, in some instances a check may be inappropriately processed as every confidence level is associated with an error margin. Some of these cases may not develop until after the physical check is disposed. In such a situation, the financial institution may only be left with the check image used in the processing of the check and not the physical check itself. To avoid such a situation, financial institutions store every check that is processed. In doing so, the financial institutions are currently faced with the problem of a space crunch due to the increased volume of checks aggregated over the years. The present invention provides the functional benefit of determining an automated means for disposition of checks based on processing a set of information associated with a check image using one or more disposition parameters.
In some embodiments, the set of information further includes whether the check image was associated with an error. In this regard, the system may be configured to determine whether the check image used to process the check had image quality issues is required personnel intervention for clarification and additional processing. This includes accounting for overall clearing expenses, research and repair process, transportation costs, write-offs, and in some cases, paper settlement process.
Next, as shown in block 204, the process flow includes receiving one or more disposition parameters associated with a financial institution. Typically, the disposition parameters may be one or more internal, external, and/or regulatory parameters used to analyze the set of information associated with the check image. The disposition parameters may reflect one or more conditions and/or standards that the check is expected to adhere to from a time the check is deposited by the customer until a time the check is processed and funds transferred.
In response to receiving one or more disposition parameters, the process flow includes applying the one or more disposition parameters to the set of information associated with the check file, as shown in block 206. In this regard, the system may be configured to identify one or more issues associated with the check based on at least applying the one or more disposition parameters and determining automated disposition of the check based on at least the one or more identified issues. Typically, the one or more issues may be determined based on at least determining whether the set of information associated with the check meets the one or more disposition parameters. If the set of information associated with the check meets the one or more disposition parameters, then the check is said to have seamlessly processed. If the set of information associated with the check does not meet even one of the one or more disposition parameters, then the check set to have not seamlessly processed.
Next, as shown in block 208, the process flow includes determining automated disposition of the check based on at least applying the one or more disposition parameters to the set of information associated with the check image. In some embodiments, the system may be configured to determine that the automated disposition of the check includes determining that the check has been process successfully and that the check can be disposed of permanently. In this regard, the system may determine that the check has been processed seamlessly and does not indicate any issues. In another embodiment, the system may be configured to determine that the automated disposition of the check includes placing the check on hold in the check repository for a predetermined period of time based on at least the one or more issues identified. In this regard, the system may determine that the processing of the check required an additional manual processing and that the check was not processed seamlessly. For example, if a checking account associated with the payer was identified to have insufficient funds or a stop-payment order has been placed, the process is flagged and the information is transmitted back to the financial institution where the check was deposited. In this situation, the financial institution may require an employee to further verify this information during the processing of the check. In yet another embodiment, the system may be configured to determine that the one or more issues include an indication that the check is to be returned to a financial institution customer. In response, the automated disposition of the check may include placing the check on hold to be returned to the customer.
Next, as shown in block 210, the process flow includes executing the automated disposition of the check. In this regard, the system may be configured to transmit control signals configured to cause a proprietary mechanical apparatus associated with the financial institution to physically place the check in a check repository associated with the financial institution. In some embodiments, the system may be configured to transmit control signals to cause the mechanical apparatus associated with the financial institution to place the check into one or more categories within the check repository. In one aspect, the one or more categories may be based on one or more post-processing actions to be executed on the check.
In some embodiments, the system may be configured to receive a set of information associated with the one or more check images, wherein the set of information associated with the one or more check images includes information extracted from a scanned image of one or more checks and metadata associated with the one or more checks. In this case, the system may then initiate a batch processing for the one or more checks, wherein initiating further comprises aggregating the set of information associated with the one or more check images into one or more batches. In this case, if an issue is identified, the system may be configured to determine whether the issue is associated with a specific check or whether the issue is associated with the batch of checks. In this regard, the system may be configured to identify one or more issues associated with a batch of checks based on at least aggregating the set of information associated with the one or more checks. In response, the system may then determine an automated disposition of the batch of checks based on at least the one or more identified issues associated with the one or more checks in the batch.
Although many embodiments of the present invention have just been described above, the present invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Also, it will be understood that, where possible, any of the advantages, features, functions, devices, and/or operational aspects of any of the embodiments of the present invention described and/or contemplated herein may be included in any of the other embodiments of the present invention described and/or contemplated herein, and/or vice versa. In addition, where possible, any terms expressed in the singular form herein are meant to also include the plural form and/or vice versa, unless explicitly stated otherwise. Accordingly, the terms “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Like numbers refer to like elements throughout.
As will be appreciated by one of ordinary skill in the art in view of this disclosure, the present invention may include and/or be embodied as an apparatus (including, for example, a system, machine, device, computer program product, and/or the like), as a method (including, for example, a business method, computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely business method embodiment, an entirely software embodiment (including firmware, resident software, micro-code, stored procedures in a database, or the like), an entirely hardware embodiment, or an embodiment combining business method, software, and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having one or more computer-executable program code portions stored therein. As used herein, a processor, which may include one or more processors, may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or by having one or more application-specific circuits perform the function.
It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, electromagnetic, infrared, and/or semiconductor system, device, and/or other apparatus. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as, for example, a propagation signal including computer-executable program code portions embodied therein.
One or more computer-executable program code portions for carrying out operations of the present invention may include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#.
Some embodiments of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of apparatus and/or methods. It will be understood that each block included in the flowchart illustrations and/or block diagrams, and/or combinations of blocks included in the flowchart illustrations and/or block diagrams, may be implemented by one or more computer-executable program code portions. These one or more computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s).
The one or more computer-executable program code portions may be stored in a transitory and/or non-transitory computer-readable medium (e.g. a memory) that can direct, instruct, and/or cause a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).
The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with, and/or replaced with, operator- and/or human-implemented steps in order to carry out an embodiment of the present invention.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations, modifications, and combinations of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.
Number | Name | Date | Kind |
---|---|---|---|
3555349 | Munz | Jan 1971 | A |
3555988 | Wagner | Jan 1971 | A |
3556050 | Trachtenberg et al. | Jan 1971 | A |
3558810 | Cecchin | Jan 1971 | A |
3560739 | Wolff | Feb 1971 | A |
3561432 | Yamaki et al. | Feb 1971 | A |
3564133 | Hobrough | Feb 1971 | A |
3564266 | Klotz, Jr. | Feb 1971 | A |
3566139 | Hardy et al. | Feb 1971 | A |
3567856 | Nezu | Mar 1971 | A |
3571527 | Becker et al. | Mar 1971 | A |
3572924 | Matsumoto et al. | Mar 1971 | A |
3576392 | Hofstein | Apr 1971 | A |
3576999 | Blythe et al. | May 1971 | A |
3578857 | Busch | May 1971 | A |
3584148 | Flory | Jun 1971 | A |
3584931 | Doring | Jun 1971 | A |
3585283 | Graser, Jr. | Jun 1971 | A |
3586765 | Jirka | Jun 1971 | A |
3592535 | Gerry | Jul 1971 | A |
3592548 | Majkowski | Jul 1971 | A |
3614309 | Presti | Oct 1971 | A |
3614764 | Kolb et al. | Oct 1971 | A |
3615540 | Land et al. | Oct 1971 | A |
3619052 | Diachuk et al. | Nov 1971 | A |
3619060 | Johnson | Nov 1971 | A |
3620729 | Somerset et al. | Nov 1971 | A |
3622224 | Wysocki et al. | Nov 1971 | A |
3627918 | Redpath | Dec 1971 | A |
3630623 | Schirmer | Dec 1971 | A |
3632181 | Lee | Jan 1972 | A |
3635139 | Guite, Sr. | Jan 1972 | A |
3636845 | Harvey | Jan 1972 | A |
3643017 | Pekau | Feb 1972 | A |
3643019 | Beltz | Feb 1972 | A |
3646256 | Jacob et al. | Feb 1972 | A |
3647289 | Weber | Mar 1972 | A |
3647290 | Egnaczak et al. | Mar 1972 | A |
3647441 | Bachelder | Mar 1972 | A |
3648388 | Lowell et al. | Mar 1972 | A |
3648584 | Eacock | Mar 1972 | A |
3652164 | Faramarzpour et al. | Mar 1972 | A |
3654707 | Roberts | Apr 1972 | A |
3656427 | Foley | Apr 1972 | A |
3659159 | Nagata | Apr 1972 | A |
3661457 | Frech | May 1972 | A |
3661577 | Klemm et al. | May 1972 | A |
3737628 | Azure, Jr. | Jun 1973 | A |
3778595 | Hatanaka et al. | Dec 1973 | A |
4417136 | Rushby et al. | Nov 1983 | A |
4523330 | Cain | Jun 1985 | A |
4555617 | Brooks et al. | Nov 1985 | A |
5007100 | D'Aoust et al. | Apr 1991 | A |
5182656 | Chevion et al. | Jan 1993 | A |
5257328 | Shimizu | Oct 1993 | A |
5359667 | Borowski et al. | Oct 1994 | A |
5453601 | Rosen | Sep 1995 | A |
5600574 | Reitan | Feb 1997 | A |
5631984 | Graf et al. | May 1997 | A |
5678046 | Cahill et al. | Oct 1997 | A |
5679940 | Templeton et al. | Oct 1997 | A |
5687250 | Curley et al. | Nov 1997 | A |
5740271 | Kunkler et al. | Apr 1998 | A |
5754673 | Brooks et al. | May 1998 | A |
5774249 | Shiraishi et al. | Jun 1998 | A |
5848400 | Chang | Dec 1998 | A |
5917965 | Cahill et al. | Jun 1999 | A |
5940844 | Cahill et al. | Aug 1999 | A |
5963659 | Cahill et al. | Oct 1999 | A |
6076074 | Cotton et al. | Jun 2000 | A |
6097834 | Krouse et al. | Aug 2000 | A |
6115509 | Yeskel | Sep 2000 | A |
6122625 | Rosen | Sep 2000 | A |
6181814 | Carney | Jan 2001 | B1 |
6181837 | Cahill et al. | Jan 2001 | B1 |
6351553 | Hayosh | Feb 2002 | B1 |
6574377 | Cahill et al. | Jun 2003 | B1 |
6658393 | Basch et al. | Dec 2003 | B1 |
6671795 | Marr et al. | Dec 2003 | B1 |
6697512 | Simonoff | Feb 2004 | B2 |
6775422 | Altman | Aug 2004 | B1 |
6845366 | Hassanein et al. | Jan 2005 | B1 |
6886136 | Zlotnick et al. | Apr 2005 | B1 |
6903767 | Robins et al. | Jun 2005 | B2 |
6913260 | Maier et al. | Jul 2005 | B2 |
7082216 | Jones et al. | Jul 2006 | B2 |
7092560 | Jones et al. | Aug 2006 | B2 |
7092561 | Downs, Jr. | Aug 2006 | B2 |
7103438 | Hallowell et al. | Sep 2006 | B2 |
7171032 | Jones et al. | Jan 2007 | B2 |
7181430 | Buchanan et al. | Feb 2007 | B1 |
7191151 | Nosek | Mar 2007 | B1 |
7191657 | Maier et al. | Mar 2007 | B2 |
7197173 | Jones et al. | Mar 2007 | B2 |
7201320 | Csulits et al. | Apr 2007 | B2 |
7209571 | Davis et al. | Apr 2007 | B2 |
7216106 | Buchanan et al. | May 2007 | B1 |
7232024 | Mazur et al. | Jun 2007 | B2 |
7362891 | Jones et al. | Apr 2008 | B2 |
7366338 | Jones et al. | Apr 2008 | B2 |
7376603 | Mayr et al. | May 2008 | B1 |
7386511 | Buchanan et al. | Jun 2008 | B2 |
7391897 | Jones et al. | Jun 2008 | B2 |
7436979 | Bruce et al. | Oct 2008 | B2 |
7440924 | Buchanan et al. | Oct 2008 | B2 |
7503445 | Yoshioka | Mar 2009 | B2 |
7505831 | Jones et al. | Mar 2009 | B2 |
7505931 | Da Silva | Mar 2009 | B2 |
7516360 | Bacher et al. | Apr 2009 | B2 |
7542598 | Jones et al. | Jun 2009 | B2 |
7590274 | Raterman et al. | Sep 2009 | B2 |
7591428 | Freeman et al. | Sep 2009 | B2 |
7599543 | Jones et al. | Oct 2009 | B2 |
7602956 | Jones et al. | Oct 2009 | B2 |
7619721 | Jones et al. | Nov 2009 | B2 |
7620231 | Jones et al. | Nov 2009 | B2 |
7624071 | Buchanan et al. | Nov 2009 | B2 |
7628326 | Freeman et al. | Dec 2009 | B2 |
7635082 | Jones | Dec 2009 | B2 |
7686151 | Renz et al. | Mar 2010 | B2 |
7702588 | Gilder et al. | Apr 2010 | B2 |
7729990 | Marceau et al. | Jun 2010 | B2 |
7735621 | Hallowell et al. | Jun 2010 | B2 |
7762380 | Freeman et al. | Jul 2010 | B2 |
7778456 | Jones et al. | Aug 2010 | B2 |
7779982 | Fitzgerald et al. | Aug 2010 | B2 |
7789243 | Hornung et al. | Sep 2010 | B2 |
7792753 | Slater et al. | Sep 2010 | B1 |
7797239 | Smith | Sep 2010 | B2 |
7802721 | Wilson, Jr. et al. | Sep 2010 | B2 |
7817842 | Mennie | Oct 2010 | B2 |
7822629 | Chen et al. | Oct 2010 | B2 |
7849994 | Klein et al. | Dec 2010 | B2 |
7873200 | Oakes, III et al. | Jan 2011 | B1 |
7873576 | Jones et al. | Jan 2011 | B2 |
7881519 | Jones et al. | Feb 2011 | B2 |
7882000 | Jones | Feb 2011 | B2 |
7885451 | Walls et al. | Feb 2011 | B1 |
7885880 | Prasad et al. | Feb 2011 | B1 |
7903863 | Jones et al. | Mar 2011 | B2 |
7929749 | Jones et al. | Apr 2011 | B1 |
7938245 | Jenrick et al. | May 2011 | B2 |
7946406 | Blake et al. | May 2011 | B2 |
7950656 | Adams | May 2011 | B2 |
7962411 | Prasad et al. | Jun 2011 | B1 |
7970677 | Oakes, III et al. | Jun 2011 | B1 |
7978899 | Jenrick et al. | Jul 2011 | B2 |
8025213 | Hartfield et al. | Sep 2011 | B2 |
8027928 | Hecht, Jr. et al. | Sep 2011 | B1 |
8041098 | Jones et al. | Oct 2011 | B2 |
8045784 | Price et al. | Oct 2011 | B2 |
8060442 | Hecht et al. | Nov 2011 | B1 |
8073751 | Garg et al. | Dec 2011 | B2 |
8082207 | Bates et al. | Dec 2011 | B2 |
8103084 | Jones et al. | Jan 2012 | B2 |
8125624 | Jones et al. | Feb 2012 | B2 |
8126793 | Jones | Feb 2012 | B2 |
8162125 | Csulits et al. | Apr 2012 | B1 |
8169602 | Jones et al. | May 2012 | B2 |
8204293 | Csulits et al. | Jun 2012 | B2 |
8214373 | Bakir et al. | Jul 2012 | B1 |
8214686 | Ueda | Jul 2012 | B2 |
8265346 | Blair | Sep 2012 | B2 |
8290216 | Blair | Oct 2012 | B1 |
8297428 | Renz et al. | Oct 2012 | B2 |
8301565 | Cantley et al. | Oct 2012 | B2 |
8322505 | Freeman et al. | Dec 2012 | B2 |
8331643 | Yacoubian et al. | Dec 2012 | B2 |
8339589 | Jones et al. | Dec 2012 | B2 |
8412605 | Griffin et al. | Apr 2013 | B2 |
8474704 | Grimm et al. | Jul 2013 | B1 |
8504456 | Griffin et al. | Aug 2013 | B2 |
8526751 | Mitchell et al. | Sep 2013 | B2 |
8527412 | Waldron, III et al. | Sep 2013 | B1 |
8600879 | Reyes | Dec 2013 | B2 |
8610966 | Hatzav et al. | Dec 2013 | B2 |
8639062 | Calman et al. | Jan 2014 | B2 |
8714336 | Csulits et al. | May 2014 | B2 |
8718367 | Schneider et al. | May 2014 | B1 |
8738529 | Kolhatkar et al. | May 2014 | B2 |
8799161 | Kreutz et al. | Aug 2014 | B2 |
8824785 | Ives et al. | Sep 2014 | B2 |
8864029 | McGlamery et al. | Oct 2014 | B2 |
9025851 | Smith et al. | May 2015 | B2 |
9082007 | Smith et al. | Jul 2015 | B2 |
20010034682 | Knight et al. | Oct 2001 | A1 |
20010037297 | McNair | Nov 2001 | A1 |
20010051921 | Garner, IV et al. | Dec 2001 | A1 |
20020038289 | Lawlor et al. | Mar 2002 | A1 |
20020072942 | Kuykendall et al. | Jun 2002 | A1 |
20020082994 | Herziger | Jun 2002 | A1 |
20020087409 | Joao | Jul 2002 | A1 |
20020128969 | Parmelee et al. | Sep 2002 | A1 |
20030059098 | Jones et al. | Mar 2003 | A1 |
20030066876 | Goldman et al. | Apr 2003 | A1 |
20030120586 | Litty | Jun 2003 | A1 |
20030126444 | Wakao et al. | Jul 2003 | A1 |
20030128375 | Ruhl et al. | Jul 2003 | A1 |
20030138128 | Rhoads | Jul 2003 | A1 |
20030217005 | Drummond et al. | Nov 2003 | A1 |
20040133516 | Buchanan et al. | Jul 2004 | A1 |
20040153650 | Hillmer | Aug 2004 | A1 |
20040153663 | Clark et al. | Aug 2004 | A1 |
20040218729 | Xue et al. | Nov 2004 | A1 |
20040245330 | Swift et al. | Dec 2004 | A1 |
20050034054 | Tsuyama et al. | Feb 2005 | A1 |
20050038756 | Nagel | Feb 2005 | A1 |
20050049950 | Johnson | Mar 2005 | A1 |
20050071283 | Randle | Mar 2005 | A1 |
20050080701 | Tunney et al. | Apr 2005 | A1 |
20050097019 | Jacobs | May 2005 | A1 |
20050125296 | Tidwell et al. | Jun 2005 | A1 |
20050139670 | McGlamery et al. | Jun 2005 | A1 |
20050160227 | Todd et al. | Jul 2005 | A1 |
20050213805 | Blake et al. | Sep 2005 | A1 |
20050220324 | Klein et al. | Oct 2005 | A1 |
20050244035 | Klein et al. | Nov 2005 | A1 |
20050283609 | Langford | Dec 2005 | A1 |
20060028689 | Perry et al. | Feb 2006 | A1 |
20060059201 | Watanabe | Mar 2006 | A1 |
20060080245 | Bahl et al. | Apr 2006 | A1 |
20060089905 | Song et al. | Apr 2006 | A1 |
20060106717 | Randle et al. | May 2006 | A1 |
20060116898 | Peterson | Jun 2006 | A1 |
20060117182 | Wolff | Jun 2006 | A1 |
20060156382 | Motoyama | Jul 2006 | A1 |
20060182331 | Gilson et al. | Aug 2006 | A1 |
20060212391 | Norman et al. | Sep 2006 | A1 |
20060212502 | Chatterjee | Sep 2006 | A1 |
20060247992 | Song et al. | Nov 2006 | A1 |
20060248009 | Hicks et al. | Nov 2006 | A1 |
20060282660 | Varghese et al. | Dec 2006 | A1 |
20070043650 | Hughes et al. | Feb 2007 | A1 |
20070045395 | Corona et al. | Mar 2007 | A1 |
20070100750 | Hartfield et al. | May 2007 | A1 |
20070124241 | Newton | May 2007 | A1 |
20070150412 | Lamparello et al. | Jun 2007 | A1 |
20070174214 | Welsh et al. | Jul 2007 | A1 |
20070234102 | Fan et al. | Oct 2007 | A1 |
20070288382 | Narayanan et al. | Dec 2007 | A1 |
20080016358 | Filreis et al. | Jan 2008 | A1 |
20080040249 | Re et al. | Feb 2008 | A1 |
20080059962 | Ito | Mar 2008 | A1 |
20080077474 | Dumas et al. | Mar 2008 | A1 |
20080086420 | Gilder et al. | Apr 2008 | A1 |
20080086421 | Gilder et al. | Apr 2008 | A1 |
20080103800 | Domenikos et al. | May 2008 | A1 |
20080103972 | Lanc | May 2008 | A1 |
20080116257 | Fickling | May 2008 | A1 |
20080140576 | Lewis et al. | Jun 2008 | A1 |
20080249931 | Gilder et al. | Oct 2008 | A1 |
20080256167 | Branson et al. | Oct 2008 | A1 |
20080270206 | Gillum | Oct 2008 | A1 |
20080294514 | Calman | Nov 2008 | A1 |
20080294541 | Weinflash et al. | Nov 2008 | A1 |
20080307258 | Challenger et al. | Dec 2008 | A1 |
20080319922 | Lawrence et al. | Dec 2008 | A1 |
20090008442 | Buchanan et al. | Jan 2009 | A1 |
20090018958 | Aveyard et al. | Jan 2009 | A1 |
20090094148 | Gilder et al. | Apr 2009 | A1 |
20090106846 | Dupray et al. | Apr 2009 | A1 |
20090141962 | Borgia et al. | Jun 2009 | A1 |
20090150288 | Bishop et al. | Jun 2009 | A1 |
20090196485 | Mueller et al. | Aug 2009 | A1 |
20090248560 | Recce et al. | Oct 2009 | A1 |
20090248573 | Haggerty et al. | Oct 2009 | A1 |
20090309694 | Nichols et al. | Dec 2009 | A1 |
20100030644 | Dhamodharan | Feb 2010 | A1 |
20100070415 | Buchanan et al. | Mar 2010 | A1 |
20100122216 | Song et al. | May 2010 | A1 |
20100161466 | Gilder | Jun 2010 | A1 |
20100217612 | Apacible et al. | Aug 2010 | A1 |
20100299553 | Cen | Nov 2010 | A1 |
20100306111 | Slater et al. | Dec 2010 | A1 |
20110066547 | Clark et al. | Mar 2011 | A1 |
20110099067 | Cooper et al. | Apr 2011 | A1 |
20110161346 | Solihin | Jun 2011 | A1 |
20110215034 | Mennie et al. | Sep 2011 | A1 |
20110276483 | Saegert | Nov 2011 | A1 |
20120030678 | Hayduchok et al. | Feb 2012 | A1 |
20120117423 | Andrade et al. | May 2012 | A1 |
20120189186 | Csulits et al. | Jul 2012 | A1 |
20130024360 | Ballout | Jan 2013 | A1 |
20130097464 | Ahmad et al. | Apr 2013 | A1 |
20130325698 | Shao et al. | Dec 2013 | A1 |
20130339204 | Dias De Assunca et al. | Dec 2013 | A1 |
20140058914 | Song et al. | Feb 2014 | A1 |
20140188804 | Gokhale et al. | Jul 2014 | A1 |
20140233831 | Palmer et al. | Aug 2014 | A1 |
20140233836 | Smith | Aug 2014 | A1 |
20140236791 | Palmer et al. | Aug 2014 | A1 |
20140250336 | Tepus | Sep 2014 | A1 |
20140281704 | Jacobson et al. | Sep 2014 | A1 |
20140330789 | Copes et al. | Nov 2014 | A1 |
20140358863 | Bennett et al. | Dec 2014 | A1 |
20150195190 | Shah Heydari | Jul 2015 | A1 |
20160034362 | Al-Wahabi | Feb 2016 | A1 |
20170109837 | Loganathan et al. | Apr 2017 | A1 |
20170168959 | Dodonov et al. | Jun 2017 | A1 |
Number | Date | Country |
---|---|---|
1492338 | Apr 2004 | CN |
1885341 | Dec 2006 | CN |
101059863 | Oct 2007 | CN |
115189 | Oct 1987 | EP |
671696 | Sep 1995 | EP |
1507243 | Feb 2005 | EP |
2006155439 | Jun 2006 | JP |
03040881 | May 2003 | WO |
2004036386 | Apr 2004 | WO |
2005006269 | Jan 2005 | WO |
Entry |
---|
Canadian Office Action dated Oct. 30, 2012 for Application No. 2,546,849. |
Chen, Ming-ju et al. “A Digital Watermarking of Detecting the Image Integrity Based on DWT.” Information and Electronic Engineering. vol. 6, No. 2, Apr. 2008. Chinese Language. 4 pages. |
Han, Shui-Hua et al. “Content-based image authentication: current status, issues, and challenges.” Int. J. Inf. Secur. (2010) 9:19-32. DOI 10.1007/s10207-009-0093-2. Regular Contribution. Published Online Oct. 8, 2009. 0 Springer-Verlag 2009. |
International Preliminary Report of Patentability and Written Opinion dated Jun. 5, 2012 for International Application No. PCT/US2010/058380. |
International Preliminary Report of Patentability and Written Opinion dated Jun. 5, 2012 for International Application No. PCT/US2010/058403. |
International Preliminary Report of Patentability and Written Opinion dated Jun. 5, 2012 for International Application No. PCT/US2010/058409. |
International Preliminary Report of Patentability and Written Opinion dated Jun. 5, 2012 for International Application No. PCT/US2010/058414. |
International Preliminary Report on Patentability dated Apr. 22, 2010 for International Application No. PCT/US2008/085873. |
International Preliminary Report on Patentability dated Jul. 3, 2006 for International Application No. PCT/US2004/043832. |
International Search Report and Written Opinion dated Jan. 24, 2011 for International Application No. PCT/US2010/058403. |
International Search Report and Written Opinion dated Jan. 24, 2011 for International Application No. PCT/US2010/058414. |
International Search Report and Written Opinion dated Jan. 31, 2011 for International Application No. PCT/US2010/058409. |
International Search Report and Written Opinion dated Jan. 24, 2011 for International Application No. PCT/US2010/058380. |
International Search Report dated Apr. 23, 2008 for International Application No. PCT/US2007/083198. |
International Search Report and Written Opinion dated May 19, 2005 for International Application No. PCT/US2004/043832. |
Kwak et al., “Benefits, obstacles, and future of six sigma approach”, Technovation, vol. 26, pp. 708-715, 2006. |
Labys, W. P. (2001). Essays on microstructure and the use of information in limit order markets. (Order No. 3003649, University of Pennsylvania). ProQuest Dissertations and Theses, 195-195 p. Retrieved from http://search.proquest.com/docview/251101049?accountid=14753. (251101049). |
Mitchell, Joseph Pershing, I., 11. (2000) The central bankers: Administrative legitimacy and the federal reserve system. (Order No. 3065450, Virginia Polytechnic Institute and State University). ProQuest Dissertations and Theses, 269-269 p. Retrieved from http://search.proquest.com/docview/304626254?accountid=14753. (304626254). |
Muller, J. D. (1998). Selected development in the law of cyberspace payments. The Business Lawyer, 54(1), 403-441. Retrieved from http://search.proquest.com/docview/228450582?accountid=14753. |
Patricia Murphy, It's a Time of Change for Check Processing, May 2004, USBanker, pp. 1-5. |
State Intellectual Property Office of the People's Republic of China. Chinese Office Action dated May 11, 2012. Chinese Application No. 200810177822.1. Name of Applicant: Bank of America Corporation. Chinese Language. 34 pages. |
“Money Laundering: A Banker's Guide to Avoiding Problems,” published on the internet at www.occ.treas.gov/money-laundering/pub-money-laundering-bankers guide, Dec. 2002 (Year 2002). |
Number | Date | Country | |
---|---|---|---|
20170228703 A1 | Aug 2017 | US |