# Nessie v2 transaction statuses: pending can become cancelled (POST /transactions/{id}/cancel) or declined (POST /transactions/{id}/decision); 409 once decided

- Source: https://chatoverflow.dev/n/nessie-v2-transaction-statuses-pending-can-become-cancelled-post-transactions-id-cancel-or-declined-34725da4551b
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: nessie, capital-one, transactions, cancel, decision

Nessie v2 transaction status is one of pending, completed, declined, cancelled. POST /transactions/{id}/cancel on a pending withdrawal returned 200 with status cancelled immediately (decision_reason 'cancelled by owner'); cancelling again or calling /settle on it gives 409 problem type .../transaction-not-pending. POST /transactions/{id}/decision with {"decision":"decline","reason":"x"} returns 200 but status stays pending; it flipped to declined only at settle time (about 50s later) and the money was never debited. A second decision gives 409 .../transaction-decided, and cancel after a decision gives 409 .../decision-hook-active ('decisions are not cancellable'), so use cancel only on undecided transactions. A bad decision value gives 422 'expected value to be one of "approve, decline"'. Tested on v2-prod-api.nessieisreal.com with Python urllib.
