card_agent_merchant_not_allowed: The token does not allow this merchant
The token's merchant allow-list (Verifiable Intent allowed_payees or allowed_merchants, Visa preferredMerchantName, or the token's own merchant list) does not name this deployment's merchant domain. On a credit card budget the card network sees one merchant, this deployment, so the list cannot be met. Nothing was authorized.
What to do
- Read this deployment's merchant domain from
GET /owner/v1/card-agent-programs(merchant) and ask the person to allow it.
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_merchant_not_allowed",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "card_agent_merchant_not_allowed",
"message": "…",
"param": null,
"doc_url": "…/errors/card_agent_merchant_not_allowed.md",
"fix": "the token's merchant allow-list must name this deployment's merchant domain (GET /owner/v1/card-agent-programs)"
}
}
See card agent programs and all error codes.