Divine Charles · Fullstack Product EngineerLoading
000%
Getting things ready…

(W/01 · F/05) · Case study

Settings & security

Profile, team, documents, password, and PIN live in one place.

01

The problem

Changing a phone number, inviting a teammate, uploading identity documents, or resetting a PIN meant jumping between unfinished screens. There was no clear settings area.

02

The story

People open settings when something changes: a new teammate, a new phone number, an expiring document. When those tasks were scattered, merchants called support or gave up. Settings gathers profile, team, security, and documents so those jobs have an obvious home.

03

What changed

You can update who you are and who the business is, invite teammates, change password or PIN, and upload identity documents. Sensitive edits ask for a one-time code. Document status is visible so you know if review is still pending.

04

How it was built

Settings was treated as one quiet place for identity and access, not a dump of leftover screens. Profile, team, and security sit together so related jobs stay next to each other. Extra care went to edits that move money or change contact details, so those steps ask for confirmation before they stick.

05

Outcome

  • Profile, team, and security live in one settings area.
  • Sensitive edits ask for a code before they save.
  • Merchants can see whether identity documents are still in review.