Key takeaways
- Check cashing software has three jobs: process the transaction, keep you compliant as a money services business (MSB), and stop you cashing bad checks. Most products are strong on the first, adequate on the second and weak on the third.
- Compliance features are non-negotiable: customer identification, Currency Transaction Reports above $10,000, suspicious-activity tracking and OFAC screening.
- Verification is where the money is lost or saved. Look for image analysis, routing validation against the Fed directory, duplicate detection and ID match — not just a "bad check" blacklist.
- Verification doesn't have to come from your POS vendor; an API-based verification service can plug into whatever software you already run.
- Price the software against one month of returned checks, not against the subscription fee.
What check cashing software does
A check cashing store is a money services business: it takes in a check, charges a fee, and hands over cash before the check has been collected from the paying bank. Software built for that business has to handle three distinct things at once.
1. Run the transaction
Enroll the customer, capture their ID, scan or photograph the check, calculate the fee (often a percentage that varies by check type and state cap), print the receipt, endorse the check and update the cash drawer. Good software does this in under a minute with no retyping.
2. Keep the store compliant
Check cashers are regulated under the Bank Secrecy Act and by state licensing. The software should enforce a Customer Identification Program, automatically flag cash transactions above $10,000 for a Currency Transaction Report (CTR), aggregate same-day transactions by the same customer, support Suspicious Activity Report (SAR) documentation, screen customers against the OFAC sanctions list, and retain records for the required five years. State rules add their own fee caps and disclosure requirements.
3. Decide whether to cash the check
This is the function that protects your margin. Every check you cash is an unsecured loan to the payer until it clears. The software should help the teller decide — quickly and consistently — whether a check is genuine and whether the person presenting it is entitled to it.
Features that matter: a checklist
| Area | Must have | Nice to have |
|---|---|---|
| Customer management | ID capture and expiry tracking, photo on file, transaction history, repeat-customer lookup by phone or ID | Biometric (face or fingerprint) match on return visits, customer risk tiers |
| Check capture | Scanner or camera capture of front and back, MICR read, image stored with the transaction | Mobile capture for drive-through or remote tellers |
| Fee engine | Fee tables by check type (payroll, government, personal, insurance), state fee-cap enforcement, printed disclosures | Promotional pricing, loyalty discounts |
| Compliance | CTR triggers and aggregation, SAR notes, OFAC screening, five-year record retention, audit log | Automated FinCEN e-filing, compliance dashboard |
| Verification | Routing number validation, duplicate-check detection, payer/payee lookup, decision recorded with the transaction | AI image analysis for alteration and counterfeit printing, fraud score, ID-to-check match, address verification |
| Cash management | Drawer balancing, shift reports, multi-teller support | Vault and armored-car reconciliation |
| Other services | Money orders, bill pay, prepaid cards if offered | Wire, remittance, tax-refund products |
| Reporting | Daily transaction, returned-item and fee-revenue reports | Returned-check rate by teller, payer, and check type |
| Integration | Export to accounting software | Open API so you can add verification or other services from other vendors |
Where most check cashing software falls short: verification
Most check cashing platforms were designed around the transaction and the compliance paperwork. Their "verification" is typically some combination of a routing-number lookup, an internal blacklist of payers whose checks have bounced before, and perhaps a shared negative database. Those are useful, but they miss the three ways stores actually lose money today:
- Counterfeits on real routing numbers. The routing number validates, the bank is real, the payer has never bounced a check with you — because the check was never issued by that payer at all. Only image analysis catches this.
- Altered (washed) checks. A genuine check with the payee or amount changed. Again, every database lookup passes.
- Wrong person. A genuine check presented by someone who stole it. Only matching the ID to the payee, and ideally the ID photo to the face at the counter, catches this.
A modern check verification service adds those layers: AI reads the check and compares every field for internal consistency, the image is analyzed for signs of alteration and counterfeit printing, the routing number is checked against the live FedACH directory and matched to the bank on the check, the check is compared against prior presentments, payer and payee are screened against OFAC, and the ID can be matched to the check and to a live selfie. The teller gets a fraud score and an Approved / Review / Not Recommended result in about ten seconds.
What a good counter workflow looks like
- Identify the customer. Scan the ID; software pulls up the record or creates one. New customers get a photo on file.
- Capture the check. Front and back in one pass; MICR and all printed fields are read automatically. No retyping.
- Verify. Routing validation, image analysis, duplicate check, OFAC and ID match run in parallel — about ten seconds.
- Decide. Approved checks proceed. "Review" goes to a manager with the specific findings on screen. "Not Recommended" is declined with a reason the teller can give the customer.
- Cash out. Fee calculated and disclosed, CTR check applied, receipt printed, drawer updated.
- Record. Images, the verification result and the fraud score are stored with the transaction for the retention period — and are there when a check comes back.
For a step-by-step teller procedure, see how to verify a check before you cash or deposit it.
How to evaluate check cashing software vendors
Ask what "verification" actually means
Have the vendor walk through exactly what happens when a teller submits a check. Does it analyze the image or just look up the routing number? Does it detect duplicates across your locations? Is OFAC screening automatic? Can it match the ID to the check? Our 12 check fraud red flags is a good list of what it should be catching.
Confirm compliance coverage for your state
Fee caps, disclosure wording and licensing requirements vary by state. Make sure the fee engine and receipts are configurable for yours, and that CTR aggregation logic matches FinCEN's rules.
Check speed at the counter
Time a full transaction — new customer, check capture, verification, cash out — in a demo. Anything over two minutes will cause tellers to skip steps on a busy Friday.
Look at the reporting
You want returned-check rate by teller, by payer and by check type. That data tells you where your losses are coming from and whether verification is working.
Ask about the API
Even if you don't need it today, an open API means you can add a stronger verification service, a new money-order provider or an accounting integration later without changing platforms.
Understand the total cost
Add the subscription, per-transaction fees, hardware (scanners, ID readers, receipt printers), onboarding and support. Then compare that total with your returned-check losses for a typical month — for most stores, a verification layer that prevents even one bad $800 payroll check pays for itself.
What check cashing software costs
Full POS platforms for check cashers generally run from a few hundred to over a thousand dollars per month per location, depending on modules and support, plus hardware. Verification is usually priced per check. Check EFI, for example, offers three free verifications, then a flat $0.50 per check on its Business plan with volume pricing for high-volume stores and processors — see pricing. At 400 checks a month that is $200, versus a single counterfeit $1,200 payroll check that would otherwise come straight out of the drawer.
Frequently asked questions
What is check cashing software?
Software used by check cashing stores and other money services businesses to process check cashing transactions: enrolling customers, capturing ID and check images, calculating fees, enforcing BSA/AML compliance such as CTR reporting and OFAC screening, deciding whether to cash a check, and keeping the required records.
Do I need separate check verification software?
Not necessarily separate, but you need verification that goes beyond a routing-number lookup and a blacklist. If your POS vendor only offers those, an API-based verification service can be added alongside it without replacing the POS.
What compliance features are required for a check casher?
At minimum: a Customer Identification Program, Currency Transaction Reports for cash transactions over $10,000 (with same-day aggregation), the ability to document and file Suspicious Activity Reports, OFAC sanctions screening, FinCEN MSB registration, state licensing requirements, and five-year record retention.
Can check cashing software detect a fake check?
Only if it analyzes the check image and validates the routing number against the bank — many systems do neither. Image analysis for alterations and counterfeit printing, combined with ID matching and duplicate detection, is what catches the frauds that database lookups miss. See how to tell if a check is fake.
How fast should verification be at the counter?
Around ten seconds. Longer than that and tellers start skipping it under pressure, which defeats the purpose.
Final thoughts
Check cashing software earns its keep on the transaction and the compliance paperwork — but it protects your profit on the one decision it's often weakest at: whether to cash the check at all. Whichever platform runs your counter, make sure verification covers the image, the routing number, duplicates, sanctions and the person presenting the check, and that every decision is recorded. The stores that lose the least aren't the ones with the strictest tellers; they're the ones where the software makes the right call every time.
