INVALID_CREDENTIALS
The data source indicated that the credentials provided were invalid.
http code 400
{
"error_category": "CONNECTION_ERROR",
"error_code": "INVALID_CREDENTIALS",
"error_message": "The provided credentials were not correct",
"display_message": "The provided credentials were not correct. Please try again."
}
Common causes
- The user entered incorrect credentials at their selected institution.
- Extra spaces, capitalization, and punctuation errors are common causes of
INVALID_CREDENTIALS
. - The data source requires special configuration steps before the user can link their account with Deck.
- The user selected the wrong institution.
- Deck supports providers that have multiple login portals for the various products they offer, and it is common for users to confuse a different selection for the one which their credentials would actually be accepted.
Troubleshooting steps
- Prompt your user to retry entering their credentials. Note: The Provider may lock a user out of their account after 3-5 repeated attempts, resulting in an
ITEM_LOCKED
error. - Confirm that the credentials being entered are correct by asking the user to test logging in to their financial institution website using the same set of credentials.
- The user should check their financial institution website for special settings to allow access for third-party apps, such as a "third party application password" or "allow third party access" setting.
- Verify that the user is selecting the correct institution in Link’s Source Select view.
If the credentials are confirmed to be legitimate, and a user still cannot authenticate, please submit an 'Invalid credentials errors' Support ticket with the following identifiers: access_token
, source_id
and link_token_id
.
Updated 3 months ago