What I learned doing compliance research for a fintech payments product
On DGold Digital Assets I worked on a mobile payments platform: building financial-tool prototypes and doing the regulatory research that shaped the compliance strategy. The research changed the product more than any design review did.
Compliance is a product constraint, not paperwork
It is tempting to treat regulation as something the legal side handles after launch. In payments it decides the product: what you can hold, who you can onboard, how quickly money can move, and what you must be able to prove afterwards.
Reading the rules early meant we designed onboarding, limits and record-keeping around them, instead of retrofitting them into a finished app.
Know-your-customer shapes the first screen
Identity requirements determine how much friction a new user meets in the first two minutes. We prototyped tiered onboarding so a light-verification user could still do something useful, with stronger checks unlocking higher limits.
That single decision protected both conversion and the compliance position.
Prototypes make regulation concrete
Written policy is easy to nod along to and hard to act on. Turning each requirement into a clickable financial-tool prototype forced the questions nobody had answered: what happens on a failed check, who reviews an exception, what the user sees while waiting.
Every prototype round shortened the gap between what the rules demanded and what the product actually did.
Build the audit trail on day one
Logging, versioned records and clear timestamps are cheap while the schema is young and painful to add later. Assume you will one day need to explain any single transaction, and design for that from the start.
The broader lesson: in fintech, research is not a phase before building. It is part of building.