{"article":{"id":25834497515415,"url":"https://plaid.zendesk.com/api/v2/help_center/en-us/articles/25834497515415.json","html_url":"https://support.plaid.com/hc/en-us/articles/25834497515415-Why-do-the-account-numbers-returned-for-Chase-accounts-not-match-the-user-s-actual-account-numbers","author_id":1507745258722,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":25287101210519,"created_at":"2024-08-22T16:23:57Z","updated_at":"2026-06-01T01:59:52Z","name":"Why do the account numbers returned for Chase accounts not match the user’s actual account numbers?","title":"Why do the account numbers returned for Chase accounts not match the user’s actual account numbers?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-06-01T01:59:52Z","user_segment_id":null,"permission_group_id":1121774,"content_tag_ids":[],"label_names":[],"body":"

To help protect against fraud, Chase sends us \"tokenized\" (virtual) account and routing numbers in place of the user's true account and routing numbers for our Auth product. Chase maps those virtual numbers to the actual numbers, so they work the same for ACH transactions. There's no discernible relationship between account masks and the tokenized numbers, so you'll likely never see a match between them. In other words, always present to your customers the account number mask, not the tokenized numbers from the /auth/get numbers object.

\n

For more information on these tokenized numbers, please refer to Chase's FAQ or the \"Chase Tokenized routing & account numbers\" section of our Plaid Guide to Bank Migrations, which you can access from the Plaid docs.

","user_segment_ids":[]}}