{"article":{"id":15255178925719,"url":"https://plaid.zendesk.com/api/v2/help_center/en-us/articles/15255178925719.json","html_url":"https://support.plaid.com/hc/en-us/articles/15255178925719-Why-has-the-account-id-of-an-account-changed","author_id":396033157154,"comments_disabled":true,"draft":false,"promoted":false,"position":4,"vote_sum":0,"vote_count":0,"section_id":16125190358807,"created_at":"2023-06-12T20:09:05Z","updated_at":"2026-06-01T01:59:32Z","name":"Why has the account_id of an account changed?","title":"Why has the account_id of an account changed?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-06-01T01:59:32Z","user_segment_id":null,"permission_group_id":1121774,"content_tag_ids":[],"label_names":[],"body":"<p>After an Item has been created, the related <code style=\"border:none;background:#f1f3f5;padding:1px 4px;border-radius:3px;font-size:0.9em;\">account_id</code> for each account should be static. However, there are some cases where the <code style=\"border:none;background:#f1f3f5;padding:1px 4px;border-radius:3px;font-size:0.9em;\">account_id</code> can change for an existing account. When we get updated data from a financial institution, information about the account can change, preventing us from reconciling the updated account data with the existing account data in our database. If this happens, the existing account is removed and a new one is created with a new <code style=\"border:none;background:#f1f3f5;padding:1px 4px;border-radius:3px;font-size:0.9em;\">account_id</code>. This can happen when the financial institution changes the way they provide account data, or a change to our integration causes the data we receive to be different. When this happens, we refer to it as \"account churn\".</p>\n<p>If this occurs, update the account data you have stored with a new call to the <a href=\"https://plaid.com/docs/api/accounts/#accountsget\"><code style=\"border:none;background:#f1f3f5;padding:1px 4px;border-radius:3px;font-size:0.9em;\">/accounts/get</code></a> endpoint. Additionally, we recommend regularly updating the account data you have stored for your users with a call to <code style=\"border:none;background:#f1f3f5;padding:1px 4px;border-radius:3px;font-size:0.9em;\">/accounts/get</code>. Regularly getting an updated account list will ensure you have the most up-to-date information on any new accounts, any that have closed, and even if accounts do churn it will ensure you don't have an interruption in data for the user.</p>","user_segment_ids":[]}}