All work

Multi-Brand Identity Verification Portal

One careful place for identity checks across several brands.

Role
Sole developer
Status
Production
Stack
Django · Python · Verification provider API

How it fits together

A simplified illustration. No identity documents, records or brand names are shown.
01

Context

Several brands each needed to verify customers’ identities. Running a separate process for each one duplicated work and spread sensitive data around.

I built a single multi-tenant portal that handles verification for all of them, and I’m its sole developer.

02

Constraints

  • Identity data is among the most sensitive data a system can hold.
  • Each brand should only see its own customers.
  • Verification goes through an authorized provider, not a direct government connection.
03

What I built

  • A multi-tenant verification workflow shared by several brands.
  • Integration with an authorized identity-verification API provider.
  • Masking of identity data in the views where it isn’t needed in full.
  • Encrypted storage of identity-related data.
04

Tradeoff: Show less by default

Masking data in everyday views makes some support tasks a step longer. In exchange, far fewer screens ever show identity data in full.

05

Outcome

Several brands share one identity-verification workflow instead of each running its own.