Settling from a notice a provider posted.
The rule the whole namespace exists to enforce: a notice NAMES an invoice, and the invoice SELECTS the rail that must authenticate the notice. A caller never chooses its own authenticator. The provider in the URL is a claim, checked against the invoice; a body that names an invoice is a claim, and granting on it directly is the vulnerability this shape removes.
Returns a verdict value, not a response: the boundary decides what an HTTP status is.
Settling from a notice a provider posted. The rule the whole namespace exists to enforce: a notice NAMES an invoice, and the invoice SELECTS the rail that must authenticate the notice. A caller never chooses its own authenticator. The provider in the URL is a claim, checked against the invoice; a body that names an invoice is a claim, and granting on it directly is the vulnerability this shape removes. Returns a verdict value, not a response: the boundary decides what an HTTP status is.
(apply-notice! {:keys [rails] :as deps} claimed notice)Authenticate notice for the invoice it names and settle from it.
Verdicts:
:notice/applied with the SettlementOutcome that was applied.
:notice/unauthenticated — the invoice's own rail did not accept the notice.
:notice/unknown-invoice — no such invoice, the claimed provider is not the
invoice's own, or that rail admits no settlement over HTTP at all. All three
are one verdict on purpose: telling a stranger which of them it was is
telling them what to send next.
Authenticate `notice` for the invoice it names and settle from it. Verdicts: `:notice/applied` with the SettlementOutcome that was applied. `:notice/unauthenticated` — the invoice's own rail did not accept the notice. `:notice/unknown-invoice` — no such invoice, the claimed provider is not the invoice's own, or that rail admits no settlement over HTTP at all. All three are one verdict on purpose: telling a stranger which of them it was is telling them what to send next.
(subject-invoice {:keys [store rails]} claimed notice)The invoice notice is about, or nil.
Named in the path when the rail can put it there, and read out of the body by the claimed rail when it cannot — a processor that posts every event of an account to one endpoint has nowhere else to put it.
The invoice `notice` is about, or nil. Named in the path when the rail can put it there, and read out of the body by the claimed rail when it cannot — a processor that posts every event of an account to one endpoint has nowhere else to put it.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |