pay_frozen: The budget or the paying stream is frozen or stopped
A payment (POST /owner/v1/human/payments) cannot go ahead because the stream it pays from is frozen or stopped:
- the
parentStreamId, or one of its ancestors, is frozen or under an emergency stop (paramisparentStreamId); or - the payment's own stream, or an ancestor, is frozen or stopped (
paramisbudgetId).
A main-switch pause counts as a freeze. A new root payment that names no parent stream is refused before this check: with frozen (error type halted) during a main-switch pause, and with stopped (error type halted) on a budget under an emergency stop. Nothing was paid. When the parent stream is not frozen, a retry of a payment that was already signed still returns that payment, because it is answered before the payment's own stream is checked.
What to do
- The owner thaws the stream or budget from the console, then retry with the same
requestRef. - After an emergency stop in revoke mode, fund a new budget.
On the wire
HTTP 409, error type state_error.
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "pay_frozen",
"message": "…",
"param": "parentStreamId",
"doc_url": "…/developers/human-payments.md#pay-frozen",
"fix": "the budget or its parent stream is frozen or stopped; thaw it from the console first"
}
}
See human payments and all error codes.