hop_consent: A consent-attributed hop outside a top-up's root
The hop names the end user's consent in place of its delegator's signature, and that is accepted only at the first hop of a budget funded by a hosted top-up whose page checked its CSRF token. This hop's consent is malformed, it is deeper than the root, it names another top-up (or the budget is not a top-up budget), names no CSRF-bound consent, or also carries a delegator signature. Nothing was opened or allocated.
The same code answers a human payment's consent root (pay-consent) that is malformed, is not at the root, or sits on a top-up budget. A consent sent without a signed-in console session answers 403 pay_consent_session first, and a consent on a budget that is not a credit card budget answers 409 pay_consent_card_only first.
What to do
- Below the root, sign every hop with the delegator's own key (
signHopIntent) and send the payee's signed offer. - A top-up consent root is created only by the hosted top-up page, and a pay-consent root only by a console click on a human payment; neither can be sent to the owner API.
On the wire
HTTP 409, error type state_error.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"reason": "hop_consent",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "hop_consent",
"message": "…",
"param": "delegation",
"doc_url": "…/errors/hop_consent.md",
"fix": "a consent-attributed hop is accepted only at the root of a budget funded by a CSRF-bound hosted top-up; below the root every hop is signed by its delegator"
}
}
See all error codes.