card_agent_controls_conflict: The token's controls and the mandate do not overlap

The token's spend controls are intersected with the requested mandate, and the intersection is empty (for example the token's validity window ends before the mandate's begins), or the token names a control this release cannot map: a recurrence frequency with no Dynamo window (Mastercard Verifiable Intent or Visa), or a Visa instruction mandate not in USD. Nothing was authorized. A Mastercard Verifiable Intent with a currency other than USD, or with a constraint type this release does not enforce, answers card_agent_proof_invalid instead.

What to do

On the wire

HTTP 409, error type state_error. param is null for an empty intersection, intent for a Mastercard recurrence refusal and instructionId for a Visa refusal. 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_controls_conflict",
  "detail": "…",
  "errorDetail": {
    "type": "state_error",
    "code": "card_agent_controls_conflict",
    "message": "…",
    "param": null,
    "doc_url": "…/errors/card_agent_controls_conflict.md",
    "fix": "the token's controls and the requested mandate have no overlap (or name a control this release cannot enforce); request a mandate inside the token's window"
  }
}

See card agent programs and all error codes.