Troubleshooting Transactions 
=============================

#### Learn how to troubleshoot common Transactions issues including API error responses and incorrect data fields. 

#### API error responses 

If the problem you're encountering involves an API error message, see [Errors](https://plaid.com/docs/errors/index.html.md) for troubleshooting suggestions.

#### No transactions or cursor returned 

When calling [/transactions/sync](https://plaid.com/docs/api/products/transactions/index.html.md#transactionssync) , a response with no cursor or transactions data is returned.

##### Common causes 

*   This is expected behavior when the Item has recently been initialized with `transactions` and Plaid has not yet completed fetching of transactions data.

##### Troubleshooting steps 

#### Missing transactions 

##### Common causes 

*   The institution is experiencing an error.
    
*   Processing of the transactions has been delayed.
    
*   The Item is not in a healthy state.
    
*   The transaction is not available on the institution's online banking portal, or appears differently on the online banking portal.
    

##### Troubleshooting steps 

If the steps above do not resolve the issue, [file a ticket with Plaid support](https://dashboard.plaid.com/support/new/financial-institutions/missing-data/missing-transactions) .

#### Incorrect data fields 

In some cases, information about a merchant, such as its name or category, may be incorrect.

##### Troubleshooting steps 

If the issue is not resolved, or if the category information is incorrect, [file a ticket with Plaid support](https://dashboard.plaid.com/support/new/financial-institutions/faulty-data/faulty-transaction-data) indicating which fields are incorrect, the correct data, and the `transaction_id` of the affected transaction.

#### Limited transaction history is returned 

##### Common causes 

*   By default, Plaid will only return 90 days of transaction history. To request more transaction history, specify the `days_requested` field when initializing with Transactions. Note that this field will only take effect when Transactions is added to an Item for the first time; if you need more than 90 days of transactions history for an Item that has already been initialized with Transactions for 90 days of history, you will need to delete the Item and create a new one.
    
*   The user's institution may provide limited transaction history. For example, Capital One provides only 90 days of transaction history and does not provide pending transactions.
    

##### Troubleshooting steps 

#### Duplicate transactions are returned 

##### Common causes 

*   An end user linked the same bank account to your app multiple times, causing the same transaction data to appear across multiple Items.
    
*   The duplicate transaction data may be an accurate reflection of the end user's transaction activity (e.g. if the end user was double-charged).
    
*   If a transaction is updated, modified, or posted, it will appear as a separate transaction in transaction history. This is expected behavior and your app should have logic to reconcile the two versions of the transaction. For more details, see [Transactions states](https://plaid.com/docs/transactions/transactions-data/index.html.md) .
    
*   There may be an error with the data provided by the institution to Plaid or with Plaid's processing of this data.
    

##### Troubleshooting steps 

If the issue is not resolved, [file a ticket with Plaid support](https://dashboard.plaid.com/support/new/financial-institutions/faulty-data/faulty-transaction-data) indicating which transactions are duplicated, and the `transaction_id`s of the affected transaction.