card_agent_cap_exceeds_token: The budget cap is above the token's limit
The requested capTotal is above what the token allows: its cumulative limit (Verifiable Intent mandate.payment.budget, the agentic token's amount limit) or its per-transaction limit (Verifiable Intent amount_range.max, Visa declineThreshold). The budget's one card authorization is one card transaction, so both bound it. For Visa Intelligent Commerce, the same code answers when the program reports that the instruction does not cover this amount at this deployment's merchant. A cap is never clamped: nothing was authorized.
What to do
- Send a
capTotalat or below the token's limit.
On the wire
HTTP 409, error type state_error. Every client gets errorDetail, with or without Dynamo-Error-Detail: 1. On the multi-tenant hosted tier the card agent funding route (POST /owner/v1/card-agent-programs/fundings) needs Dynamo-Version 1.8.0 or later: the front door answers a request served at an earlier version with HTTP 404 version_unavailable before the core sees it, and serves a request that names no version at the account's default (1.8.0 for new accounts). A single-tenant core answers whatever version the request names.
{
"error": "state",
"reason": "card_agent_cap_exceeds_token",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "card_agent_cap_exceeds_token",
"message": "…",
"param": "capTotal",
"doc_url": "…/errors/card_agent_cap_exceeds_token.md",
"fix": "send a capTotal at or below the token's amount limit; a cap is never clamped"
}
}
See card agent programs and all error codes.