Invalid Input Errors

In the Development or Production environments, use Link to create the Item. In Sandbox, use /sandbox/public_token/create

Have your user attempt to enter the micro-deposit verification input again.

If your user enters an incorrect micro-deposit verification input three times, the Item will be permanently locked. In this case, you must restart the Link flow from the beginning and have the user re-link their account.

Make sure you are not using a token created in one environment in a different environment (for example, using a Sandbox token in the Development environment).

Ensure that the client_id, secret, and access_token are all associated with the same Plaid developer account.

Verify that your integration is passing in correctly formatted and valid account_id(s)

Verify the Item's currently active accounts and their account_id(s).

The user may have revoked access to the account. If this is the case, it is a security best practice to give the user a choice between restoring their account and having your app delete all data for that account. If your user wants to restore access to the account, you can put them through update mode, which will give them the option to grant access to the account again. Note that doing so will result in an account with a new and different account_id, which can be obtained by calling /accounts/get.

Verify that after completing update mode, your implementation checks for the current account_id information associated with the Item, instead of re-using the pre-update mode account_id(s). Updated account_id data can be found in the onSuccess Link event, or by calling certain endpoints, such as /accounts/get.

Verify that the account_id was not changed or removed from the API.

Find your API keys in the Dashboard.

Make sure you are using the secret that corresponds to the environment you are using (Sandbox, Development, or Production).

Make sure you are not using a token created in one environment in a different environment (for example, using a Sandbox token in the Development environment).

Visit the Plaid Dashboard to verify that you are enabled for the environment you are using.

Generate a new audit_copy_token via /asset_report/audit_copy/create.

Check the institution_id to ensure it is valid.

Update your Link customization to enable Account Select v2 or use a Link customization with Account Select v2 enabled.

Confirm that the link_token is from the correct environment.

Generate a new link_token for initializing Link with and re-launch Link.

If you are testing in Sandbox, make sure that your processor_token was created using the Sandbox-specific endpoint /sandbox/processor_token/create instead of /processor_token/create. Likewise, if testing in Development or Production, make sure that your processor_token was created using /processor_token/create rather than /sandbox/processor_token/create.

Make sure you are not using a processor_token created in one environment in a different environment (for example, using a Sandbox token in the Development environment).

If you are using a partner integration, check the Dashboard Integrations page to make sure it is enabled.

If you are using a partner integration, update the products parameter in the /link/token/create call to remove any products other than auth or identity, and make sure that you are not using endpoints for products other than Balance, Auth, or Identity with this Item.

Contact Sales or submit a product request form to gain access to this product for your account.

Either re-initiate the Link flow without the restricted product, or contact your Plaid Account Manager or file a Support request to disable the pre-authenticated flow for your integration.

If you have migrated to Data Transparency Messaging, check that the products or additional_consented_products parameters passed to /link/token/create include the product you are requesting. You can fix any Items with missing consent by using update mode.

Make sure you are not using a token created in one environment in a different environment (for example, using a Sandbox token in the Development environment).

Ensure that the client_id, secret, and public_token are all associated with the same Plaid developer account.

The public_token expires after 30 minutes. If your public_token has expired, send your user to the Link flow to generate a new public_token.

See the returned error_message, which contains information from Stripe regarding why the account was deemed invalid.

Check that the user token is entered correctly.

Make a call to /user/create to create a user token for the given user ID.

Ensure that the key_id argument provided to /webhook_verification_key/get is in fact the kid extracted from the JWT headers. See webhook verification for detailed instructions.

Ensure that the webhook is being verified against the same environment as it originated from.

If using the pre-authenticated returning user flow, make sure to provide all the products you will be using in the products array at Link initialization.

If you need to use a product that is not supported by the pre-authenticated returning user flow, e.g. auth, contact your Plaid Account Manager to disable the pre-authenticated returning user flow for your integration.

Re-initiate the Link flow and have your user attempt to verify their account again.

Visit the Plaid Dashboard to verify that you are enabled for the environment you are using.

Make sure that your code is not calling deprecated endpoints. Actively supported endpoints are listed in the API reference.

Find your API keys in the Dashboard.

Contact Sales to gain access.

Delete the item using /item/remove and prompt your user to re-enter the Link flow to re-authorize access to their data. Note that if the user re-authorizes access, a new Item will be created, and the old Item will not be re-activated.

If applicable, direct your user to a fallback, manual flow for gathering account data.