Feedback
Roadmap
Changelog

Privacy mode: mask all amounts, reveal on hover or toggle

I would like a privacy mode that hides every monetary value in the app, so opening FinWise in public does not put my finances on display. The situation is ordinary: checking a balance on a train, in a queue, in a cafe, or in an open-plan office. On a phone especially, anyone beside or behind me can read the screen. Right now the only way to avoid that is not to open the app. How I would expect it to work: Masked by default on every app open, showing something like R••••• A single toggle in the header that reveals everything, and hides it again when tapped a second time, OR just tapping value acts as the toggle. Peek on hover for individual values on desktop, so a single figure can be checked without unmasking the whole screen. Optional persistence, so it either resets to hidden every launch or remembers the last state, user's choice. Resetting to hidden is the safer default. Three implementation details that matter more than they sound, from having built this myself: Mask on first render, do not hide after render. If values are rendered and then masked client-side, they flash visible for a moment on every page load, which defeats the point precisely when someone is looking over your shoulder. Preserve layout width. If the mask is a different width from the number, the whole page reflows every time you reveal or hide, which looks broken and makes the toggle feel unusable. Rendering the real value in an invisible sizing element and cross-fading the mask over it keeps the layout perfectly still. Handle keyboard and screen readers. Hover-only peeking is unusable without a mouse, so the same reveal should trigger on focus, and the masked element should expose something like "hidden value" rather than reading the digits aloud. A secondary benefit worth mentioning: it makes screenshots and screen sharing safe. If I ever need to send your support team a screenshot of a bug, or share my screen on a call, privacy mode means I can do that without redacting anything by hand. I have implemented exactly this in my own finance dashboard, including the masked-first render and the zero-layout-shift approach, and it works well in practice.

HxC about 1 month ago

2

Show active sessions and allow remote sign-out

Your profile docs cover password changes and 2FA enrollment, which is good, but I could not find a way to see which devices are currently signed in or to end a session remotely. For an app holding a full financial history, reviewing and revoking sessions is a standard control, and it matters most in exactly the cases you want covered: a lost phone, a shared computer, or just wanting to confirm nothing unexpected is connected. A list showing device, approximate location and last active time, with a sign-out button per session, would cover it. 2FA protects the front door but does not help once a session already exists.

HxC about 1 month ago

1

Configurable fiscal year, starting with the South African tax year

FinWise currently supports South African banks via the Gathr platform, indicating a substantial user base within South Africa. It is important to note that South Africa's tax year operates from March 1st to the end of February, rather than aligning with the calendar year. The only available period control, "Budget Start Day," allows for the selection of a day from the 1st to the 28th of a month, but lacks a month selection option. Consequently, a March 1st fiscal year start cannot be accurately configured. This limitation results in annual financial views spanning two distinct tax years, rendering them unsuitable for tax reporting purposes. Implementing a configurable fiscal year start (encompassing both month and day) would also benefit users in the United Kingdom, where the fiscal year begins in April, and Australia, where it commences in July. This enhancement would align with our multi-regional strategic positioning. Furthermore, this functionality would naturally complement the existing request for "Annual Budgets." Additionally, there is an outstanding request for the tracking of Retirement Annuity and Tax-Free Savings Accounts (TFSA), which underscores the recurring theme of accommodating South African-specific tax structures.

HxC about 1 month ago

1

Transaction filters as URL params

Hey folks, love your app! I periodically open up Finwise to read through and verify the category for all my recent credit card transactions. Right now the easiest way to do that is to bookmark links to each Account view -> transactions page. I would love if Transaction page view filters persisted as GET params so they were linkable. That way I could bookmark a link that automatically filters to my two credit cards.

Giovanni Carvelli 14 days ago

1

Dynamic pay day selection

Hey team - really love your product!!! I joined yesterday and have already built out my full historical financial data analysis 😂 The ONLY thing I have noticed that I would like to request is the selection of dynamic dates for budgets. The easiest example is the last Friday of every month. That would be a huge unlock in helping people realise some months are 4 weeks and some are 5 weeks 😉 Other than that the product kicks ass 🤘

Liam Poole 15 days ago

1

Title: Wishlist and gift list

Things you want to buy currently have no home in FinWise. They end up in notes apps, screenshots, browser tabs etc. The same goes for gifts. Birthdays and holidays are predictable, often the largest irregular spend of the year, and there's nowhere to record who needs one, what to get them, or what you plan to spend. This belongs in a finance app specifically, because the app already knows what you can afford. A wishlist in a notes app can't tell you anything. A wishlist next to your budget can. Wishlist Item, estimated cost, optional link or photo Date added, so you can see how long you've wanted something. Six months of still wanting it is very different from six minutes Status: wanted → saving for → ready to buy → bought → no longer want Optionally link an item to a savings goal, so it can actually be funded Mark as bought by linking the transaction Gift list Recipient, occasion and date, with birthdays recurring annually A budget per person or per occasion Ideas captured throughout the year, not the week before Upcoming gift spend rolled into your forecast, so December stops being a surprise The wishlist is also a spending-control tool, not just a list. Writing something down and letting it sit is the most reliable defence against impulse buying, and "no longer want" as a status turns that into visible feedback about your own habits.

CJ 21 days ago

1

Track money owed — including what never touches your bank feed

Not every debt starts as a transaction. Cash lent to a friend, a favour someone owes you back, an invoice you've received but haven't paid, a shared cost before anyone settles up — none of these appear in a bank feed, but they're all real money that changes what you're actually worth. FinWise can only describe money that has already moved. So these either go untracked, or get faked with manual accounts and tag conventions that decay the moment you're inconsistent. Proposed: a standalone obligation record, created independently of any transaction, with: Direction — owed to me, or owed by me Counterparty — the person, business or institution on the other side, so "what does X owe me" is a single filter Status — open, submitted/claimed, partially settled, settled, written off Days outstanding — calculated automatically from the date it arose, and sortable, so the oldest items surface instead of quietly ageing out of mind Settlement linking — attach the transaction that clears it, in full or in part, so the repayment nets against the obligation instead of registering as income Balance impact — money owed to you counts as an asset, money you owe as a liability, both reflected in net worth Dashboard totals for outstanding in each direction

CJ 21 days ago

1