What it means

You have used up your contracted verification allowance for the current period, AND any extra (burst) allowance alseda configured on top of it has also been exhausted. PreVOP refuses the request to keep your account within its agreed consumption envelope.

When you'll see it

• Your daily / weekly / monthly / annual quota (whichever unit applies to your contract) is fully consumed.
• If extra allowance was provisioned, it is also exhausted.
• No active quota is configured for your account — for example a new customer that is not yet operational.
• The gateway is configured to refuse once the window closes, not to queue — there is no backpressure or delayed retry.

Example response

HTTP/1.1 429 Too Many Requests
Content-Type: application/problem+json
X-Request-ID: 550e8400-e29b-41d4-a716-446655440000
X-Quota-Extra: false
Retry-After: 3600

{
  "type":    "https://errors.prod.prevop.alseda.eu/errors/quota-exceeded",
  "code":    "QUOTA_EXCEEDED",
  "title":   "Quota exhausted for current period",
  "status":  429,
  "detail":  "Monthly quota of 100000 + extra 5000 reached; resets 2026-05-01"
}

How to fix

1. Read the detail field — it names the quota unit and, where possible, the reset date.
2. Wait until the quota window resets. For monthly quotas this is the 1st of the next month (Berlin time); for daily, midnight Berlin.
3. For a longer-term need, contact alseda to discuss raising your contracted quota or adding extra allowance.
4. If your traffic spiked unexpectedly, inspect your own caching + deduplication — repeated verifications of the same payee are usually avoidable.
5. Monitor the X-Quota-Extra header on successful responses — it is true when you are consuming extra allowance, a leading indicator of running out.

Related

• Customer API Contract §3 — Quota headers (X-Quota-Extra, Retry-After)
• See also: CUSTOMER_BLOCKED — administrative throttling, distinct from the volume-based throttling on this page.