Check Cashing Software and Hardware: Scanners, ID and POS
Compare check cashing software feature by feature: check scanners, ID capture, verification, fee tables and compliance reporting for your counter.
On this page 7 sections
- Core Features of Check Cashing Software
- Choosing a Check Scanner for a Check Cashing Store
- ID Scanners for Money Services Counters and Photo Enrollment
- Verification Service and Maker Database Integrations
- Built-In CTR Aggregation and SAR Flagging
- How a Check Cashing POS System Handles Money Orders and Transfers
- Questions to Ask Vendors Before You Sign
Key takeaways
- Judge check cashing software first on whether it totals one customer's same-day cash activity across every window and location. Screen design matters much less.
- Ask your bank which scanners its deposit program supports before you buy one, or you may end up scanning every check twice.
- Store your state's fee caps as hard ceilings in the fee table, and log each teller override with a name and a reason.
- Get your reporting thresholds and aggregation rules from a compliance officer, then make each vendor prove on screen that its software applies them.
Check cashing software is the system of record for every check that crosses your counter. It captures the check image, ties it to a verified customer, applies your posted fees and flags the activity your anti-money-laundering program needs to track. The hardware list is short. Besides the receipt printer and cash drawer, a typical check cashing store setup puts four things at each window: a check scanner with a built-in endorser, an ID scanner, a webcam for customer photos and a card terminal for debit.
Buy the reporting and aggregation logic first. Screens come second. A clean interface is worth little if the system can't tell that the customer at window two this afternoon is the same person who cashed a check at window one this morning.
Core Features of Check Cashing Software
Every serious platform handles five jobs. Use this table as a scorecard during demos, and make the vendor show each item live instead of describing it.
| Component | What it should do | What to test in the demo |
|---|---|---|
| Customer record | Hold ID images and a photo, plus every past transaction | Look up a customer enrolled at a different location |
| Transaction record | Tie the check image to the maker and to the teller who paid it out | Pull up a cashed check and trace it back to the customer |
| Fee engine | Price each check by type, inside your state's limits | Try to override a capped fee |
| Verification layer | Query outside services and your own maker database | Run a check from a maker the system has never seen |
| Compliance layer | Aggregate cash activity and queue suspicious patterns for review | Split one customer's activity across two windows |
Vendors look alike in the first two rows. They split apart in the bottom three, so spend most of your demo time there.
Fee Tables That Enforce Your State's Limits
State rules on check cashing fees vary widely. Depending on where you're licensed, you may face fee limits by check type, a required posted schedule, specific receipt disclosures, or some mix of the three. Whatever applies to you, the software should store each cap as a hard ceiling that no teller override can exceed. It should also log every override with the teller's name and a reason.
Small coding errors become exam findings. Here is an illustrative case that doesn't reflect any state's real limits. Suppose your state caps the fee on a government benefit check at $4 less than you charge for a payroll check of the same amount. A teller who picks "payroll" from the dropdown for a benefit check overcharges that customer, and nobody notices at the window. If tellers miscode 30 benefit checks during the first-of-the-month rush, you've collected $120 above the cap in one week. Each overcharge sits in your own transaction records, where an examiner can find it.
The fix is a design choice. Software that sets the check type from the maker database, instead of trusting the teller's dropdown, prevents the error. Confirm your state's actual fee rules with your licensing regulator.
Choosing a Check Scanner for a Check Cashing Store
A counter scanner reads the MICR line, which is the magnetic-ink routing and account number printed along the bottom of the check. It also images both sides, and most counter models print your endorsement on the back. Judge each of those jobs on its own.
MICR read accuracy decides how often tellers retype numbers by hand. Every manual entry is a chance for a mistake. Image quality matters because those images are your evidence when a check comes back unpaid, and in many setups they double as your deposit file. An inkjet endorser stamps the endorsement and a transaction number automatically, which beats a rubber stamp and a pen.
Ask your bank one question before you buy. If you deposit through its remote deposit program, the bank may support only certain scanner models and image formats. Should your software accept a scanner that your bank rejects, you'll scan every check twice: once at the counter and again at closing.
Single-feed scanners suit most counters. Checks arrive one at a time, with a customer waiting. Multi-feed models earn their price in the back office of high-volume stores, where a day's checks get batched for deposit.
ID Scanners for Money Services Counters and Photo Enrollment
An ID scanner reads the barcode on the back of most U.S. driver's licenses and state IDs and fills in the customer record for the teller. Typos in names and birth dates disappear. That matters more than it sounds, because the record may later have to match a report you file. Better systems also image both sides of the card and compare the barcode data with the printed front, since a mismatch between the two is a common sign of a fake.
Your customer base sets the next requirement. If you accept passports or consular IDs, the software needs a passport capture mode and a clean manual-entry path for documents a scanner can't read. Your written ID policy should list the documents you accept. The software should enforce that list, not leave it to each teller's judgment on a busy Friday.
Photo enrollment links a face to the account the first time someone cashes a check. A webcam at each window takes the picture, and tellers see it on every later visit. Some platforms add fingerprint enrollment. Some states have laws on collecting and keeping biometric data such as fingerprints, so check with counsel before you turn that feature on.
Verification Service and Maker Database Integrations
Verification has two halves: outside services and your own history.
Third-party check verification and guarantee services compare the account and the maker against shared data on returned items and known fraud. Ask each software vendor which services it integrates with natively. With a native integration, the answer appears on the teller's screen. Without one, tellers switch to a separate web portal while the customer waits and the line grows.
Owners tend to underrate the maker database. Every employer or issuer whose checks you cash gets its own record, holding at least the routing and account numbers and a sample image of a valid check. A useful record also carries a per-check limit and a running history of returns.
When a regular customer brings in a payroll check from a maker you've verified many times, the teller sees a green flag and moves on. Two cases should stop the transaction for a call to the maker: an unknown maker, and a known maker's check that's far larger than its history. For what that call should probe, see our guide to spotting fake payroll and altered checks.
Returned items should feed back into both records automatically. A customer with an open return gets blocked before the next check is cashed, not after. So does a maker with a recent string of returns.
Built-In CTR Aggregation and SAR Flagging
Many check cashers fall under the federal anti-money-laundering rules that FinCEN applies to money services businesses under the Bank Secrecy Act. Coverage isn't automatic. It depends on factors such as how much you cash for a single person in a day, so have a compliance officer confirm your status, your reporting thresholds and your filing deadlines. What follows is general information about what the software should do, not legal advice.
CTRs Turn on Aggregation
A currency transaction report (CTR) covers large cash transactions. For software, the hard part is aggregation. Take two specific questions to your compliance officer: which same-day transactions by one customer you have to add together, and whether cash paid out and cash taken in are totaled separately or combined. Then hold every vendor to those answers.
One scenario exposes weak systems fast. A customer cashes a payroll check at window one in the morning. Late in the afternoon, the same person brings a second check to window two, where a different teller is working. Each check sits comfortably below any reporting line. The day's total may not. Software that judges one transaction at a time never notices.
Make vendors show aggregation across windows and across your locations. Cash in and cash out should run as separate totals that the system can keep apart or combine, whichever your compliance officer directs.
Money Order Purchase Records
Selling money orders may bring a separate recordkeeping duty for certain cash purchases. Owners sometimes assume the same log covers check cashing, and that assumption is worth testing before you configure anything. Ask your compliance officer what the log covers, what triggers an entry and which buyer details it needs. The software should capture those details at the point of sale and refuse to complete the sale until they're entered.
SAR Flags Need a Human Decision
Software helps with suspicious activity reports (SARs), up to a point. A good system watches for patterns such as repeated transactions just under a threshold, or one maker's checks turning up with many unrelated payees, and sends those cases to a review queue. A trained person decides whether to file. The system records that decision and the reasoning behind it.
Confidentiality rules limit what you can tell customers about SARs, and counsel can give you the specifics. The operational rule is simpler: flags never appear on receipts or on any screen a customer can see.
If you also send money abroad, sanctions screening belongs in the same workflow. Our article on OFAC screening at the remittance counter covers how holds and logs should work.
How a Check Cashing POS System Handles Money Orders and Transfers
Most check cashing stores are multi-service counters, and the large transfer and money order providers usually require their own terminals or software. A check cashing POS system rarely replaces those platforms. It records transactions alongside them.
What you want is one customer record showing every transaction from every provider. Some platforms import data from provider systems. Others rely on the teller to log each transaction by hand, which works only if the drawer can't balance until the entry is made. If you're still choosing a transfer provider, compare terms in Western Union vs. MoneyGram vs. Ria agent commissions. For utility payments, our guide to becoming a bill payment agent explains settlement timing and who carries the liability.
Card acceptance is the last piece. Many counters take debit for bill payments and service fees. Some check cashing platforms integrate with a card terminal, so the amount passes to the terminal automatically and nobody keys it twice. With others, you run a standalone terminal and reconcile card sales against the drawer at closing. Either approach works, provided the card transactions are coded correctly for what you actually sell. Processors underwrite money services closely, and how MCC 4829 and 6051 shape fees and risk explains why that coding matters. MannyPay offers high-risk merchant accounts and POS systems and card terminals for businesses that processors review more closely.
Questions to Ask Vendors Before You Sign
Bring this list to every demo, and ask the vendor to show each answer on screen.
- Show me aggregation for one customer across two windows and two locations on the same business day.
- Which check scanners and ID scanners do you support, and has my bank approved those scanners for remote deposit?
- Can fee caps be set as hard limits by check type, and where are teller overrides logged?
- Which check verification services do you integrate with, and what does the teller see when a check fails?
- How do returned items update the customer and maker records?
- How do transactions from outside money order and transfer providers get into the customer record?
- Can SAR review notes and decisions be exported for an examiner without exposing them to customers?
- Where are check and ID images stored, and how long do you keep them?
- If I cancel, in what format can I export my data?
- Does the software work with my card terminal, or will I reconcile card sales separately?
Weight the aggregation demo and the SAR export most heavily. Examiners test those answers, and they're expensive to fix once you've signed a multi-year contract.
If you're setting up card acceptance alongside your check cashing counter, request a free quote. A MannyPay specialist responds within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


