Bulk PDF verifier — checking many documents at once

If you've received a stack of Turtini-issued PDFs (an audit packet, a vendor invoice batch, a contract bundle) and want to confirm every one is authentic, visit https://turtini.com/verify with no document id. You'll see a drag-and-drop zone that accepts up to 20 PDFs at a time.

What happens:
• Each file is hashed locally in your browser using SHA-256 — the bytes never leave your device.
• Each hash is looked up against Turtini's pdfVerifications registry.
• Per file you see one of four results:
- Authentic — issued by the org and not modified after issuance.
- Revoked — issued by the org but the issuer has since revoked it (typically because it was superseded by a newer version).
- Not issued by Turtini — no record of this hash. Either the file wasn't generated through the platform, or it was modified after issuance.
- Error — the file couldn't be read; usually it's not a valid PDF.

A summary at the top counts the totals so you can spot mismatches quickly.

When to use this:
• Procurement / AP teams confirming a vendor's monthly invoice batch hasn't been forged en route.
• Auditors comparing a stack of contracts pulled from Drive against what the issuing org actually sent.
• Compliance teams spot-checking customer-facing documents before they're filed.

For a single document, the per-file flow at /verify/{id} (the URL printed under the QR on every page) gives you the same authenticity signal plus the issuing org's metadata. The bulk verifier is the same logic, just batched.

Privacy:
Files are hashed in-browser and discarded. Only the hash is sent to the registry lookup. The platform doesn't see the contents of the documents you're checking.

If you need to verify documents from outside a browser (a server-side audit pipeline, a compliance bot, a contract management system), use the public verifyPdf HTTP API instead — see "Verifying Turtini PDFs from your own systems (verifyPdf API)".