spending_cap_exceeded

HTTP 403   title: Spending cap exceeded

What it means

The human set a spending cap for the acting assistant: the most that one pay may charge. The checkout total of this pay is above it, or the checkout is in another currency than the cap. Rejected before charging — no money moved. A cap of 0 stops the payments of that assistant.

What to do next

The assistant cannot raise its own cap; that is the human’s. Report the refusal and let the human raise it, or set it in the checkout’s currency (the reference implementation exposes it on the manage-assistants page). Caps are operator policy and off by default.

The response

{
  "type":   "https://kiosk.tech/problems/spending_cap_exceeded",
  "title":  "Spending cap exceeded",
  "status": 403,
  "detail": "… what went wrong on THIS request …",
  "code":   "spending_cap_exceeded"
}

This page documents the RFC 9457 type URI https://kiosk.tech/problems/spending_cap_exceeded. The URI is an identifier, not a locator a client should fetch: branch on the document’s code member. The normative definition lives in the error vocabulary of the Kiosk specification (§9 of the formal spec).