Skip to main content
Article banner
Case Study·Nov 13, 2026·6 min read

Is This Document Real? Screening Invoices, Certificates and Social Media with C2PA Content Credentials

Scams no longer target engineers. They target whoever receives a PDF, a certificate or a “customer” photo and has no way to tell real from generated. C2PA Content Credentials give a file a tamper-evident history, so the check can happen before a person acts on it.


KE
Kerem Ege Pakten
Case Studies · AI
inNewsroom

The fake invoice that fools an accounts team no longer looks fake. Same logo, same layout, new bank details — generated in minutes, paid in seconds. The qualification certificate a candidate attaches looks genuine too, and nobody can verify the issuer from the pixels alone. The people most at risk are not engineers. They are the accounts clerk, the HR officer and the client who receives a PDF.

•The problem: pixels cannot be trusted any more

For a decade the advice was “look closely”. That advice is dead. AI image and document generators produce output that passes visual inspection, and screenshots of real documents can be edited in a browser. What a business needs is not a sharper eye but a different question: not “does this look real?” but “where did this file come from, and has it changed since?”

•What C2PA is: a signed receipt that travels with the file

C2PA is an open standard from the Coalition for Content Provenance and Authenticity. Its steering committee includes Adobe, Amazon, BBC, Google, Meta, Microsoft, OpenAI, Sony and TikTok. The specification covers images, video, audio, fonts and PDF — so invoices and certificates are in scope, not just photos.

  • Assertions. Facts about the file: which device or software made it, what edits were applied, whether an AI model generated it.

  • Claim. Those facts are bundled with a cryptographic fingerprint of the content — a hard binding that breaks if a single pixel changes.

  • Signature. The bundle is digitally signed by the device or company that made it. Together this is a manifest, shown to people as a “Content Credential” or CR badge.

  • Validation. Anyone can check that the fingerprint still matches, the signature is intact, and the signer is on a published trust list.

Every edit adds a new manifest and keeps the previous file as an ingredient, so the chain stays verifiable back to the first capture. The specification defines the states a validator reports: Well-formed, Valid, and Trusted — or a failure code such as a hash mismatch or an untrusted signing credential.

•What it proves — and what it does not

A Content Credential answers one question well: has this exact file changed since a known party signed it? It proves the content is unchanged since signing, who signed it, and what the signer declared — including an AI-generated source type. It does not prove that the content is true. A signed lie is still a lie; you simply know who told it.

→

Missing is not the same as fake. Screenshots and re-encoding strip metadata. A file with no credentials is a file nobody can vouch for — which is exactly why it must route to a human, not to the bin.

•How a business uses it: a first filter, not a final verdict

  • Inbound document gate. Every PDF or image that reaches finance, HR or legal is validated on arrival. Trusted files flow through. AI-labelled or tampered files are blocked with the reason attached. Files with no credentials go to a short manual-check queue.

  • Client relations. Sign what you send — quotes, invoices, reports, certificates — so your client can prove it came from you unchanged. Platforms such as LinkedIn and YouTube already show the badge on media that carries credentials.

  • Social content. Publish brand media with credentials, and watch mentions for media under your name that carries none, or carries an AI label. The same validator, pointed outward.

On day one the check will not be conclusive for every file, and it does not need to be. Adoption is uneven today, so most inbound files land in the “no credentials” lane at first. But the gate already removes most generated or altered material from the pile, and that lane shrinks as cameras, phones, design tools and AI generators sign by default. The point is to have it in place before the fakes get better.

•What we are building

We are turning this into a product: a document gate that sits in front of the inbox your team already uses. Invoices, certificates and media are validated the moment they arrive, routed to release, label-or-block or manual review, and signed on the way out so your clients can verify what came from you. An interactive validator that walks through the checks step by step is on its way to this site.

“

Pixels cannot be trusted any more. The file’s history can.


KE
Kerem Ege Pakten
Founder & CEO, KMCP Solutions
→

Stay tuned. Want early access or a pilot with your own documents? Tell us which files keep you up at night — contact@kmcpsolutions.co.uk.

Subscribe

The KMCP Dispatch

One monthly email. Engineering deep dives, release notes, and behind-the-scenes from our London studio. No filler.

Unsubscribe anytime · GDPR compliant · No third parties