Talk to the founder

Research for community banks and credit unions

Fraud doesn’t stop at one branch. Neither should your visibility.

When a check turns up at a second branch, tellers need to see prior cashing, returned items, and possible duplicate submissions before handing over cash. Halftone is exploring how to bring that evidence and the supervisor’s decision into one case.

Workflow concept · Fictional example

Check exception review

Teller workstation · Oak BranchCashing · HX-024

Verify check details

Sample check · 042$485.00November 15, 2026
Routing number
•••••0021
Account number
••••7314
  • Prior activity needs review
Teller workstation · Oak BranchCashing · HX-024

Review writer account history

On-us check · Writer account ending in 7314
Available funds
Sufficient for this sample check
This exact check
Check 042 · Returned Nov 12 · Insufficient funds
Same writer, different check
Check 037 · Returned Nov 6 · Insufficient funds
Prior mobile deposit
Possible match for check 042 · Status unavailable in writer history

Log the call to the person or business who wrote the check.

Supervisor workstation · Review queueCashing · HX-024

Review a flagged check

Escalation required
From
Oak Branch teller · 10:16 AM
Alert
Prior return and possible mobile submission
Evidence
Writer history, return evidence and mobile lookup
Check writer callback
Teller note
Confirm whether the possible mobile match is the same item before cashing.
Supervisor workstation · Case historyCashing · HX-024

Review the saved decision

Internal decision record

Case history
  1. Teller escalatedWriter history, return evidence and callback outcome attached.
  2. Decision linked to the check review and teller notes.

The problem

A check can turn up at another branch before the first review is resolved.

A teller may see a possible repeat attempt but still have to call the other branch to learn what was checked or whether someone already placed a hold.

The supervisor needs both attempts and the reason for escalation. Operations needs that same record later to see who decided what and why.

Security principles

Keep check activity inside your institution.

These principles guide the proposed design. Discovery conversations use hypothetical or de-identified examples.

Concept showing Oak Branch and Pine Branch routing exceptions to a supervisor within the same institution.
  • Institution boundariesKeep branch activity within each institution and collect only approved fields.
  • Controlled accessPlan for least-privilege roles, encryption, and agreed retention limits.
  • Human decision authorityKeep staff in control and preserve an audit trail of actions and rationale.

Why Halftone

Carry the evidence from the teller to the decision record.

Existing tools can surface check history or flag risk. Halftone’s proposed workflow would give the supervisor both branch attempts, the teller’s notes, and the callback outcome in one case. The same record would show what the supervisor decided and why, including when they chose a different path from the suggested one.

We’re testing whether that handoff still breaks down at banks and credit unions. A future pilot would test whether staff can assemble evidence with fewer manual steps and leave a more complete decision record alongside their existing tools.

Talk to the founder

If you handle checks or review exceptions at a community bank or credit union, we’d like to hear how your team handles a check that turns up at a second branch.

We’ll ask what your systems show, when staff need to call another branch, and where the decision gets recorded. A hypothetical example is enough. Please leave out customer, account, and check details.