The customer did a bank transfer but didn’t include the reference

Failure to include this reference will result in EMS refunding the money to the customer. He or she will have to initiate another bank transfer. No status update via the webhook will be done when this occurs

Posting the incorrect API key

Each request is authenticated with the encoded base64 authentication token. Please refer to the Authentication section. The incorrect authentication token will result in response with an error. Performing such a request is illustrated in the example bellow.

If we misspell the authentication token and you try to send the encoded hutter2 in base64:

Request:

GET /v1/orders/4c6afd74-a840-4aab-b411-1e6e0636d341/ HTTP/1.1
Authorization: Basic aHV0dGVyMgo=

Response:

{
  "error": {
  "type": "<class 'werkzeug.exceptions.Unauthorized'>", 
  "value": "The server could not verify that you are authorized to access the URL requested.  You either supplied the wrong credentials (e.g. a bad password), or your browser doesn't understand how to supply the credentials required."
  }
}

Unsupported payment method

A merchant should apply for each of the provided methods separately. When the merchant is verified and the payment method is activated, the merchant can provide the payment method to the customers. If the payment method is not activated or the order request demands the unsupported payment method the server will respond with an error. It will also include the reson of the error.

An example below simulates an order request with the inactive credit-card payment method credit-card. The server responds with the error status for such order request. The response also provides the reason, which describes the error in detail.

Request:

POST /v1/orders/ HTTP/1.1
Authorization: Basic __AUTH_BASE64_KEY__
Content-Type: application/json

{
  "merchant_order_id": "EXAMPLE001",
  "amount": 995,
  "currency": "EUR",
  "description": "Example order #1",
  "return_url": "http://www.example.com/",
  "transactions": [
    {
      "payment_method": "credit-card"
    }
  ]
}

Response:

{
  "error": {
    "type": "<class 'werkzeug.exceptions.BadRequest'>", 
    "value": "The browser (or proxy) sent a request that this server could not understand."
  }
}