Relink data access to a Financial Connections account with your user’s permissionPublic preview
Learn how to reestablish data access on inactive accounts with your user’s permission.
Your end user’s previously linked Financial Connections account might become inactive for a variety of reasons, including:
- The OAuth token provided to Stripe by their financial institution expires after a set period of time or because of inactivity.
- The financial institution has changed their multi-factor authentication requirements.
- The account becomes locked by their financial institution due to suspicious activity.
- They close their account at their financial institution.
- They change their username or password.
- They revoke access to sharing data with you or Stripe.
New account data isn’t accessible on inactive accounts. In rare cases, new account data is permanently inaccessible–for example, when an end user closes the account at their financial institution. For all other cases, they must re-authenticate to consent to sharing new account data with you.
The Financial Connections API allows you to repair the data connection of previously linked Financial Connections accounts (with your user’s permission) with a streamlined authentication flow that directs users straight to the institution of their previously linked account.
To know when a user must relink an account, you must use a preview API Version such as 2026-01-28. in all of your requests and webhook endpoints as indicated in the code snippets below.
Understand when an account becomes inactiveServer-side
You’re notified when a previously linked Financial Connections account becomes inactive with the financial_ webhook. If the account’s authorization is inactive, then the inactive subhash on the status_ hash on the Authorization object shows a relink_ action if it’s possible to relink an inactive authorization. For example, you might have a webhook handler like the one below to process webhook events.
Additionally, you can retrieve the status of an account by retrieving the account using the account ID.
curl https://api.stripe.com/v1/financial_connections/accounts/:id \ -u: \ -X "GET" \ -H "Stripe-Version: 2026-01-28.preview"sk_test_BQokikJOvBiI2HlWgH4olfQ2
{ "id": "fca_1LDYuMGxLVUXRs6HW0lrat9T", "object": "financial_connections.account", //..., "authorization": "fcauth_1LDYuMGxLVUXRs6HW0lrat9T", "status": "inactive" }
You can then retrieve the authorization of the account using the authorization ID.
curl https://api.stripe.com/v1/financial_connections/authorizations/:id \ -u: \ -X "GET" \ -H "Stripe-Version: 2026-01-28.preview"sk_test_BQokikJOvBiI2HlWgH4olfQ2
{ "id": "fcauth_1LDYuMGxLVUXRs6HW0lrat9T", "object": "financial_connections.authorization", //..., "status": "inactive", "status_details": { "inactive": { "action": "relink_required" } } }
The authorization. is none when an inactive account can’t be relinked for data access. In this case, redirect the end user to the usual authentication flow to select an institution and connect an account from scratch.
{ "id": "fcauth_1LDYuMGxLVUXRs6HW0lrat9T", "object": "financial_connections.authorization", //..., "status": "inactive", "status_details": { "inactive": { "action": "none" } } }
In some cases, the Authorization of an account might be active, but the account itself is inactive. This might happen, for instance, if the account was closed at the institution. In these cases, the inactive account can’t be relinked for data access. Likewise in this case, redirect the end user to the usual authentication flow to select an institution and connect an account from scratch.
Retrieve the authorization to relink from an inactive Financial Connections accountServer-side
To reestablish data access on an inactive account, retrieve the ID of the account’s authorization from the account object.
{ "id": "fca_1LDYuMGxLVUXRs6HW0lrat9T", "object": "financial_connections.account", //..., "authorization": "fcauth_1LDYuMGxLVUXRs6HW0lrat9T", "status": "inactive" }
You have two options to repair data access on a Financial Connections account, which depend on whether you want to repair an account previously linked to accept ACH Direct Debit payments with Stripe, or some other purpose.
Before you can regain data access from a user’s bank account with Financial Connections, your user must re-authenticate their account with the authentication flow. They begin the authentication flow when they want to relink their account to your site or application. Insert a button or link on your site or in your application, which allows a user to re-link their account—for example, your button might say “Re-link your bank account”.
When they see the authentication flow, your end user is prompted to authenticate access to their account at the relevant financial institution. Unlike the authentication flow where your user first links a new account, your end user won’t need to choose their financial institution from the bank picker.
Retrieve data on a Financial Connections accountServer-side
After your user has successfully completed the authentication flow, access or refresh the account data you specified in the permissions parameter of the Financial Connections Session.
To protect the privacy of your user’s data, account data accessible to you is limited to the data you specified in the permissions parameter.
Follow the guides for balances, ownership and transactions to start retrieving account data.