Bank connections
Connecting an account through finAPI or Plaid, what arrives, and the re-authorisation banks demand every few months.
A connected account keeps its own balance and transactions current. Add one from the assets view: pick your bank, authorise with the provider, and choose which of its accounts to bring in.
The two providers
Walletguide uses finAPI and Plaid. Which one handles a given bank depends on the bank and its country; the institution search picks for you, so it is not usually a choice you make.
Your credentials go to the provider, never to Walletguide. What comes back is a token that reads accounts and transactions, and nothing else.
What arrives
Balances, and transactions with their date, amount and the bank's own description. That description is raw and rarely a clean name, which is what merchants are for.
Transactions can appear as pending and settle later. A pending row can change amount or vanish, which is normal and not a bug.
Refreshing
Connected accounts refresh on a schedule, and you can trigger one. A refresh runs as a background task, so a slow bank does not block the app; the notifications view records how it went.
Re-authorisation
The part worth knowing about. European banking rules make consent expire, often every 90 days, and an expired connection stops importing. It does not announce itself in the numbers — a report simply goes quietly stale.
You get a notification when a connection needs re-authorising, and the asset shows it. Re-authorising takes the same flow as connecting.
Removing one
Disconnecting stops the import and leaves the history in place. If you also want the transactions gone, removing an asset's history before a date is a separate operation, with a preview, because it does not come back.