---
issue: 087
title: "Frontend: getPaymentStatus and checkPaymentStatus hit different endpoints"
severity: medium
domain: Payment
labels: [bug, frontend]
status: open
created: 2026-05-30
source: Full Codebase Audit 2026-05-30
---

# Frontend: getPaymentStatus and checkPaymentStatus hit different endpoints

**Severity:** medium
**Domain:** Payment
**Labels:** bug, frontend

## Description

`src/actions/payment.ts:62` has two functions — `getPaymentStatus` and `checkPaymentStatus` — that appear to serve the same purpose but call different endpoints (`/payment/:id/status` vs `/payment/payments/:id/status`). Only one of these can be the correct backend path.

## Options

1. Point `getPaymentStatus` at the registry-defined `/payment/:id/status` and deduplicate with `checkPaymentStatus`.
2. Add `/payment/payments/:id/status` to the endpoints registry if backend truly serves it.
3. Remove the redundant `getPaymentStatus` and migrate callers to `checkPaymentStatus`.

## Recommendation

Verify the real backend route, then collapse to a single function using the registry path. Could break callers, so verify before removing.

## Affected Files

- `frontend/src/actions/payment.ts:62`

## References

- [Full Codebase Audit 2026-05-30](../09%20-%20Audits/Full%20Codebase%20Audit%20-%202026-05-30.md) — DEC-16