A former accountant stole a roll of payroll checks after being fired. She quickly cashed a number of the checks at a chain of family-owned supermarkets. The stores used a check security system that required several forms of identification – including fingerprints – from check-cashing customers. The system worked well at uncovering counterfeit and stolen checks, but the system had a major flaw. It relied heavily on personal background checks, so if you didn’t have a criminal history it was much easier to pass checks. Though the perpetrator was eventually arrested, she did manage to take in over $100,000 before the authorities caught up with her.

Even fingerprint identification didn’t work in this case. But our software could have. It lets you set all kinds of parameters for check acceptance or denial with a plus/minus velocity. In other words, you decide how many checks a person can cash in a particular timeframe before they’re red-flagged. Because this is a positive database – as opposed to most companies’ negative databases that react only to people who have bounced checks – it can easily stop check runners. Just like this supermarket thief.

Our software is also able to access third-party databases on the parameters you set, whether it’s a certain check amount or a given number of checks cashed in a particular time period. This saves you money since you’re not paying a third party for every check that comes across your counters. And the software is completely flexible, so there’s no expense in resetting or changing your parameters.