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

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

Linked accounts

When a bank link breaks, you can fix it, and you can ask for a statement without leaving the app.

01

The problem

Bank links stopped updating and nobody knew why. Reconnecting was confusing. Statements lived outside the app. Labeling payments and sending money depended on links that often broke.

02

The story

Everything else in FloatMerchant assumes the bank link works. When it does not, the product feels broken even if other features are fine. This work is about telling merchants the link is unhealthy, helping them fix it, and handing them a statement when they need proof.

03

What changed

The accounts page shows what is linked, when it last updated, and what to do next. You can reconnect or refresh. You can ask for a statement, see that it is processing, then get a PDF or email. Unlinking asks for confirmation so a mis-tap does not remove a bank.

04

How it was built

The focus was reliability merchants can understand: status, next step, and proof. Reconnect and statements were put where people already look for their banks, so recognition and transfers sit on links people can actually maintain.

05

Outcome

  • A broken link shows a clear next step.
  • Statements can start inside FloatMerchant.
  • Other money features sit on bank links that stay workable.