session_signer_missing: No session signer is supplied for the key
A credit card top-up or a human payment named sessionKeyAddress, a session key the payer signs vouchers with itself, and this deployment's session signer resolver supplies no signer for that key. The resolver is part of a library or self-hosted core's configuration (CoreConfig.sessionSigners); it is never read from the environment. The request was refused before anything was allocated: no budget, stream, card authorization or record was created (fail closed). The same refusal answers a later voucher for such a stream when the resolver no longer supplies the key, for example after a restart: nothing is signed, so nothing is acknowledged.
What to do
- Supply a signer for the key in the deployment's
sessionSignersresolver (a local key in the payer's process, a KMS key or a wallet session key), then send the request again. - Or omit
sessionKeyAddress: the core then generates the stream's per-stream key, as before.
On the wire
HTTP 409, error type state_error.
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "session_signer_missing",
"message": "…",
"param": "sessionKeyAddress",
"doc_url": "…",
"fix": "…"
}
}
See top-ups, human payments and all error codes.