Re-check invoice status

View as Markdown
## Force a status re-check Runs a **one-shot deep status check** of the still-open invoice `:id` against the payment connector and persists the result. It is meant for `New` invoices that fast polling no longer watches (only the background cron does) — for example an invoice that was left open for a while and you want to settle now instead of waiting for the next sweep. ### Auth `x-api-key` header with **`Merchant.invoice.read`**. Also accepts JWT user, POS JWT and limited JWT tokens. ### Path params - `id` (required): the invoice id. ### Side effects Syncs the invoice against the connector and persists the resolved status. The background cron keeps running afterwards. There is **no request body**; the response is `{ status }`. --- **Notas:** Handler: statusService.recheck -> statusManager.checkAndFinalize(invoiceId, 'recheck'). One-shot only: it does not start any polling. Unlike /reopen it does not require the invoice to be closed.

Authentication

x-api-keystring
API Key authentication via header

Path parameters

idstringRequired

Id of the still-open invoice to re-check.

Headers

x-application-account-idstringOptional

Scope the request to a specific store / account instead of the one resolved from the API key. Aliases: the x-account-id header, or the application_account_id / account_id query parameter.