Digital Certificates That Are Easier to Verify
Digital certificates are often sent as ordinary files and then stored separately in many places. The problem appears when the document needs to be proven: who issued it, whether the file has changed, and how others can verify its authenticity quickly.
SertiKu was built to solve that problem. The platform helps institutions issue certificates, manage recipient data, create templates, send certificates, and provide a verification page accessible through a QR code.
With this flow, a certificate is not only a PDF file, but also a digital document with an identity, status, and verification mechanism.
Benefits for Institutions and Recipients
For institutions, SertiKu shortens the certificate issuance process. Participant data can be uploaded in bulk via CSV or Excel, templates can be arranged with a visual editor, and certificates can be managed from a dashboard based on user roles.
For recipients, certificates become easier to share and verify. By scanning a QR code, the verification page displays certificate information so other parties can check its validity without manually contacting the issuer.
For verifiers, the system reduces uncertainty. Verification no longer depends only on the appearance of a PDF, but also on data and hashes stored in the system.
- QR codes speed up the certificate validation process.
- Bulk upload makes mass issuance more efficient.
- The template editor helps institutions create certificate layouts that match their identity.
- Multi-role access separates the needs of users, institutions, admins, and masters.
Security and Trust Advantages
SertiKu does not rely only on a regular database. Certificate files can be checked through SHA-256 and MD5 hashes, so changes to a file can be detected. This matters because digital certificates must preserve document integrity.
IPFS through Pinata is used to store metadata or certificate files in a more distributed way. Metadata includes important information such as certificate number, recipient name, program, issue date, issuer, verification URL, and document hash.
Blockchain through Polygon is used as an additional proof layer. The system can store certificate hashes and transaction hashes, giving verification a more transparent trace.
- Hashes help detect changes to certificate files.
- IPFS supports more open metadata storage.
- Polygon provides auditable integrity proof.
- QR codes keep verification simple for general users.
Designed as a Production-Ready Product
SertiKu is built as a full stack product with operational needs in mind. The system supports email and password login, Google OAuth, wallet login through MetaMask or WalletConnect, six-digit email OTP, password reset, reCAPTCHA, Cloudflare Turnstile, and cookie consent.
The dashboard provides analytics, notifications, support tickets, PWA support, push notifications, SEO metadata, sitemap, robots, and payment integrations such as Midtrans and NOWPayments. This means the project does not stop at core features, but also considers the needs of a growing platform.