checkscanner
Python package for the check scanner backend. Manages connections to Magtek and RDM check scanning devices, extracts MICR data and check images, and serves them through a JWT-authenticated REST API.
Requirements
- Python 3.6+
- SQLite3
- pip 21.3.1+ (required on Python 3.6 to resolve pre-built wheels)
Installation
Ensure pip is up to date before installing:
pip install --upgrade pip
Then install the package from PyPI:
pip install checkscanner
Or from the source tree:
cd server
pip install .
For development (changes take effect without reinstalling):
pip install -e .
Building the Frontend
The frontend must be built and bundled into the package before installing. Run this once from the source tree (requires Node.js):
checkscanner build
pip install . # reinstall to pick up the bundled frontend
In development with an editable install, checkscanner build copies the output directly into src/checkscanner/static/ so it takes effect immediately without reinstalling.
Usage
The package installs two commands. Run them from your project directory — config files and the database are created there.
# Start the API server (serves UI at http://localhost:8000/).
# Runs first-time setup automatically if needed.
checkscanner
# Open the interactive admin console
checkscanner-cli
checkscanner also accepts subcommands (run checkscanner --help or checkscanner <command> --help for details):
checkscanner server [options] # Same as no arguments; see `checkscanner server --help`
checkscanner setup [-i] # Create anything missing: config/, server.db, admin user (-i: edit config first)
checkscanner status # Show config, database and connection status
checkscanner admin # Same as checkscanner-cli
checkscanner build # Build the frontend and bundle it into the package (source tree only)
checkscanner user list|add|passwd|delete
checkscanner profile list|add|delete
checkscanner config show|edit|rotate-keys
checkscanner token <username>[:<password>] # or -u <username> [-p <password>]
Server options can also be passed directly, e.g. checkscanner --port 9000.
First-Time Setup
checkscanner setup (also runs automatically before the server and admin console start) creates:
| File | Description |
|---|---|
config/config.toml |
Server host, port, debug mode |
config/auth.toml |
JWT signing key, FTP credentials |
server.db |
SQLite database |
admin_credentials.txt |
Generated admin username and password — delete after noting |
Admin Console
checkscanner-cli opens an arrow-key menu for managing the server:
- View server status
- List, add and delete users; reset passwords
- List, add and delete check scanner profiles
- Edit config and regenerate auth keys
- Get a bearer token for API testing
- Start the server, optionally restarting it automatically when it stops
Every menu action is also available as a checkscanner subcommand for scripting.
API
Swagger UI is available at http://localhost:8000/docs when the server is running.
| Method | Endpoint | Description |
|---|---|---|
| POST | /token |
Authenticate, receive JWT |
| GET/POST | /connections |
List or create reader connections |
| DELETE | /connections/<id> |
Disconnect from reader |
| GET/PUT | /connections/<id>/check |
Get check data or return check to queue |
| GET/POST/PATCH/DELETE | /profiles |
Manage reader device profiles |
| GET/POST/PATCH/DELETE | /users |
Manage users (admin only) |
Supported Devices
| Type | Protocol |
|---|---|
| Magtek | Telnet + FTP |
| RDM | HTTPS (XML) |
Project Structure
src/
└── checkscanner/
├── app.py # Bottle API server
├── admin_console.py # Interactive admin CLI
├── active_scanners.py # In-memory scanner connection registry
├── auth.py # Password hashing and JWT verification
├── ftp_server.py # FTP server for Magtek image uploads
├── debugger.py # Colored terminal logging
├── bottle/ # Vendored Bottle framework + plugins
├── resources/ # REST resource handlers
├── check_scanner_handlers/ # Device-specific connection handlers
├── static/ # Bundled frontend (populated by `checkscanner build`)
├── swagger/ # Bundled Swagger UI
└── data/ # Bundled assets (schema, font, API spec)
Dependencies
| Package | Purpose |
|---|---|
gevent |
Async concurrency for the server |
Pillow |
Check image processing |
pyftpdlib |
FTP server for Magtek readers |
PyJWT |
JWT signing and verification |
requests |
HTTP client for RDM readers |
toml |
Config file parsing |
Metadata
Release files for checkscanner 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| checkscanner-0.1.4.tar.gz | 5.5 MB | Without provenance | Details for checkscanner-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| checkscanner-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for checkscanner-0.1.4-py3-none-any.whl |
Total release size: 11.1 MB
Release files / checkscanner-0.1.4.tar.gz
| Download URL | checkscanner-0.1.4.tar.gz |
|---|---|
| Size | 5.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ecbe178f9581b979cae8d0fd19d9fc7d0c96bab6249694cbcc8554e2ded77d6
|
|
BLAKE2b-256 checksum How to use checksums |
21120dddb320780c7e37305b0825dd58597a843747d698a911ce4824412732f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
Release files / checkscanner-0.1.4-py3-none-any.whl
| Download URL | checkscanner-0.1.4-py3-none-any.whl |
|---|---|
| Size | 5.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fab4a49068db40dc147e2bb0d3dff51d0a92c630a9058f58a71885d46239b7b4
|
|
BLAKE2b-256 checksum How to use checksums |
3188583fcc2bb2fa63670a1d3bbc6a1ca026304abefa6c8aae3ee1328f2e5ab9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
Security for checkscanner 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.