About OpenClear

The author

OpenClear is written and maintained by Chaffed (github.com/chaffed), a bank payments professional with:

• 20 years in bank systems, payments and check processing;
• the Accredited ACH Professional (AAP) credential;
• day-to-day experience running positive pay from the bank's side: onboarding business customers, issue file problems, exception queues, cutoffs, returns, and the questions examiners and auditors ask.

The positive pay guides on this site come from that experience. They're written for the people at banks and credit unions who operate the service, not for the business customers who use it.

Why OpenClear exists

This was built using Claude Code. I am not a developer/programmer. I do have 20 years of bank systems, payments, and check processing experience. This is the Positive Pay system I want. My goal is to demonstrate banking software needs to be modernized.

Much of the software banks run on is old, closed and hard to examine. OpenClear is an argument that it doesn't have to be. Someone who knows the business deeply can now build modern software with AI coding tools: multi-tenant, tested on every release, with signed audit logs and automated control testing. Publishing it as open source means anyone can check the claim.

The project

• License: GNU Affero General Public License v3 or later.
• Source: github.com/chaffed/OpenClear. Bugs and questions go in GitHub issues.
• Try it: a free sandbox bank, or run it locally in one click.
• History: formerly called PosPay. Existing installs kept working through the rename; see the changelog.

Independence

OpenClear is a personal, independent project. It isn't affiliated with, endorsed by or built for any employer, bank or vendor, and the views on this site are the author's own. The guides describe positive pay in general terms and don't evaluate or compare specific commercial products.