Let anyone verify a certificate you issued
ReciCheck gives every certificate you issue a verifiable record and a public check page, so an employer can confirm it in seconds without contacting your office.
What it does
Each credential gets a unique identifier and a public page showing what was issued, to whom, when, and whether it is still valid. Verifiers need no account. Your office stops answering verification calls one at a time.
- A public verification page per credential, reachable by code or QR
- Bulk issuance from a spreadsheet, so a cohort is one upload
- Revocation, with the reason and date recorded and shown
- An audit trail of every lookup, including when and from where
- Branded certificate output as PDF, with the check code printed on it
How it is delivered
ReciCheck is delivered as a project rather than a self-service subscription. We deploy it into your environment or host it for you, configure it to your certificate types, and hand over the administration. It is not a product you sign up for online today, and it would be misleading to imply otherwise.
Who runs it day to day
Your registrar or administration team. Issuing a cohort is an upload and a review step. Revoking is two clicks and a reason. Nothing needs a developer once it is deployed, which is the main design constraint we built to.
Integration
Most institutions already hold the records somewhere, so the usual integration is a scheduled import from a student information system or an HR platform. Where an API exists we use it. Where one does not, a scheduled file drop works and is often more reliable.
- Scheduled import from an existing student or HR system
- REST API for issuing and revoking programmatically
- Single sign-on for administrators via your identity provider
- Webhooks on issue, revoke and verification events
What happens to the data
Credential records stay in your database, in your environment or an instance we host for you alone. Verification lookups are logged with a timestamp and a coarse location, and that log is yours. We do not aggregate across institutions and there is no shared pool of credential data.
Questions we get asked
Not as a self-service subscription. ReciCheck is deployed per institution, because certificate types, branding and record sources differ enough that a generic sign-up would not work. Deployment typically takes three to five weeks including the first data import. We would rather say that plainly than have you discover it after a demo.
The verification page lives on your own domain and the code is generated, not sequential, so it cannot be guessed from another certificate. The page shows the issuing record from your database rather than anything encoded in the certificate itself, so altering a PDF changes nothing about what the check returns.
Yes, and the public page then shows it as revoked with the date, rather than disappearing. A page that vanishes looks like an error; a page that says revoked is unambiguous. The reason field is optional and you control whether it is shown publicly or held internally.
They can be imported retrospectively, which most institutions do for the last few years of graduates. A spreadsheet with name, credential and date is enough to generate records and check codes, though the printed certificates obviously will not carry a QR code. Verifiers can still look them up by name and year.
What clients say on Google
Unedited, pulled live from our Google Business listing.
Loading reviews from Google - read them on Google.
Issuing certificates people need to verify?
Tell us what you issue and how many a year, and we will say what a deployment would involve.
- USD
- EUR
- GBP
- CHF
- SGD
- AUD
- CAD
- AED
- SAR
- QAR
- JPY
- INR
Card, netbanking, wallet and UPI through Razorpay, which is what our checkout runs on, so anything it accepts we accept. Bank transfer, SEPA, Wise and Payoneer for invoices that prefer it.
NDA before the first call. Full IP assignment on delivery. Contracts under Indian, English or Delaware law.