Here's a question that most fintech teams can't confidently answer: is the consent you're collecting from users actually legally valid?
Not 'does it have a checkbox?' — that's necessary but not sufficient. Is the consent specific? Is it informed? Is it freely given? Is it an unambiguous affirmative action? Because if any one of those four requirements isn't met, the consent you're collecting is legally meaningless — regardless of how many checkboxes you have.
This lesson maps the four legal requirements for valid consent under GDPR and UK financial regulation, the four consent design patterns (three that work, one that doesn't), a consent copy rewrite workshop, a flow sequencing exercise, and a 16-point pre-handoff checklist.
Consent design is the most legally consequential UX decision a fintech designer makes. A poorly designed payment form creates a poor user experience. A poorly designed consent screen creates a compliance failure — an invalid consent record that exposes the company to regulatory action and leaves users without the protections they thought they'd agreed to.
Let's start with what the law actually requires — because the patterns follow directly from the requirements.