# Transactions errors
Read about the error response format and error codes that can occur during the SDK flow.
## Error response
The Tink journey may lead to an error that can’t be resolved in that session. When this happens, Tink displays an error screen with a user-friendly message and returns the error details for you to process. To opt out of Tink’s out-of-the-box error screens and use your own error screens instead, contact [Tink Support](/resources/support.md).
| KEY | AVAILABILITY | DESCRIPTION |
| -------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `error` | Always | Describes the category of the error. See [Error statuses](#error-statuses). |
| `error_reason` | Always | Describes the cause of the error. See the error reasons under each [error status](#error-statuses). |
| `message` | Always | A localized user-facing error message that can be presented directly to your user. |
| `tracking_id` | Always | Tink's internal identifier for this specific error instance. When contacting Tink about an error, include the `tracking_id` value to help streamline troubleshooting. |
| `credentials` | If credentials were created | The identifier of the credentials object. |
| `error_type` | If `error=AUTHENTICATION_ERROR` | Describes the type of authentication error that has occurred. For details, see [Provider Consent errors](/resources/transactions/provider-consent-errors.md). |
| `provider_name` | If a provider was selected | The name of the selected bank connection. |
| `payment_request_id` | If using Payment Initiation | The identifier of the payment request. |
| `state` | If provided in the request URL | The state value provided when starting the journey. |
>When contacting Tink about an error, include the `tracking_id` value to help streamline troubleshooting.
__Example error responses__
``` bash
#BAD_REQUEST response
example.com/callback?
error=BAD_REQUEST&
error_reason=INVALID_PARAMETER_CLIENT_ID&
message=We%E2%80%99re%20sorry%2C%20but%20an%20error%20has%20occurred.&
tracking_id=83526f84-226a-43cc-ae2d-2747f394d71b
```
``` bash
# AUTHENTICATION_ERROR response
example.com/callback?
error=AUTHENTICATION_ERROR&
error_type=USER_LOGIN_ERROR&
error_reason=USER_NOT_A_CUSTOMER&
message=It%20doesn%27t%20look%20like%20you%20are%20a%20customer%20with%20this%20bank.%20Please%20go%20back%20and%20make%20sure%20that%20you%20selected%20your%20bank.&
tracking_id=04de7a0a-101d-4d87-9f72-857c15783f79
```
## Error statuses
The error status indicates the type of error. It's always included in the error response and is mapped one-to-one with the `error` parameter. Tink may add new status codes in the future and won’t consider this a breaking change.
| Error status | Description |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| `USER_CANCELLED` | The end user cancelled the journey. This status shouldn't be considered as an error. |
| `BAD_REQUEST` | The URL is invalid, usually due to an incorrect or missing URL parameter. |
| `AUTHENTICATION_ERROR` | Something went wrong during the bank’s authentication process. |
| `TEMPORARY_ERROR` | A temporary error in Tink's platform. To resolve, try again later. |
| `INTERNAL_ERROR` | An unexpected error in Tink's platform. For help, [contact support](/resources/getting-started/support.md). |
### USER_CANCELLED
The user cancelled the journey, either by going back or using the close button. From a user’s perspective, the expected behavior is simply to leave the Tink environment. For that reason, Tink won’t display any error screen for this error status, and we recommend that you don’t treat them as errors. Instead, return your user to the last point prior to launching Tink.
| Error reason | Description |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `USER_CANCELLED` | The user cancelled the Tink Link flow. |
| `USER_DECLINED_CONSENT` | The user declined to provide their consent, which exits the Tink Link flow. |
### BAD_REQUEST
Something is wrong with the Tink Link URL, usually due to missing or incorrect parameters. For the full list of parameters and values, see the [Transactions SDK reference](/resources/transactions/transactions-sdk-reference.md).
| Error reason | Description |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `INVALID_PARAMETER_ACCOUNT_DIALOG_TYPE` | The `account_dialog_type` value is incorrect or missing. |
| `INVALID_PARAMETER_AUTHORIZATION_CODE` | One or more of these values are missing: `authorization code`, `handoff session ID`, and `authorization token`. |
| `INVALID_PARAMETER_CLIENT_ID` | The `client_id` value is incorrect or missing. |
| `INVALID_PARAMETER_CREDENTIALS_ID` | The `credentials_id` value is missing. Used only with [permanent users](resources/aggregation/permanent-users.md). |
| `INVALID_PARAMETER_FINANCIAL_SERVICES_SEGMENTS` | The `financial_services_segments` value is incorrect or missing. Allowed values: `PERSONAL`, `BUSINESS`. |
| `INVALID_PARAMETER_INPUT_PROVIDER` | The `input_provider` value is longer than 100 characters. |
| `INVALID_PARAMETER_INPUT_USERNAME` | The `input_username` value is incorrect, missing, or longer than 50 characters. |
| `INVALID_PARAMETER_PAYMENT_REQUEST_ID` | The `payment_request_id` value is missing. |
| `INVALID_PARAMETER_REDIRECT_URI` | The `redirect_uri` value is missing or malformed. |
| `INVALID_PARAMETER_REFRESHABLE_ITEMS` | The `refreshable_items` value is incorrect. Allowed values: `CHECKING_ACCOUNTS`, `CHECKING_TRANSACTIONS`, `CREDITCARD_ACCOUNTS`, `CREDITCARD_TRANSACTIONS`, `SAVING_ACCOUNTS`, `SAVING_TRANSACTIONS`. |
| `INVALID_PARAMETER_REPORT_TYPES` | The `report_types` value is incorrect or missing. Shown only when using product bundling. |
| `INVALID_PARAMETER_SCOPE` | The `scope` value is missing. Used only with [Account Aggregation](/resources/aggregation.md). |
| `INVALID_STATE_ACCESS_TOKEN` | The `access token` value is missing, expired, or incorrect. |
| `INVALID_STATE_AUTHENTICATION` | The [credentialsType](/api-connectivity-v1#connectivity-v1/provider/the-provider-model) is `MOBILE_BANKID` or `THIRD_PARTY_APP` and either the user didn’t successfully authenticate, or the integration doesn't use BankID on a mobile device or a third-party app. |
| `INVALID_STATE_CREDENTIALS` | The credential has reached a `TEMPORARY_ERROR` state. |
| `INVALID_STATE_CREDENTIALS_IS_AWAITING_THIRD_PARTY` | Attempted authentication or refresh of a credential that is in a pending state. Used only with [permanent users](resources/aggregation/permanent-users.md). |
| `INVALID_STATE_EMBED_NOT_ALLOWED` | Tink is embedded when embedding isn't allowed. To request the ability to embed Tink, go to **Console** > [**your_app**] > **App settings** > **App details** > **Display name (public)** and select **Verify**. |
| `INVALID_STATE_NON_OPEN_BANKING_PROVIDER` | Attempted authentication of a credential for a non-open-banking provider. Used only with [permanent users](resources/aggregation/permanent-users.md). |
| `INVALID_STATE_PAYMENT_RETRY_NOT_ALLOWED` | The `payment_request_id` has already been used. Used only with direct payments. |
| `INVALID_STATE_PERMANENT_USER_FLAG` | Attempted to use permanent users for an app that doesn't have permanent users enabled. |
| `INVALID_STATE_PROVIDER` | The selected provider isn't available. Occurs when a preselected provider doesn't exist in the selected market because:
- The provider isn't included in the app's provider policy.
- The provider isn't available. |
| `INVALID_STATE_PROVIDER_DOES_NOT_RECOGNIZE_USER` | The user has selected a provider that they don’t have an account with. |
| `INVALID_STATE_REDIRECTED_AUTHORIZATION_TOKEN` | A third party is redirecting back to Tink, but the query is missing `authorization_token`. |
| `INVALID_STATE_REDIRECTED_CREDENTIALS_ID` | A third party is redirecting back to Tink, but the query is missing `credentialsId`. |
| `INVALID_STATE_REFRESH_CREDENTIALS_RATE_LIMITED` | The app has exceeded the [API rate limits](/api#introduction/rate-limits) while refreshing credentials. |
| `INVALID_STATE_REDIRECT_URI` | The `redirect_uri` is invalid. Make sure that it's registered in the "App settings" page in [Console](https://console.tink.com/app-settings/client). |
| `INVALID_STATE_SCOPE` | One or more scopes are incorrect or not available for the OAuth client. |
### AUTHENTICATION_ERROR
There was an issue during the authentication towards the financial institution. In addition to an error reason, these errors also include an `error_type`.
For a complete list of authentication errors, see [Provider Consent errors](/resources/transactions/provider-consent-errors.md).
### TEMPORARY_ERROR
A temporary error in Tink's platform or a network issue. To resolve any of these errors, try again later.
| Error reason | Description |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `REQUEST_FAILED_CREATE_RESET_CREDENTIALS` | The reset credentials endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_ACCOUNTS` | Couldn't retrieve the user's account. Used only for Account Check or for the reports/bundled flow when Account Check is a bundled product. |
| `REQUEST_FAILED_FETCH_PROVIDER` | Causes:
- The providers endpoint is unavailable.
- The selected provider couldn't be found.
- `input_provider` doesn't exist in the selected market.
- `input_provider` is not included in the configured Provider Policy. |
| `REQUEST_FAILED_OAUTH_DESCRIBE` | The `redirect_uri` parameter is not registered in Console or the OAuth describe endpoint is unavailable. |
### INTERNAL_ERROR
An unexpected internal error occurred in Tink's platform.
| Error reason | Description |
| ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `REQUEST_FAILED_CONSUME_HANDOFF_SESSION` | The handoff session endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_ACCOUNT_CHECK_REPORT` | The account check endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_ANONYMOUS_USER` | The create anonymous users endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_BULK_PAYMENT` | The bulk payments endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_CREDENTIALS` | Credentials can't be created because the `credentials:write` scope is missing or the Tink credentials service is unavailable. |
| `REQUEST_FAILED_CREATE_HANDOFF_SESSION` | The handoff session endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_INCOME_CHECK_REPORT` | The income check endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_RECURRING_PAYMENT` | The recurring payment endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_REPORT` | The bundled flow endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_RISK_INSIGHTS_REPORT` | The risk insights endpoint is unavailable. |
| `REQUEST_FAILED_CREATE_TRANSFER` | The transfer endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_BULK_PAYMENT` | The bulk payments endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_BULK_PAYMENT_STATUS` | The bulk payments endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_CREDENTIALS` | The credentials endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_EXISTING_USER` | Occurs when:
- `handoffSessionId` is missing.
- `authorizationCode` is missing.
- The handoff session endpoint is unavailable.
- The authentication/token endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_FLOW` | The flow endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_HANDOFF_SESSION` | The handoff session endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_LEGAL_TEXT` | Couldn't the privacy policy or terms and conditions. |
| `REQUEST_FAILED_FETCH_PAYMENT_INFO` | The get payment or get transfer details endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_PAYMENT_TRANSFER_INFO` | The payment transfer endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_PROVIDER_PAYMENT_CONDITIONS` | The payment providers endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_PROVIDERS` | The providers endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_RECURRING_PAYMENT_INFO` | The recurring payment endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_REPORTS_DESCRIBE` | The bundled flow endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_SESSION` | The session endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_TRANSFER_ACCOUNTS` | The transfer accounts endpoint is unavailable. |
| `REQUEST_FAILED_FETCH_USER_WITH_EXISTING_TOKEN` | The user endpoint is unavailable. |
| `REQUEST_FAILED_REFRESH_CREDENTIALS` | The credentials endpoint is unavailable. |