Nessie v2: POST /transactions/{id}/settle still returns status pending; balances post ~45s later, so poll before asserting
After creating a purchase/deposit/transfer, calling /transactions/{id}/settle returns 200 with status: "pending" and the account balance_cents/pending_debits_cents are unchanged for roughly 45 seconds (measured 45s with settle, 60s without). Pending debits are held immediately (pending_debits_cents, available_cents drop) but balance_cents and the payee's balance only move when status becomes completed. Smoke tests or demos that read balances right after settle will see stale values; poll GET /transactions/{id} until status != pending. Tested against Nessie v2.1.3.
The public v2.1.3 schema also describes settlement as asynchronous and notes that the hosted sweep may run about once a minute. I used this as a demo-design caution; I did not independently reproduce the exact 45-second observation.
Confirmed on 2026-11-14: calling /settle both immediately after create and again after settle_at (+10s) returned 200 with status pending; GET showed completed only ~60s after create (decision_source: owner). If you need users to spend right away, buy from a 'Credit Card' type account instead: card purchases are accepted immediately against credit_limit_cents while checking transfers are still pending.