Web application
Blanco Finanças
A client portal for tracking savings plans and payments, with an admin area for managing plans and cash flow.

INSIDE THE APPLICATION
From clients to administrators
Real screenshots using test accounts, with identifying details hidden. Select an image to view it at full size.
Savings and goals
Installments and payments
Administrative overview
Cash flow
Plan management
Reports Two workflows in one application
Blanco Finanças clients need to check their savings plan balances, see upcoming installments and track payments. Administrators need a different view: clients, the plan catalog, incoming and outgoing funds, and pending withdrawals. I built both areas around a shared API, with separate permissions for each role.
What I built
My work covers the Nuxt frontend and FastAPI backend, including financial rules and integrations. The client portal shows plan progress, installments and payment history, with access to withdrawals.
When signing up for a plan, clients see a recommendation and a cost breakdown before activating it through Pix, Brazil's instant payment system. The backend integrates with Mercado Pago to track transaction states and receive payment confirmations.
Administrators can review key figures, filter transactions by date and category, manage the plan catalog and access reports on clients, transactions, cash flow and returns.
Application structure
The frontend uses Nuxt, Vue and TypeScript with Nuxt UI components. Pages handle navigation, while composables centralize API access for the client and admin screens.
FastAPI handles incoming requests, and application services coordinate use cases. Domain entities and services contain the financial rules, separate from adapters for external services. Data is stored in PostgreSQL through asynchronous SQLAlchemy, with Alembic managing migrations.
Technical decisions
- Monetary calculations: I use integer cents and
Decimalin the backend, with rounding defined in the monetary value object. This makes the representation and rounding of amounts explicit in the financial rules. - API permissions: authentication uses JWT, and backend operations check access by role. Client and admin access is enforced beyond the screens each user can see.
- Payment confirmations: the backend tracks transaction states and handles Pix confirmations idempotently, so a repeated confirmation does not apply the same transaction again.
- Integration boundaries: adapters handle Mercado Pago, Brazil's Central Bank, email delivery and report exports, keeping those details out of the domain rules.
What the application supports
Clients can track their plans and payments while administrators review transactions and manage plans within the same system. Both areas are implemented and shown in the screenshots on this page.
In operation, the application served more than 100 users, with three administrators working at the same time. Bringing these workflows together reduced spreadsheet work by around 30 hours per week and allowed the operation to grow.
The screenshots were taken from a local instance using test accounts and existing transactions. Identifying details have been hidden.
Technologies
Nuxt · Vue · TypeScript · Nuxt UI · FastAPI · Python · PostgreSQL · SQLAlchemy · Alembic