mandate_payee: The payee is not allowed
The payee is not on a governing mandate's payees list, or it is on payeeDeny. Three places check it:
- Opening or delegating a stream: its
serviceNodeis outside the delegator's or an ancestor's payee list, or outside the child's own requested mandate. Nothing is opened. - Spending on a stream: its
serviceNodeis outside a governing payee list. Nothing is billed. - A payment authorization (
POST /owner/v1/streams/{id}/payment-authorizations): the payee it names is outside a payee list governing the stream. Nothing is authorized.
What to do
- Use a payee the mandate allows.
- If the payee should be allowed, the root funder opens a budget whose mandate lists it; a running mandate can only narrow.
On the wire
HTTP 409, error type halted (or mandate_error, error: "mandate", on open and delegation).
On spending, a client that does not send Dynamo-Error-Detail: 1 to a route that predates 1.4.0 sees the legacy reason cap, so its response shape is unchanged. Opted-in clients, and the routes that always answer in detail such as payment authorizations, see mandate_payee.
On a stream open or delegation or a human payment, a client that does not send Dynamo-Error-Detail: 1 gets {"error": "mandate", "reason": "mandate_payee", "detail": "…"}: the precise reason, without errorDetail. The child adoption preparation (POST /owner/v1/streams/{id}/children/adopt-prepare) sends errorDetail to every client. The plugin wire's child open (POST /plugin/v1/streams/{id}/children) answers HTTP 409 {"error": "child open refused (fail closed)", "reason": "mandate_payee"}, with no detail and no errorDetail.
With Dynamo-Error-Detail: 1:
{
"error": "halted",
"reason": "mandate_payee",
"streamId": "stm_…",
"detail": "…",
"errorDetail": {
"type": "halted",
"code": "mandate_payee",
"message": "…",
"param": null,
"doc_url": "…/errors/mandate_payee.md",
"fix": "the serviceNode is not on the mandate's payee list (or is denied); use an allowed payee"
}
}
See all error codes.