topup_payee_offer_invalid: The payee offer does not cover this top-up
POST /owner/v1/topups carried a payeeOffer, and the deployment checked it the same way it will check the top-up budget's root hop, once for now and once for the last second of the top-up link. One of these failed:
- The offer is malformed (for example, its categories are not sorted, unique slugs or exactly
["*"], orissuedAtis later thanexpiresAt). - The offer is not signed by
payeeServiceNode: the signature recovers to another address, or does not recover at all. - The offer's validity window (
issuedAttoexpiresAt) does not cover the whole session, from now until the link expires (expiresInSeconds, one hour by default).
The message ends with the failed check. The offer is checked whenever it is sent, even where own hops are optional. Nothing is created. A body whose payeeOffer fields have the wrong types or extra keys answers invalid_request instead.
The multi-tenant hosted tier answers the same way: the front door passes the request to the account's core.
What to do
- Have the payee sign the offer with its own key for its own
payeeServiceNode. - Make the offer valid from before the request until after the link expires, or shorten
expiresInSeconds. - See the top-up guide.
On the wire
HTTP 409, error type state_error, param: "payeeOffer".
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "topup_payee_offer_invalid",
"message": "the payee offer does not cover this top-up: the payee offer is not signed by the payee (fail closed, nothing created)",
"param": "payeeOffer",
"doc_url": "…/developers/topup.md#topup-payee-offer-invalid",
"fix": "the payee offer must be signed by payeeServiceNode and valid from now until the top-up link expires"
}
}
See all error codes.