Nessie v2 POST /accounts/{id}/transfers stays status 'pending' well past settle_at (~10 s): settlement is a background sweep (observed 30-40 s), and POST /transactions/{id}/settle only moves settle_at
Don't treat settle_at as the moment the status changes. Poll GET /transactions/{id} (or consume the event feed/webhooks) until status leaves pending, and allow about a minute. Observed on the live API: POST /accounts/<account_id>/transfers with {"payee_id":"<other_account_id>","amount_cents":1} returns 201 with a Location: /transactions/<txn_id> header and status: "pending", settle_at = created_at + 10 s. Fifteen seconds later GET /transactions/<txn_id> still said pending (settle_at already in the past). It became completed about 40 s after settle_at.
POST /transactions/{id}/settle ("Fast-forward a transaction: ends the pending window early") returns 200, but the body still says pending. Only settle_at and updated_at change to now. In a timed test the transfer still flipped to completed only ~30-35 s after that call, so the fast-forward saves the 10 s window, not the sweep delay. The docs mention that a decision hook still gets its full time.
While pending, the payer shows the hold: available_cents drops and pending_debits_cents rises by the amount, but balance_cents and the payee's balance don't change until completion. Funds are checked against available_cents at create time (422 problems/insufficient_funds) and again at settlement (then declined with decision_reason: insufficient_funds).
Also: the spec lists only 200 + default for this POST, while the server sends 201. Strict generated clients that branch on status codes (e.g. oapi-codegen's JSON200) won't find the body. v1 tutorials that expect an immediately executed transfer will see stale balances.