litmus

Open this on a laptop

The canvas needs room: requirements on one side, live feedback on the other. Any screen 1024px or wider works.

Design a KYC System

hard

Customers fill a journey that adapts to them, slow outside checks never lose a case, and every product reads their status.

Browse all problems

The problem

Build the KYC platform of a bank or fintech. Every product sends customers through it to prove who they are, and asks it later whether a customer is verified.

Each case waits on outside providers for about 5 checks, some answering in seconds and some a minute later, and a retry must never pay twice.

Every decision must be explainable years later, and personal data lives in one locked place.

What it must do

  • Journey. The steps and fields fit the customer, from a journey version pinned when the case starts. Photos go straight to storage.
  • Verify. One durable workflow per case runs each check with an outside provider, swaps a provider that's down, and never pays twice.
  • Decide. Screen against sanctions and politically exposed people, apply a versioned policy, keep every reason, and announce the decision.
  • Status. Any product reads a customer's level, risk tier and expiry date from a cache.

What you'll learn

  1. Start with the simplest design that works
  2. Keep files out of the database
  3. Keep running when a server dies
  4. Run slow checks on their own clock
  5. Keep personal data behind tokens
  6. Screen and decide with clear rules
  7. Explain any decision years later
  8. Answer a status check on every payment