Skip to main content

​
Overview

Bank connection errors occur when a user is actively attempting to connect a financial institution for a banking verification. To monitor for bank connection errors:
  1. Subscribe to the verifications.updated webhook and set include_resource = true so the webhook payload contains the full verification object in data.resource.
  2. When you receive the verifications.updated webhook or are encountering bank connection issues, check the verification object’s status. If the status.state value is PAUSED, check the errors array in the status object.
  3. Proceed to the troubleshooting steps below for the bank connection error that matches the code value.

​
Bank connection errors

​
account_closed

The selected account could not be found or is no longer available at the banking institution.

​
account_not_found

The selected account could not be found or is no longer available at the banking institution.

​
generic_error

A connection error occurred while trying to verify the account.

​
institution_not_supported

The selected banking institution does not currently support connections.

​
invalid_credentials

The borrower provided invalid banking login credentials.

​
mfa_issue_encountered

A multi-factor authentication or security verification step was not completed successfully.

​
one_time_passcode_issue

There is a temporary issue preventing a successful connection to the borrower’s banking institution right now.

​
report_generation_failed

We could not generate the requested banking report.

​
temporary_connection_issue

There is a temporary issue preventing a successful connection to the borrower’s banking institution right now.

​
token_invalid_or_expired

The borrower needs to reconnect their account to restore access and complete verification.

​
user_action_required_at_institution

The borrower must sign in directly at their banking institution and complete an account action before reconnecting.