UzSU needed membership status that could be checked immediately while keeping subscription, profile, and verification data structured enough for daily administration.
Case study
Verifier App for UzSU
A production membership platform that connects subscription choices, member records, digital QR passes, public verification, and administration in one workflow.
A prepared portfolio composite shows the verification product across desktop and mobile without cropping the interface.
Built an Angular and NestJS platform around regional membership plans, Stripe-backed subscriptions, Prisma/PostgreSQL records, digital QR passes, and a public verification surface.
Turned membership verification into a coherent product flow: choose a plan, maintain an active record, present a QR pass, and verify it in real time.
Context
UzSU needed more than a membership landing page. A member had to be able to join, understand the available plan, access a reusable digital pass, and confirm that the membership was still active. Staff needed the same information represented as structured records rather than scattered confirmations or manually checked messages.
The project scope covered application architecture and full-stack implementation under PenguinDev: the Angular interface, NestJS API, relational model in Prisma and PostgreSQL, Stripe subscription path, and the operational surfaces around verification and membership management.
The Product Flow
The product starts with a regional membership choice. That matters because availability and benefits can differ between the United Kingdom, Germany, and global membership without requiring separate applications. Free membership can create a record directly; premium membership adds a Stripe-backed subscription state before the member record becomes the source of truth.
From there, the member receives a digital QR pass. The public verifier deliberately does one job: accept the member token represented by the QR code and return the current status. Keeping this surface narrow reduces ambiguity for a partner or event organizer who only needs to answer one question: is this membership valid now?
Decisions and Tradeoffs
The central decision was to model membership as data, not as a generated image. The QR pass is only a portable pointer into the current record. Expiry, plan, and active status remain server-controlled, so a previously issued pass cannot become a permanent source of truth by itself.
The second decision was to keep the public verification surface separate from the richer member cabinet and administration views. Public verification should reveal only the result needed for the interaction; profile, billing, and internal management information stay behind authenticated access.
The application also connects public acquisition and internal operations. The same plan definitions shown during signup feed the membership and subscription workflow, rather than creating a disconnected marketing page that staff later reconcile manually.
Screenshots and Access
The live public portal, verification form, and membership options can be inspected directly. Administration exists as part of the shipped system, but screenshots containing member identifiers and profile data are intentionally excluded from this portfolio. The system map communicates that operational layer without turning client data into visual decoration.
Result
UzSU gained a single product path spanning membership selection, subscription state, a digital pass, public verification, and administration. The visible interface is connected to payments, relational data, access boundaries, and the organization’s operational workflow.
Contact
Let's talk.
For professional opportunities, collaborations, or selected freelance work.
Open to conversations Frankfurt, Germany Europe/Berlin
GitHub penguindevteam@gmail.com