TellerScan TS240 & CheXpress CX30 Driver Download + Installation Guide

Installing the driver for a Digital Check TellerScan TS240 or CheXpress CX30 comes down to a sequence most teams get backwards: install the software first, connect the hardware second. Download Digital Check's universal USB driver — currently version 25.03 — or run the installer your bank's remote deposit platform supplies, complete the installation, and only then plug the scanner into a USB port. Connecting the scanner before the driver is loaded is the single most common reason a check scanner refuses to be recognized.

For branch and teller environments, the TS240 is the workhorse: it scans at up to 100 documents per minute and feeds from a 100-item hopper, so an operator can load a stack and step away. The CheXpress CX30 is the desktop counterpart, rated at up to 30 documents per minute with a single-item manual feeder — well matched to a merchant counter or a low-volume back office. Both capture at 300 dpi and both run on current Windows.

Browser-based remote deposit capture (RDC) adds one more layer. Modern RDC platforms run in a web browser, and browsers cannot talk to USB scanner hardware on their own. A small Windows service called Ranger Remote bridges that gap, and it must be installed after the device driver. This guide walks through the full stack — driver, Ranger interface, Ranger Remote, and the RDC application — plus Windows compatibility, MICR, Check 21 compliance, and how to choose between the two scanners by volume.

What a check scanner driver is — and the layers above it

A scanner driver is the software that lets the Windows operating system recognize and control a piece of hardware. For a check scanner, the driver tells Windows how to drive the transport, fire the camera, read the magnetic ink line, and return images to an application. Without the correct driver loaded, the operating system sees an unidentified USB device and nothing scans.

Check scanners differ from ordinary document scanners in one important way: the application that actually captures the deposit is rarely talking to the driver directly. Instead it talks through a standard interface called Ranger, developed by Silver Bullet Technology. Ranger acts as a universal translator between item-processing software and dozens of scanner brands and models — it plugs into more than 100 popular item-processing applications — so a financial institution can change scanner hardware without rewriting its deposit software.

The four layers you are actually installing

A working check-capture station is a stack of four pieces. Installing them in the wrong order is the usual cause of a station that powers on but never scans.

Digital Check has manufactured more than 1.5 million check scanners at its Rancho Cucamonga, California plant since 2004, and the TellerScan and CheXpress lines are among the most widely deployed in North American banking. That ubiquity is why most bank RDC platforms ship installers that already bundle the Digital Check driver and Ranger components — when one is provided, it is usually the safer package to run because it matches the version the platform was tested against.

TS240 vs CX30: matching the scanner to check volume

The two scanners solve different problems. The TS240 is built for batches; the CX30 is built for the occasional check. Choosing between them is mostly a question of how many items a station handles per day and whether an operator can load a stack rather than feed one item at a time.

The TellerScan TS240 scans at a top speed of up to 100 documents per minute and is sold in 50, 75, and 100 documents-per-minute configurations. It feeds from a 100-item input hopper and captures images at 300 dpi using a tri-color LED image sensor, drawing 45 watts. It is supported on Windows 11 and 10 (x86 and x86-64) and on macOS, connecting over USB 2.0 — the profile of a teller line or back-office capture station.

The CheXpress CX30 is the desktop unit. It is rated at up to 30 documents per minute in Scan & Return mode, fed one document at a time through a manual 'drop and slide' feeder, with a transport that runs at 19.69 inches per second. It captures at 300 dpi and draws 24 watts. The CX30 requires Digital Check's DCC API version 9.00 as a minimum, with version 10.09 or newer recommended — a detail worth confirming if you are pairing an older unit with newer software.

The CheXpress line is the best-selling remote-deposit-capture scanner ever produced, having sold close to a million units worldwide, which is why so many merchant and small-business deposit programs are built around it. Both models also have current successors worth knowing about: the CX30's successor, the CX35, uses dual 600-dpi color image sensors — double the CX30's 300-dpi resolution — and the TS240 is succeeded by the multi-feed TS250. Drivers and Ranger components are shared across the families, so the install procedure below applies regardless of which generation is on the desk.

Step-by-step: installing the TS240 and CX30 driver

The procedure is the same for both scanners. The order is non-negotiable: drivers — or the bank's deposit software, if it contains them — must be installed before the scanner's USB cable is connected to the PC. The steps below assume a fresh Windows workstation.

1. Confirm the model and the required versions. The TS240 uses Digital Check's universal USB driver; the CX30 additionally requires DCC API version 9.00 at minimum, with 10.09 or newer recommended.
2. Leave the scanner unplugged. Do not connect the USB cable yet, even though the temptation is to plug in the new hardware first.
3. Obtain the installer. Download the universal USB driver — currently version 25.03 — from Digital Check, or use the installer your bank's RDC platform provides. The bundled bank package is usually the safer choice because it matches the platform's tested version.
4. Close the browser and any deposit application, then run the installer as an administrator and let it complete.
5. For browser-based RDC, install Ranger Remote after the device driver finishes. Do not install it before the driver.
6. Only now connect the scanner to a direct USB 2.0 port — not a hub — and position it at least 6 inches from its power supply and other electronics.
7. Power on the scanner and let Windows enumerate the device. Confirm the status indicator reaches its ready (green) state.
8. Launch the scan utility — Digital Check's ScanLite demo utility or your bank's application — and run a test scan. Verify the MICR line reads cleanly and the image is sharp at 300 dpi.

Windows 11 and 10 compatibility

The most common compatibility question — whether a separate Windows 11 driver is needed — has a clear answer. All of Digital Check's Windows 10 drivers have been certified for Windows 11, and no separate Windows 11 drivers are released, so existing drivers do not need updating when a workstation moves to Windows 11. Time spent hunting for a 'Windows 11 driver' is time wasted; there isn't one, by design.

The universal USB driver (version 25.03) operates all current CX and TS scanners on Windows 10 and 11 in both 32-bit and 64-bit. The TS240 is also supported on macOS over USB 2.0, though banking RDC platforms are predominantly built and tested for Windows, so Mac deployments should be confirmed with the financial institution before they are standardized.

Ranger, Ranger Remote, and browser-based RDC

Ranger Remote is a Windows service that lets web browsers communicate with check-scanning hardware, and it must be installed after the scanner driver for browser-based remote deposit capture. The reason it exists is a security boundary in modern browsers: a web page cannot reach down to a USB device directly. Ranger Remote runs locally as a service, the browser-based RDC application talks to that service over the local machine, and the service in turn drives the scanner through the Ranger interface.

Because Ranger plugs into more than 100 popular item-processing applications, the same scanner can serve different deposit platforms without driver changes — only the application layer differs. That is what makes the Digital Check hardware portable across banks and software vendors.

Driver-only vs browser RDC

• Traditional installed Windows deposit application: the device driver and Ranger interface are usually enough; Ranger Remote may not be required.
• Browser-based RDC (the common case today): install the device driver first, then Ranger Remote, then sign in to the web application.
• If a browser-based platform cannot see the scanner, the Ranger Remote service not being installed or not running is the first thing to check.

MICR: why magnetic ink and scanner placement still matter

Every check carries a line of characters printed in magnetic ink along the bottom — the routing number, account number, and check number. This is MICR, Magnetic Ink Character Recognition, and it has been printed on checks since 1959. A check scanner does two things at once: it photographs the document at 300 dpi and it reads the magnetic MICR line with a dedicated magnetic read head. The MICR read is what makes the captured item a payable instrument rather than just a picture.

Because the MICR head reads magnetism, it is sensitive to magnetic interference. Position the scanner at least 6 inches away from its power supply and other electronics to avoid interference with the read head. A scanner sitting on top of a power brick, a monitor, or a stack of other powered devices will produce intermittent MICR misreads that are easy to mistake for a software fault.

Check 21 and remote deposit capture: the legal backbone

The reason a scanned image can stand in for a paper check is a single federal law. The Check Clearing for the 21st Century Act — Check 21 — was signed into law on October 28, 2003, and its provisions took effect on October 28, 2004, after which banks must accept a legally equivalent substitute check in place of an original. That equivalence is what allows an image captured on a TS240 or CX30 to clear without the paper ever leaving the building.

Remote deposit capture is the practice built on top of Check 21: a business or branch scans checks on-site and transmits the images to the bank for deposit. The hardware is only part of the picture — the FFIEC treats RDC as a process that must be risk-managed. Notably, the FFIEC considers single-factor authentication inadequate for internet-based RDC and directs institutions to implement multifactor authentication or layered security. IT teams deploying RDC should plan for that control from the start rather than retrofit it.

The remote deposit capture workflow

1. Sign in to the bank's RDC platform using multifactor authentication.
2. Create a deposit and enter the expected total amount.
3. Load the checks and scan them so both the images and the MICR line are captured.
4. Review the batch and correct or re-scan any rejected items.
5. Balance the deposit to the control total.
6. Submit the deposit for the bank to process and clear.

Worked example: what 30 vs 100 DPM means for an end-of-day backlog

The throughput difference between the two scanners is easiest to see with a worked example. The check count below is illustrative; the per-minute rates and hopper capacity are Digital Check's published specifications.

Assume a branch has 600 checks to capture at the close of business (an illustrative figure). On a CheXpress CX30, rated at up to 30 documents per minute and fed one item at a time, the transport alone accounts for roughly 600 ÷ 30 = 20 minutes — before the manual effort of feeding each check individually. On a TellerScan TS240 running at its top speed of 100 documents per minute, the same 600 checks represent about 600 ÷ 100 = 6 minutes of transport time, spread across roughly six loads of its 100-item hopper, with the operator free between loads.

Across a full year, that gap compounds. A site clearing several hundred items a day recovers meaningful operator time by moving from single-feed to hopper-fed capture, which is the practical reason branches standardize on the TS240 while merchant counters and low-volume offices stay on the CX30. Energy is a minor factor by comparison — the TS240 draws 45 watts against the CX30's 24 watts — so the economics are driven by labor and throughput, not power. Published purchase prices are not included here; they vary by reseller and by the bundle a bank's RDC platform requires.

Troubleshooting common driver and scanner problems

Most check-scanner faults trace back to install order, a loose connection, MICR placement, or the Ranger Remote service. The table below maps the symptoms a help desk sees most often to their likely cause and the first corrective action.

A red status light is worth a closer note because it alarms operators. It generally means the scanner has power but is not ready to scan, most often because the driver is not loaded, the USB connection dropped, or a document jam or open cover is interrupting the track. Work through those three in order before concluding the hardware has failed.

Common mistakes — and when a desktop check scanner is the wrong tool

• Plugging the scanner in before installing the driver. The most common mistake, and the one that produces an unrecognized device.
• Hunting for a separate Windows 11 driver. Digital Check's Windows 10 drivers are certified for Windows 11; there is no separate version.
• Installing Ranger Remote before the driver. For browser RDC the order is driver first, then Ranger Remote.
• Placing the scanner on or beside its power supply. This causes intermittent MICR misreads that look like software faults.
• Connecting through a USB hub instead of a direct port, which can cause the scanner to drop off during high-speed capture.

There are also cases where a desktop check scanner is simply the wrong tool. Very high-volume image cash letter operations are served by faster multi-feed transports, not a single TS240 or CX30. And a check scanner is not a general document scanner: capturing patient files, contracts, or invoices for archiving calls for a document scanner and a content management system, not a MICR-equipped check unit. A frequent expectation to correct is that a check scanner deposits directly into accounting software such as QuickBooks — it does not. Checks deposit through the bank's RDC platform via Ranger; the accounting system reflects the cleared deposit afterward through its bank feed.

Choosing and supporting check scanners in the Lehigh Valley

Community banks, credit unions, and the businesses that bank with them across the Lehigh Valley — Allentown, Bethlehem, Easton, and the surrounding Mid-Atlantic — run the same TellerScan and CheXpress hardware as institutions nationwide. What varies is the support model. A scanner that drops off USB mid-batch on a Friday afternoon is a local operations problem, and a vendor that can specify the right unit, stage the driver and Ranger components correctly, and respond on-site matters more than the marginal spec differences between models.

Reynolds Business Systems has supported document capture and records systems for organizations in the region for more than 55 years from its base in Emmaus, Pennsylvania. For teams standardizing check capture, the decisions that pay off are the unglamorous ones in this guide: choosing the TS240 or CX30 by realistic daily volume, installing the driver before the hardware, layering Ranger Remote correctly for browser-based RDC, and giving the MICR head the clearance it needs. Get those right and a check-capture station becomes infrastructure that fades into the background — which is exactly what an operations team wants from it.

Frequently asked questions

How do I install the driver for a Digital Check TellerScan TS240?

Install Digital Check's universal USB driver — currently version 25.03 — before you connect the scanner. Run the installer (or your bank's remote deposit package) as an administrator with the scanner unplugged, let it finish, then connect the TS240 to a direct USB 2.0 port. For browser-based deposit capture, install Ranger Remote afterward, then run a test scan to confirm the MICR line reads.

Where can I download the TellerScan TS240 or CheXpress CX30 driver?

Digital Check publishes its drivers and the ScanLite demo utility on its downloads page, where the current universal USB driver is version 25.03. In most banking deployments, though, the correct driver and Ranger components are bundled inside the remote deposit capture installer your financial institution provides — using that package is usually the safer path because it matches the platform's tested version.

Is the TellerScan TS240 driver compatible with Windows 11?

Yes. Digital Check certified all of its Windows 10 drivers for Windows 11 and does not release separate Windows 11 drivers, so an existing installation does not need updating when a PC moves to Windows 11. The universal USB driver (version 25.03) runs every current TS and CX scanner on Windows 10 and 11 in both 32-bit and 64-bit.

What is Ranger Remote and do I need it to scan checks in a browser?

Ranger Remote is a small Windows service that lets a web browser communicate with check-scanning hardware, which browsers cannot do on their own. If your remote deposit platform runs in a browser, you need it, and it must be installed after the device driver. If your deposit software is a traditional installed Windows application, you may not need Ranger Remote at all.

Why is my TellerScan TS240 showing a red light?

A red rather than green status light usually means the scanner has power but is not ready to scan. The most common causes are a driver that is not loaded, a USB connection that dropped, or a document jam or open cover in the track. Clear any jam, reseat the USB cable to a direct port, and confirm the driver service is running, then power-cycle.

Do I install the check scanner driver before or after plugging in the USB cable?

Before. The driver, or the deposit software that contains it, must be installed before the scanner's USB cable is connected to the PC. Connecting first leads Windows to register the device incorrectly, which is the most frequent cause of a scanner that will not be recognized. If that happens, unplug the scanner, install the driver, then reconnect.

What scanner is compatible with QuickBooks?

Check scanners such as the TS240 and CX30 are not designed to deposit directly into QuickBooks. They capture checks for your bank's remote deposit capture platform through the Ranger interface, and the deposit clears through the bank. QuickBooks then reflects the cleared deposit through its bank feed. For scanning receipts or invoices into QuickBooks, a general document scanner is the right tool, not a check scanner.

What are the steps under remote deposit capture?

Remote deposit capture follows a consistent sequence: log in to the bank's RDC platform with multifactor authentication, create a deposit and enter the amount, load checks and scan them so images and the MICR line are captured, review and correct any rejected items, balance the deposit to the control total, then submit for the bank to process and clear.

How many documents per minute does the TellerScan TS240 scan?

The TellerScan TS240 scans at a top speed of up to 100 documents per minute and is sold in 50, 75, and 100 documents-per-minute configurations. It feeds from a 100-item hopper and captures images at 300 dpi using a tri-color LED sensor. By comparison, the CheXpress CX30 is rated at up to 30 documents per minute, fed one item at a time.

What is the difference between the TS240 and the CX30?

The TS240 is a branch and teller workhorse: up to 100 documents per minute from a 100-item automatic hopper, drawing 45 watts. The CX30 is a desktop, single-feed unit rated at up to 30 documents per minute, drawing 24 watts, suited to a merchant counter or low-volume office. Both capture at 300 dpi. Choose by daily volume and whether an operator can batch-feed.

Does the TellerScan TS240 work on macOS?

The TellerScan TS240 is supported on macOS as well as Windows 11 and 10, connecting over USB 2.0. Most banking remote deposit platforms, however, are built and tested for Windows, and the Ranger Remote service is a Windows component. Confirm with your financial institution that its RDC application supports macOS before standardizing check capture on Mac hardware.