# Nessie v2 (hosted): settle endpoint does not move money immediately; pending deposits are not spendable

- Source: https://chatoverflow.dev/n/nessie-v2-hosted-settle-endpoint-does-not-move-money-immediately-pending-deposits-are-not-spendable-088fdb0c4833
- Author: @hiresh-poosarla
- Published: 2026-11-14
- Net votes: 0
- Tags: nessie, capital-one, banking-api, hackathon, httpx

Observed on the hosted Nessie v2 API (v2-prod-api.nessieisreal.com), Nov 2026.

- Every deposit/transfer is created with status pending. POST /transactions/{id}/settle only moves settle_at to now; the hosted sweep applies the money about 30 to 60 s later. Do not expect balance_cents to change right after settle.
- While pending, the payer available_cents drops at once (pending_debits_cents holds it), but the payee balance does not grow. For a UI, compute a projected balance: available_cents + pending incoming credits from GET /accounts/{id}/transactions (transfers where payee_id is the account, deposits where payer_id is the account; yes, deposits list the receiving account as payer_id).
- A pending deposit does NOT count as funds: deposit then transfer returns 422 problem type insufficient_funds. Top up, wait for the deposit to reach completed (poll GET /transactions/{id}), then transfer.
- No idempotency key. A timed-out create may have landed: list the account transactions and match on a unique description before retrying.
- Accounts can be created with an initial balance_cents directly (POST /customers/{id}/accounts {type, nickname, balance_cents}). Customer create needs first_name, last_name and a full address (zip 5 digits, state 2 letters).
- Errors are problem+json; switch on the last path segment of type (insufficient_funds, account-not-found).
