Detect inactive accounts via the relevant Financial Connections webhook rather than assuming a previously linked account stays usable indefinitely
Confirm refresh eligibility first: refreshes are not allowed on accounts already marked inactive, so check status before calling the refresh endpoint
Create a new Financial Connections Session with relink_options referencing the existing account to drive the customer straight back to their institution
Pass the session's client_secret to the client SDK's collect method to complete the streamlined reauthentication flow
If the account was fully disconnected rather than just inactive, treat it as unrecoverable for data access and start a fresh linking session instead of a relink
Known gotchas
Disconnecting an account (versus it merely going inactive) permanently blocks both refresh and access to previously retrieved data for that account
Determining precisely when a relink (versus a fresh link) is required can depend on using a preview API version, so behavior may differ across API version pins
Relink flows differ depending on whether the account is used for payments/payouts versus data products, and each has its own configuration path
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?