## Error and response codes
IF the API is not called successfully, you receive a HTTP Status Code `4xx` or `500`. A `422` code is returned when the message was well-formed, but could not be processed because of, for instance, wrong data.
In the response you find additional information on how to prevent or handle the error through an array of `Errors` with an `error_code` and `error_message`, like in the following example.

```json
{
  "Errors": [
    {
      "error_message": "Amount can't be 0 or negative",
      "error_code": "200"
    }
  ]
}
```
Below are some of the possible error codes:
| Code | Description |
|  --- | --- |
| 010 | Malformed request: missing one or more mandatory core parameter(s) |
| 011 | Malformed request: missing one or more mandatory Payment Processor parameters |
| 012 | Malformed request: missing one or more mandatory SourceConnector parameters |
| 200 | Invalid data: the supplied data is incorrect (e.g. an invalid e-mail address). |
| 201 | Sort code or bank account is invalid (Bacs Direct Debit). |
| 202 | IBAN *<your-IBAN>* is not valid. |
| 203 | The provided IBAN is not in SEPA geographical zone. |
| 204 | BIC is required to collect SEPA Direct Debit from a non-EAA country bank account. |
| 205 | Street, Housename or Number, Zip code and City are required to collect SEPA Direct Debit from a non-EEA country bank account. |
| 206 | Clearing number and/or bank account invalid (Sweden). |
| 998 | An object is missing and no default is specified in the org. |
| 999 | Error without specific category: consult the `error_message` for details. |