AgileWebs/pos-transactions-web
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
development
pos-transactions-web/docs/architecture/frontend-boundary.md
José René White Enciso 0dfa200ebf feat(pos-transactions-web): show payable payment progression
2026-03-31 19:08:40 -06:00

1.3 KiB
Raw Permalink Blame History

Frontend Boundary

  • This repository hosts a React edge application for a single BFF.
  • Frontend data access flows through src/api/* adapter modules.
  • The UI does not access DAL or internal services directly.
  • Route shell uses Ant Design layout/menu and keeps business views behind session checks.
  • Unauthenticated users are redirected to the central auth host OIDC start endpoint.

Runtime Base URLs

  • API_BASE_URL for business BFF calls.
  • THALOS_AUTH_BASE_URL for session login/refresh/logout/me.
  • THALOS_DEFAULT_RETURN_URL for safe callback fallback.
  • THALOS_DEFAULT_TENANT_ID for OIDC tenant context defaults.

Protected Workflow Endpoints

  • GET /api/pos/transactions/summary?contextId=...
  • GET /api/pos/transactions/{transactionId}?contextId=...
  • GET /api/pos/transactions/recent-payments?contextId=...
  • POST /api/pos/transactions/payments

UI Workflow Coverage

  • POS transaction summary lookup with open balance visibility
  • Transaction detail inspection for a selected payable check or transaction id
  • Recent payment activity review
  • Payment capture with retry-ready local session history and lifecycle-aware payment hints
  • Protected route shell for summary, payment capture, and session inspection
  • POS actions are presented as the final step after kitchen and floor service complete the restaurant order.