vatverify home
All errors

bzst_server_error

BZSt accepted the request but returned an internal server error (evatr-2004, evatr-2011, evatr-3011).

HTTP 502 · Bad Gateway

Example response

{
  "error": {
    "code": "bzst_server_error",
    "message": "BZSt evatr-2004: internal server error.",
    "retryable": true
  },
  "meta": {
    "request_id": "a1b2c3d4-...",
    "latency_ms": 1620,
    "bzst_status_code": "2004"
  }
}

What happened

The BZSt eVatR endpoint received and processed the request but returned an internal error status: 2004, 2011, or 3011. The request was well-formed and the connection to BZSt was successful. The failure originated inside the BZSt system.

This error is distinct from bzst_unavailable, where the eVatR service itself was unreachable or in a maintenance state. Here the service was reachable but encountered a fault while handling the specific request.

These codes occur rarely. They are most common during high-load periods at BZSt or immediately after a deployment on the BZSt side.

How to fix

  1. Retry once after a short delay (10-15 seconds). Most bzst_server_error responses resolve on the next attempt.
  2. If the error persists across multiple retries, contact vatverify support and include the request_id from meta. This lets the support team correlate the BZSt status code with the upstream request log.
  3. Do not discard the original request parameters. A persistent bzst_server_error on the same number may indicate a BZSt-side data issue for that specific VAT number that requires manual investigation.

See also