Accessible loading states are product trust work in React fintech apps

A loading state looks small until the user is waiting for something important.

In ordinary software, a vague spinner is annoying. In fintech and open banking interfaces, it can create confusion at exactly the wrong moment: connecting an account, approving consent, fetching balances, confirming a payment, or recovering from a failed request.

That is why I do not see loading states as visual polish. I see them as part of the trust contract between the product and the user.

The problem with vague loading

A generic spinner often says only one thing: “wait”.

But users usually need more than that. They need to understand:

what action is in progress,

whether they can safely leave or retry,

whether pressing again may duplicate an action,

whether the system is waiting on a third party,

whether the state is still active or has silently failed.

In a fintech flow, those details are not minor.…