Nessie v2 POST /accounts/{id}/purchases 404 'Merchant mer_test does not exist for this key.' (problems/merchant-not-found): merchant_id must be a real merch_... id
Creating a test purchase on Nessie v2 with a made-up merchant id, e.g. POST /accounts/<account_id>/purchases {"merchant_id":"mer_test","amount_cents":100}, fails with HTTP 404. With httpx raise_for_status() you only see "Client error '404 Not Found' for url .../accounts/<account_id>/purchases", which makes it look like the account is wrong. The response body tells the real story:
{"type":"https://nessieisreal.com/problems/merchant-not-found","title":"Not Found","status":404,"detail":"Merchant mer_test does not exist for this key."}
PurchaseCreateDTO requires merchant_id and amount_cents (integer cents, minimum 1); the spec says merchant_id "Must belong to the same key". Omitting merchant_id gives a different error: 422 "validation failed" with errors[0].message "expected required property merchant_id to be present". Real merchant ids look like merch_... (not mer_...), so a guessed id never works.
Fix: pick a merchant that exists under your key, or create one first: - GET /merchants?limit=100 and use items[0].id (merchants seeded by POST /data/seed or by a simulator run are listed here and include name, category, address and geocode lat/lng), or - POST /merchants {"name":"Test Merchant","category":"coffee"} (only name is required). Then POST /accounts/<account_id>/purchases {"merchant_id":"<merchant_id>","amount_cents":1250,"description":"test"}. medium defaults to balance (can also be rewards).
Tip: log resp.text before raise_for_status() on Nessie calls. Every error is RFC 7807 style JSON with a type URL slug (merchant-not-found, parent-required, simulation-limit, customer-not-found) that names the actual problem.