Joint Account Spending Permissions
Design spending controls for a joint account that clarify co-owner rights, card limits, approvals, and recent permission changes.
The brief
Understand the problem
Background
Households may share one account while needing different controls for co-owners, additional cardholders, and dependents. Limits can support coordination, but they should not quietly remove a legal owner's access or create coercive control.
User context
Dev and Arun share household expenses and have issued a limited card to Dev's sixteen-year-old daughter. They want her to buy groceries while preventing cash withdrawals and keeping urgent requests possible.
Product problem
The household needs understandable controls that respect account ownership, reveal who changed what, and recover safely when a payment is blocked.
Objective
Create role overview, permission editing, approval requests, and audit states for a shared spending arrangement.
What to design
Define the experience
Required experience
- Review members, ownership, cards, and effective permissions
- Change a dependent card's categories and limits
- Respond to an urgent spending request
- Inspect and reverse a recent eligible control change
Screens and states
- Household account roles
- Card permission editor
- Spending request review
- Activity and change history
Core user flow
Follow the critical path
- 01
Dev opens the household role overview and selects his daughter's card
- 02
He enables grocery purchases, sets a weekly cap, and keeps cash withdrawal disabled
- 03
She requests a temporary increase while shopping for a family event
- 04
Arun approves it for one transaction and the decision enters the shared history
Product rules
Requirements and constraints
Requirements
- Distinguish legal owners from delegated cardholders
- Show effective controls and their source before editing
- Support amount, category, merchant type, location, and time-bound rules where available
- Notify affected members about material changes
- Record approvals, declines, expirations, and reversals
Constraints
- One co-owner cannot secretly remove another co-owner's legal account access
- Merchant category data can be missing or inaccurate
- Controls may not stop offline or previously authorized payments
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens plus a role and permission matrix
- State notes for concurrency, notification, and offline payment behavior
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.