Errors

The Direct Debit API uses conventional HTTP response codes to indicate the success or failure of an API request. In general:

• codes in the 2xx range indicate success
• codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a header is missing, etc.)
• codes in the 5xx range indicate an error with Ayoconnect or the bank's system (these are rare but they happen).

As our API can raise errors for many reasons, such as a failed charge, invalid parameters, authentication errors.. we recommend writing code that gracefully handles all possible error codes.

All the errors include an error code and a short human-readable message that briefly explains the error reported (you can use it internally but don't share it with your clients/users).

Error responses

Error responses are a combination of the HTTP response code, the service code, and the case dode.

Error response = HTTP response code + service code + case code

Service Codes

Below is a list with all the service codes:

HTTP Response Codes

Below is a list of possible HTTP response codes, along with additional information about them:

Case Codes

Below is a list of all possible HTTP response codes and case codes, along with additional information about them: