# Data Connect Fix Experience
source: https://developer.mastercard.com/open-finance-us/documentation/experience-design-guide/connect-enhancements-and-features/recall-experience-connect-fix/index.md

**Data Connect Fix** is a feature within Mastercard Data Connect that enables end users to seamlessly restore access to accounts that are disconnected or "broken." When a connection issue occurs---often token revocation and/or expiration, due to password changes, multi-factor authentication updates, or other technical interruptions---partners can prompt end users to securely re-enter Data Connect to re-establish the link. Most accounts refresh automatically on a nightly basis, but occasional disruptions can occur.

**Benefits of Data Connect Fix for users:**

* **Faster Resolution:** Quickly repair broken connections without waiting for manual support intervention.
* **Improved continuity:** Minimize gaps in aggregated data by restoring access promptly.
* **Better User Experience:** Provide a secure, guided process to fix accounts, reducing confusion and support requests.

## When is Data Connect Fix used? {#when-is-data-connect-fix-used}

Data Connect Fix should be implemented whenever an account experiences an aggregation error that can be resolved by the end user. Specifically, when the account returns a ["fixable" error code](https://developer.mastercard.com/open-finance-us/documentation/products/manage/aggregation-status-codes/index.md#using-data-connect-fix) when using Data Connect Fix. These codes indicate issues, such as expired credentials or additional authentication requirements that the user can resolve by re-entering Data Connect.
Note: Connect Fix should not be used for errors outside of these fixable codes (for example, institution downtime or unsupported account types), as end-user action will not resolve these conditions.

**When integrating Data Connect Fix, partners should evaluate:**

* **Triggering criteria:** Determine which ["fixable" error codes](https://developer.mastercard.com/open-finance-us/documentation/products/manage/aggregation-status-codes/index.md#using-data-connect-fix) align with your product flow and when to prompt users through a recall experience.
* **User experience (UX) goals:** Provide proactive notifications (for example, through SMS, email, or in-app messaging) versus passive prompts within your interface.
* **Implementation model:** Decide how to integrate Connect Fix (for example, standalone fix experience versus integrated into existing Connect flows).

## How is Data Connect Fix enabled? {#how-is-data-connect-fix-enabled}

There are two primary ways to enable Data Connect Fix depending on whether you use **Mastercard Data Connect Full** or **Mastercard Data Connect Lite** and how much control you need over the user experience (UX).

##### Option 1: Embed in the standard Data Connect flow {#option-1-embed-in-the-standard-data-connect-flow}

For partners using Mastercard Data Connect Full, Data Connect Fix is enabled by default as part of the standard Data Connect experience. In this model, when an account encounters a ["fixable" error](https://developer.mastercard.com/open-finance-us/documentation/products/manage/aggregation-status-codes/index.md#using-data-connect-fix), users are automatically prompted to repair the connection during their normal Connect session. No additional development work is required.

|                                                                                                                     Pros                                                                                                                     |                                                                                  Considerations                                                                                  |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| * Requires no additional development work. * Simplifies implementation by leveraging built-in functionality within Mastercard Data Connect Full. * Provides a familiar and consistent experience for users already interacting with Connect. | * Users may need to complete 1--2 extra clicks to access and resolve broken accounts. * Limited flexibility to customize the Fix workflow beyond what Connect natively provides. |

##### Option 2: Use the Data Connect Fix endpoint {#option-2-use-the-data-connect-fix-endpoint}

Mastercard Data Connect Lite partners must use the [Generate Data Connect Fix URL endpoint](https://developer.mastercard.com/open-finance-us/documentation/api-reference/index.md) since the embedded Fix workflow is not available in Lite. Full partners may also choose this method if they need greater control over how and when users are prompted to fix broken accounts.

|                                                Pros                                                |                                                                                                                                                                      Considerations                                                                                                                                                                       |
|----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| * Directs users straight to the broken accounts offering a faster, more focused repair experience. | * Requires additional development effort to integrate with the Data Connect Fix API endpoint. * Partners must implement logic to identify ["fixable" error codes](https://developer.mastercard.com/open-finance-us/documentation/products/manage/aggregation-status-codes/index.md#using-data-connect-fix) and trigger the Fix flow only when applicable. |

##### Decision Tree: Which approach should you use? {#decision-tree-which-approach-should-you-use}

![Decision tree](https://static.developer.mastercard.com/content/open-finance-us/uploads/decision-tree.png)

## Data Connect Fix user experience flow {#data-connect-fix-user-experience-flow}

For the best viewing experience of app to app, click the **full screen mode** option or **zoom** using the controls located on the right.

## What causes an account connection to break? {#what-causes-an-account-connection-to-break}

Broken account connections occur when Mastercard Data Connect can no longer successfully aggregate data from a financial institution. These disruptions typically map to "fixable" error codes (as detailed in the Aggregation Status Codes documentation) and can usually be resolved through user action through Connect Fix. Understanding these causes enables partners to design proactive notifications, minimize user friction, and improve overall data continuity.

**There are four main reasons for an account connection to break:**

1. **Authentication and credential-related issues**
   * **Credential changes**   
     Users who update their login credentials (for example, password or username) at their financial institution must re-enter Connect to restore access.
   * **MFA expirations**   
     Multi-Factor Authentication (MFA) prompts can expire if not completed in time, leading to a failed connection that requires re-authentication.
   * **MFA-enforced challenges**   
     Some institutions enforce MFA at scheduled intervals (for example, every 30 or 90 days) or trigger MFA dynamically, based on risk (for example, logging in from a new device or location). If the user does not complete these challenges, the connection breaks.
   * **MFA high-risk actions**   
     MFA may be required for specific high-risk actions (such as initiating large transfers or modifying sensitive account details), and failure to complete such actions disrupts access.
2. **Session and token expiry issues**
   * **OAuth token expiration**   
     OAuth tokens provided by financial institutions have defined lifespans. When these tokens expire, users must re-authenticate to regain access and re-authorize data sharing.
3. **Account and consent change issues**
   * **Consent revocation**   
     Users can withdraw consent at any time through their financial institution, which immediately terminates aggregator access until renewed by the user.
4. **Institution-level changes and technical disruption issues**
   * **Financial Institution (FI) API or system Updates**   
     Financial institutions may deploy updates (for example, API schema changes, new security protocols) that temporarily disrupt aggregator connectivity until integrations are updated.
   * **FI connectivity losses or downtime**   
     Outages or temporary connectivity failures at the financial institution can also cause account aggregation to fail.
   * **Fixable versus non-fixable causes**   
     Not every broken connection can be resolved using Connect Fix.
     * **Typically fixable:** Credential updates, expired MFA or token challenges, and periodic or risk-based MFA requirements
     * **Typically non-fixable:** Institution downtime or outages, permanent account closures, and consent revocations (until renewed by the user)

<br />

Refer to the [Aggregation Status Codes](https://developer.mastercard.com/open-finance-us/documentation/products/manage/aggregation-status-codes/index.md) page to confirm which specific error codes qualify for Connect Fix.

### Best Practice {#best-practice}

* Proactively alert users when their connection breaks and provide a **direct entry point to Connect Fix** (for example, through in-app notification or email). Sending an alert reduces confusion, shortens resolution time, and improves customer satisfaction by guiding them to the fixable issue. See the Figma file of the [Data Connect Fix user experience flow](https://developer.mastercard.com/open-finance-us/documentation/experience-design-guide/connect-enhancements-and-features/recall-experience-connect-fix/index.md#data-connect-fix-user-experience-flow) above for greater detail.

* Developers and product owners should review the Connect Fix technical documentation, which provides detailed guidance on the web hooks and APIs required for implementation.

Tip: If you have any questions or need assistance with the customer experience or development, please [contact us](https://developer.mastercard.com/open-finance-us/documentation/support/index.md).

<br />

Next: [Accessibility Guidelines](https://developer.mastercard.com/open-finance-us/documentation/experience-design-guide/accessibility-guidelines/index.md)