card_agent_proof_invalid: The signed proof did not verify

For Mastercard Agent Pay, the Verifiable Intent chain did not verify: a layer has the wrong shape, layer 1 is not signed by the pinned issuer or binds no user key, layer 2 is not signed by the user key layer 1 binds, a layer is not current, it is addressed to another merchant, its amounts, dates, payee website or constraints are malformed (including a currency other than USD, a budget with no maximum, or a recurrence without its amount range), or it carries a constraint this release does not enforce. For Visa Intelligent Commerce, the Trusted Agent Protocol signature did not verify: the covered components, tag, algorithm or time window are wrong, the key directory does not know the key, or the nonce was used before. Nothing was authorized.

What to do

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_proof_invalid",
  "detail": "…",
  "errorDetail": {
    "type": "state_error",
    "code": "card_agent_proof_invalid",
    "message": "…",
    "param": "intent",
    "doc_url": "…/errors/card_agent_proof_invalid.md",
    "fix": "the Verifiable Intent chain or the Trusted Agent Protocol signature did not verify, is stale or was replayed; have the person or agent sign afresh"
  }
}

See card agent programs and all error codes.