Files
nick-doc/Issues/ISSUE-121-frontend-transferfunds-and-createpayment-post-to-same-endpoint.md
Siavash Sameni dceaf82934 audit: 2026-05-30 full-codebase audit — report, issues, docs, runbooks
Full-codebase-audit 2026-05-30 outputs:
- Audit report: 09 - Audits/Full Codebase Audit - 2026-05-30.md
- 81 issue files ISSUE-055..135 (decisions + 1 skipped no-brainer).
- Scanner docs from scratch (was zero): architecture, data model, API ref, payment
  flow, operations runbook + repo README.
- Doc-sync updates across API reference, data models, flows, design system.
- Secret Rotation Runbook (08 - Operations) for the exposed credentials.
- Reusable workflow guide (07 - Development) + .claude/workflows/full-codebase-audit.js.

Issues remain status:open intentionally — the code fixes are uncommitted-then-committed
working-tree changes per repo and aren't "resolved" until merged/deployed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 18:48:04 +04:00

1.1 KiB

issue, title, severity, domain, labels, status, created, source
issue title severity domain labels status created source
121 Frontend: transferFunds and createPayment POST to the same endpoint low Payment
bug
frontend
open 2026-05-30 Full Codebase Audit 2026-05-30

Frontend: transferFunds and createPayment POST to the same endpoint

Severity: low Domain: Payment Labels: bug, frontend

Description

src/actions/payment.ts:186transferFunds and createPayment both POST to the same backend endpoint. It is unclear whether this is intentional (payload-shape disambiguation on the backend) or an error where transferFunds should use a dedicated route.

Options

  1. Give transferFunds a dedicated backend route + frontend endpoint constant.
  2. Keep shared endpoint but document the backend disambiguation contract.
  3. Merge the two functions if they are truly the same operation.

Recommendation

Confirm backend routing intent; if distinct operations, introduce a dedicated endpoint.

Affected Files

  • frontend/src/actions/payment.ts:186

References