Operated by CheckCheck
We run and administer the platform — provisioning, monitoring, audit logging, and compliance evidence — so your team integrates rather than operates.
How it works
At its core, CheckCheck seals a Digital Watermark into a check when it's issued and authenticates it when it's deposited — but underneath sits a regulated, multi-institution platform. Each institution works in its own isolated environment; nothing about your deposits is commingled with another bank's.
1 · Issue
The issuing bank registers the check — amount, payee, and key fields — and those details
are sealed into a Digital Watermark that's carried on the item.
2 · Present
The receiving bank captures the check — MICR, image, and Digital Watermark — at deposit
and submits it for authentication, at the teller line, in the branch, or via mobile
deposit.
3 · Decide
A clear result — match, no-match, or already-presented — comes back in real time. Your
policy turns that into pay, hold, or reject.
4 · Resolve
The payment moves through its full lifecycle, with stop payments and duplicate detection
enforced across the network.
Your own environment
Each institution is provisioned its own isolated environment, with separate data, keys, and secrets. Your records are never commingled with another institution's.
A stable, versioned API
Integrate over a documented, modern API with safe retries, webhooks, and bulk processing. See developer resources for an overview.
You control what's retained
Configurable storage tiers decide how much CheckCheck keeps. New institutions default to retaining no account-holder data — only the Digital Watermark needed to authenticate a check. Higher tiers, for deeper audit or analytics, are opt-in and encrypted at rest.
See where it fits in your workflow
See how registration, verification, and resolution fit your workflow — or talk to us about connecting a pilot to your core.