cs-transacion-manage

Experience · Repository · Active

cs-transacion-manage

Transaction management experience with a dedicated NestJS BFF, React frontend, local shared contracts, platform-auth roles, platform-payments subscription tiers and dedicated PostgreSQL persistence.

• NestJS 11
• Prisma 7
• PostgreSQL
• React 19
• Vite
• Redux Toolkit
• Tailwind 4

Spec sheet

Area

Experience / CS Transaction Manage

Public host

http://transactions.cs.lvh.me:8080

Runtime shape

apps/api + apps/web + packages/shared

Backend port

3005

Frontend port

5179

Data store

Dedicated PostgreSQL

Responsibilities

• Own the transaction, relationship, counterparty, series, investment and agenda user experience.
• Expose a same-origin BFF that delegates login and session resolution to platform-auth-service.
• Calculate subscription-aware product capabilities from platform-auth roles and platform-payments plan status.
• Persist product state in transaction-postgres through Prisma.
• Keep frontend traffic same-origin and route all browser API calls through /api.
• Keep DTO and UI-facing types aligned through the local @casa-srl/shared package.

Interfaces and contract surface

• GET /api/health
• GET /api/auth/me
• POST /api/auth/register
• POST /api/auth/login
• GET /api/transactions
• GET /api/series
• GET /api/investments
• GET /api/agenda

Internal modules

Backend

cs transaction api

NestJS BFF for CS Transaction Manage, delegating auth/session/role flows to platform-auth-service and subscription status to platform-payments-service while owning onboarding, ledger, transaction, series, investment and agenda APIs.

Frontend

cs transaction web

React and Vite frontend for CS Transaction Manage, rendering the ledger workspace, onboarding, agenda, transactions, series and investments through same-origin APIs.

Package

cs transaction shared

Local shared package for CS Transaction Manage contracts and TypeScript types consumed by the BFF and frontend.

Consumers

• Internal users via transactions host

Dependencies and external touchpoints

• platform-auth-service
• platform-payments-service
• platform-local-stack
• platform-status-service

Notes

• The BFF uses platform-auth-service local credentials and the cs-transacion-manage product code while keeping ledger profiles local.
• ADMIN bypasses subscription limits; USER capabilities are derived from FREE, PRO or BUSINESS tiers.
• The local stack starts the shared package watcher, then API and web processes.

Source references

• cs-transacion-manage/package.json
• cs-transacion-manage/apps/api/package.json
• cs-transacion-manage/apps/web/package.json
• cs-transacion-manage/packages/shared/package.json

Accesso e subscription

Il BFF calcola l'accesso prodotto in un modulo access dedicato. Il ruolo arriva dalla membership di platform-auth-service; il tier subscription arriva da platform-payments-service tramite consumerTenantId, con fallback iniziale su subjectId quando manca il tenant.

ADMIN ha tutte le capability e bypassa i limiti subscription. Gli utenti USER ricevono capability per tier: FREE abilita workspace base e transazioni manuali, PRO aggiunge serie, investimenti, simulazione, pay-yourself-first e import/export, BUSINESS aggiunge condivisioni avanzate senza concedere privilegi amministrativi.

Le API negate rispondono 403 Forbidden; la UI usa access.capabilities solo per nascondere navigazione e azioni non disponibili.