---
title: "Discussion on \"How I Built a Fintech Front End from Scratch and What I’d Change Today\" | Hashnode"
description: "Discussion on \"How I Built a Fintech Front End from Scratch and What I’d Change Today\". A practical account of building a financial front end from an empty repository, while the product, API contracts and delivery process were still taking shape.\n\n\nConfidentiality note: I have anonymised"
url: "https://hashnode.com/posts/built-a-fintech-front-end-from-scratch/6aa4f7ca97838e2fe715be7f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I Built a Fintech Front End from Scratch and What I’d Change Today](https://gonzalosimon.hashnode.dev/built-a-fintech-front-end-from-scratch?utm_source=hashnode&utm_medium=feed)

A practical account of building a financial front end from an empty repository, while the product, API contracts and delivery process were still taking shape. Confidentiality note: I have anonymised

Sep 12 · 25 min read · gonzalosimon.hashnode.dev  
Updated Sep 14  
Read the article

-   [#nextjs](https://hashnode.com/tag/nextjs)
-   [#typescript](https://hashnode.com/tag/typescript)
-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#fintech](https://hashnode.com/tag/fintech)
-   [#front-end-development](https://hashnode.com/tag/front-end-development)

## Written by

[Gonzalo Aguilar](https://hashnode.com/@gonzalosimon)

@gonzalosimon · Cordoba, Argentina

  
[View profile](https://hashnode.com/@gonzalosimon)

Software Engineer

Full-stack engineer with 6+ years building scalable backend systems and web platforms. Specializes in database optimization, API architecture, and performance engineering with TypeScript, Python, and Node.js.

## Responses 1

Markdown supported · ⌘↵ to post

[Tarun Sharma](https://hashnode.com/@101beardo)

[Sep 12](https://hashnode.com/posts/built-a-fintech-front-end-from-scratch/6aa4f7ca97838e2fe715be7f/comment/6aa518cbe6859bf866b79eb7)

the discriminated-union transfer state is the right instinct, and the honest framing on near-real-time polling over pretending it's a stream is exactly the kind of clarity that avoids a whole class of confused bug reports later. one thing I'd add to the money-as-floating-point section: even after moving to minor-unit integers, currency conversion/display formatting still needs its own decimal library at the boundary, Intl.NumberFormat is fine for display but silently reintroduces float rounding if you feed it a computed value instead of a stored one.
