Some users report that re-subscribing to Direct Access to force a token refresh, or simply exporting transactions via QFX from your bank and importing them manually, is the only way to get around the broken server-side connections.
As Banktivity 7 is outdated and likely won't receive further patching, the long-term solution mentioned in community discussions is upgrading to the modern version, which uses a new, more reliable connection system. To make sure this post is perfectly tailored, let me know: Banktivity 7.5.3 fix
IGG confirmed that v7 is not fully supported on newer macOS versions like Big Sur and later, meaning direct connection fixes are unlikely to come from them, as they have moved on to Banktivity 8+ . Option 2: Social Media Post (Quick Tip) Some users report that re-subscribing to Direct Access
is specifically causing the issue? (e.g., Chase, Vanguard, etc.) Option 2: Social Media Post (Quick Tip) is
Enter your email to get our special. Gift straight to your inbox.