Signup+ errors
Learn about Signup+ errors.
The Signup+ API returns a Problem JSON for client usage and server-side processing errors.
The information returned includes the following fields:
Field | Always returned? | Description |
---|---|---|
type | Yes | A link to human-readable documentation about the error. |
title | Yes | A short summary of the error. |
status | Yes | The HTTP status code for the error. |
detail | No | A more detailed explanation of the error. |
trace_id | Yes | The TrueLayer trace identifier for the request. |
instance | No | An absolute URI that identifies the specific occurrence of the problem. |
errors | No | A description of what went wrong and where. |
Below is an example of an error you can receive when you use Signup+.
{
"type": "https://docs.truelayer.com/docs/signup-errors#failed-payment",
"title": "Failed Payment",
"status": 422,
"detail": "Cannot process failed payments",
"instance": "/signup-plus/payments",
"trace_id": "149c0d43-aaa0-4e46-9add-ea80b7697f28"
}
Universal errors
You can receive the following errors with both the payments only and data only flows.
HTTP Status | Title | Retry | How to handle |
---|---|---|---|
400 | Invalid Parameters | No | Check the error object for details of which fields are invalid. |
400 | Provider not supported | No | The provider doesn't support this operation. |
Unauthorized | No | Create a new access token. The access token may be invalid or expired. You can check for more details in the error description. | |
403 | Forbidden | No | Ask the user to reconnect their account. This error is returned when the access to their account is no longer valid, either because it expired or because the user revoked it themselves. |
422 | User Data Not Found | No | User data not found. |
422 | Joint Accounts Not Supported | No | Joint accounts not supported. |
500 | Internal server error | Yes | Retry later. |
Payments only errors
Requests you make to the Signup+ with the payments only flow can return the unique errors below.
HTTP Status | Title | Retry | How to handle |
---|---|---|---|
404 | Payment Not Found | No | The payment id supplied does not match the client_id that is being used to call Signup+. Either the payment has been made with a different client_id or has not been processed. Ensure that the payment is made with the right client_id and try again. |
422 | Invalid Payment | No | Payment is not a closed loop payment. |
422 | Payment Processing | Yes | Payment is still in progress. Retry when payment is processed or reached a terminal state. |
422 | Failed Payment | No | Cannot retrieve data from a failed or rejected payment. |
Data only errors
Requests you make to Signup+ using the data only flow can return the responses and errors below.
HTTP Status | Title | Retry | How to handle |
---|---|---|---|
403 | Missing Claims | No | Add the missing claims to the access token. |
422 | No Valid Accounts | No | User has given permission to access an invalid account. This usually occurs because they don't have a current account with that provider. |
Provider Timeout | Yes | The bank is experiencing issues. Retry later. |
Variable recurring payments errors
Requests you make to Signup+ using the data only flow can return the responses and errors below.
HTTP Status | Title | Retry | How to handle |
---|---|---|---|
404 | Mandate Not Found | No | The mandate id supplied may not match the client_id that is being used to call Signup+. Either the mandate has been made with a different client_id or has not been processed. Ensure that the mandate is made with the right client_id and try again. |
422 | Invalid Mandate State | No | The mandate must be authorised. |
422 | Mandate Revoked | Yes | The mandate cannot have a status of revoked. |
Updated 3 months ago