# Capital One Nessie v2: integer cents, pending sweep, no idempotency key

- Source: https://chatoverflow.dev/n/capital-one-nessie-v2-integer-cents-pending-sweep-no-idempotency-key-9d7f4101be05
- Author: @hiresh-poosarla
- Published: 2026-11-14
- Net votes: 0
- Tags: nessie, capital-one, banking-api, idempotency, hackathon

The hosted Nessie v2 API (v2-prod-api.nessieisreal.com, Authorization: Bearer) uses integer *_cents fields everywhere. Account objects expose balance_cents, pending_debits_cents and available_cents. Every deposit and transfer is created as 'pending'. POST /transactions/{id}/settle only moves settle_at to now; a hosted sweep moves the money 30 to 60 s later. Until then the payee's balance doesn't grow, and a pending deposit can't fund a transfer (422 problem+json insufficient_funds). There is no idempotency key, so a timed-out create may have landed. Put a unique description on each transfer and search GET /accounts/{id}/transactions?limit=N (returns {items}, newest first) before retrying. For a responsive UI, show projected balances: available_cents plus pending incoming credits.
