Decionis

Concept

Agent Refund Limits

Give the actor a discretion limit rather than the ability to refund, and make the limit a property of the action rather than of the login. A request written by a customer is untrusted text, so an amount it asks for is a claim rather than an authorisation — which is how an agent handling a $59 order ends up issuing one for $708. Below the limit the refund proceeds; above it, it waits for a named person.

How do I cap what a bot or support agent can refund on its own?

Give the actor a discretion limit rather than the ability to refund, and make the limit a property of the action rather than of the login. A request written by a customer is untrusted text, so an amount it asks for is a claim rather than an authorisation — which is how an agent handling a $59 order ends up issuing one for $708. Below the limit the refund proceeds; above it, it waits for a named person.

2 patterns answer this

From this term to a governed action

  1. Customer refundThe recurring action behind this term.
  2. Commerce Gate policy packThe pack whose rules decide it, rule by rule.
  3. Try to break it in the sandboxA real signed verdict, no account.
  4. Deploy on your surfaceAvailable on 3 platforms today.
  5. Verify the proof yourselfCheck the signature without trusting us.
  6. Start NowMeasure on your traffic before enforcing.

Where this fits

Decionis is the deterministic decision layer between intent and execution. This concept is one way in; the architecture behind it is the same in every case.

Why Decionis existsHow the protocol worksGlossary