Case 04 of 10

Certify

Dynamic certificate generation with customisable templates and a validation portal.

• My part: Contributed (owned features, logic or change requests)
• Role: Feature owner
• Where: Pexus product suite · ING Tech
• 5+ tenants

The picture on this page is a concept illustration, not a product screenshot.

The problem

Every organisation wants certificates that look and read like its own, yet every certificate still has to be generated reliably and remain verifiable afterwards.

My responsibility

Feature ownership: multiple features within the platform, not the product as a whole.

• Owned and delivered multiple product features.
• Worked on enhancements and requirements supporting different tenant needs.

Decisions and contributions

• Tenant requirements gathered from different organisations and folded into one platform instead of one-off builds.
• Generation and validation treated as one flow: a certificate is only useful if it can be verified later.

Working with engineering, QA and stakeholders

• Managed product requirements and coordinated feature delivery across the development lifecycle.

Challenges and trade-offs

• Configurability: what a tenant can customise in a template, and what stays fixed so generation behaves consistently.

Outcomes

A configurable certificate platform in use across 5+ tenants: organisations generate certificates to their own templates, and issued certificates can be checked through the validation portal.