topup_payee_offer_required: The top-up needs the payee's signed offer
POST /owner/v1/topups was sent without payeeOffer, and this deployment requires own hops on credit card budgets. With own hops, every hop carries its signers' own signatures: the end user's click on the top-up page is the consent at the budget's root, and the payee's signed offer says what it agrees to be paid for. Without the offer the top-up cannot be opened later, so it is refused now. Nothing is created.
Own hops are required on credit card budgets when CORE_OWN_HOPS is required, and also when it is unset: money modes default to required. Only CORE_OWN_HOPS=optional lets a top-up run without an offer.
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 an offer with its own key (
signPayeeOfferin the SDK) that covers the session's lifetime, and send it aspayeeOffer(categories,issuedAt,expiresAt,signature). - See the top-up guide and its "Who signs what" section.
On the wire
HTTP 409, error type state_error, param: "payeeOffer".
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "topup_payee_offer_required",
"message": "this deployment requires own hops on credit card budgets: the app agent signs a payee offer (signPayeeOffer) and sends it as payeeOffer (fail closed, nothing created)",
"param": "payeeOffer",
"doc_url": "…/developers/topup.md#topup-payee-offer-required",
"fix": "this deployment requires own hops on credit card budgets; the app agent signs a payee offer (signPayeeOffer) and sends it as payeeOffer"
}
}
See all error codes.