Title: | -={ H A C K E R S }=- |
Notice: | Write locked - see NOTED::HACKERS |
Moderator: | DIEHRD::MORRIS |
Created: | Thu Feb 20 1986 |
Last Modified: | Mon Aug 03 1992 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 680 |
Total number of notes: | 5456 |
I have a customer who wants to write an application to print checks. The problem is that he wants to know if the check was actually printed or not. That is, the checks are numbered and the application actually successfully completed printing, and that the printer actually printed the check. Anybody got any ideas. Thanks, Rob
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
461.1 | Simple matter of programming | MAY20::MINOW | I need a vacation | Tue May 05 1987 13:29 | 12 |
Have the customer print an OCR readable status code (including a one-way hashed encryption of the check number and amount). Then, as a separate processing step, have the output checks read by a verification program. This should be reasonably safe against loss and casual thievery. (A clever thief with access to a computer and OCR printer could still create fake checks that would pass the verification step.) Many years ago, one of our customers attached a micro-switch to a teletype to check for paper jamming. This is probably not a suitable solution for your customer, however. Martin. |