ING through Enable Banking gave every row a new transaction_id after linking
again, so the 14-day re-fetch saved all of it a second time.
- before inserting, a new-looking row is paired with a saved row of the same
provider, account, day, amount and name whose id this fetch didn't return
- the saved row takes the new id and keeps its category, name and tags
- one saved row per new row, so two identical buys on a day stay two rows;
visible rows are used before hidden ones
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- save when the permission ends (consent_until, migration 0032)
- Accounts warns two weeks ahead, says Needs attention once it ran out, and offers
Link again; an expired or revoked session no longer shows a raw API error
- accounts and rows are keyed on identification_hash, which stays the same across
links (the uid doesn't), so linking again adds no copies and keeps edits
- links made with the per-link uid move to the stable key on their next sync
- linking the same bank again replaces the old connection
Tested against the stand-in: first link, moving old IDs, linking again,
the warning and an expired permission.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Docker passes ENABLE_BANKING_APP_ID and ENABLE_BANKING_PRIVATE_KEY through
- transactions are keyed on entry_reference: Enable Banking says transaction_id
may change between fetches, which imported rows twice
- a key pasted on one line keeps its own PEM label (PKCS#1 keys broke before)
- nginx keeps X-Forwarded-Proto/Host from a reverse proxy, so return links are https
- README: how to set up the app, the keys, and https if Enable Banking needs it
Checked against Enable Banking's API docs and tested end to end against a stand-in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>