pay_consent_session: Only a signed-in console click can consent
A payment (POST /owner/v1/human/payments) carried consent: true, but it was not made from a signed-in console session: an API key or the owner token sent it. A pay-consent is the signed-in owner's CSRF-bound click in the console; on the hosted tier the dashboard's front door names the signed-in owner to your core in its own signed header, and an organisation member cannot consent. Nothing was opened (fail closed).
What to do
- Click Pay with Consent in the console while signed in.
- From code, sign the hop with the payer's own key and send it as
delegationinstead ofconsent.
On the wire
HTTP 403, error type authentication_error, errorDetail.param consent.
{
"error": "unauthorized",
"errorDetail": {
"type": "authentication_error",
"code": "pay_consent_session",
"message": "…",
"param": "consent",
"doc_url": "…/developers/human-payments.md#pay-consent-session",
"fix": "give consent by clicking Pay in the console while signed in; an API key or owner token cannot consent"
}
}
See human payments and all error codes.