How our receipts hold up.

Where to find each product's details.

Sealed (our SMB receipts product) publishes the deepest documentation — it's the one most often reviewed by buyers' procurement teams. The other products share the same receipt substrate and the same public record.

The promises we make.

• Bank-grade hardwareEvery public record we publish is signed inside the same kind of secure hardware that signs ACH transactions for U.S. banks. The signing key is identified publicly so anyone can confirm it's ours.
• Future-proof signaturesEvery receipt carries two independent signatures — one of today's standards, one built to survive quantum computers a decade out. A forger would have to break both at once.
• Court-grade retentionRecords are kept at least seven years. Longer retention is available on higher plans. The retention period is part of the receipt itself.
• SOC 2 Type IIIn progress. Evidence collection is live. Type II report target: Q4 2026.
• IBM Partner PlusEnrolled. Twelve of our agents are listed in IBM's watsonx Orchestrate marketplace.
• Built on CloudflareTrust-hub partner. Workers run at the edge in 300+ cities; your seals don't slow down because we don't have a server room.

How a receipt actually works.

Plain-English version of what happens behind every sealed document:

• Step 1 · Take the fingerprintThe moment your document is sealed, we compute a unique digital fingerprint of it. Change one byte, the fingerprint changes completely.
• Step 2 · Add it to the hour's batchEvery fingerprint joins that hour's batch of receipts. Once an hour, the whole batch gets bundled into a single public-record entry.
• Step 3 · Sign the public recordThe hour's record is signed twice — one signature for today's standards, one built to survive future quantum computers. Both signatures are public.
• Step 4 · Lock it in hardwareThe signing happens inside bank-grade secure hardware. The hardware's identity is published as part of the record.
• Step 5 · Anyone can checkOpen chain.epochcoreqcs.com, paste the receipt's fingerprint, see the answer. No account, no API key, no calling us.

Every receipt across every EpochCore product traces back to a single founding record from when we started. The math underneath is the same math underneath the U.S. banking system.

We sign our own software the same way.

Every time we update our software, we publish a build receipt — a snapshot of the exact code that was running, with its own fingerprint, added to the same public record where your receipts live. So when someone asks "what was the version of your software when my contract was sealed?", we point at the record and they verify it themselves.

• Latest build receipt Check today's record on the public verifier →
• What's inside The full source code of every public product we run, every file fingerprinted. Anyone can untar the build receipt and read the exact code that was running.
• How it ties back The build receipt and your customer receipt land in the same hour's public record. Forging either would require forging both — and the math behind that resistance is the same math behind U.S. banking infrastructure.
• What this answers "What code was running when my client's contract was sealed?" The build receipt from that hour is the answer — and we don't have to be in the room for you to verify it.

We publish a fresh build receipt every time we ship. The verifier link above always reflects the latest one we've published.

Your content stays yours.

We publish a machine-readable opt-out so AI-training crawlers can't use anything on our public pages. We don't grant any third party permission to train models on your sealed records.

Security disclosure.

Responsible-disclosure path for vulnerabilities in any EpochCore-operated surface: seal.epochpay.today/security. Same-day acknowledgment; coordinated-disclosure timelines on request.