Chargeback representment

Scenario. An inbound chargeback is ingested and classified by network reason code. The run scores winnability and assembles a compelling-evidence packet concurrently. A disputes manager signs the fight-vs-refund decision before the response is filed to the card network — and signs again at every irreversible network filing downstream.

Vertical: chargeback-representment · Parks at gate step-id: signoff (gate:fight-vs-refund-signoff). Clearly-losing disputes route to accept-signoff (gate:accept-chargeback-signoff) instead; low-value ones get an automatic goodwill refund and never park.

1. Start the run

RUN=$(curl -s -X POST "$API/process-runs" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "vertical": "chargeback-representment",
    "inputs": {
      "dispute_id": "CB-88231",
      "reason_code": "10.4",
      "amount": 249.00,
      "network": "visa",
      "risk": "high-value"
    }
  }')
RUN_ID=$(echo "$RUN" | jq -r .id)

The run classifies the dispute, scores winnability, assembles the evidence packet, runs QC, and parks at the fight-vs-refund gate. risk is the routing input the resolver matches against the branch labels: "high-value" routes the compliant packet to the fight-vs-refund gate.

2. Read where it parked

curl -s "$API/process-runs/$RUN_ID" -H "Authorization: Bearer $TOKEN"

status is awaiting_human. Read the trace to confirm which gate step-id the run parked on — signoff for a fightable dispute, or accept-signoff for a low-value / unwinnable one — and resume with that step-id.

3. Resume — the disputes manager signs

curl -s -X POST "$API/process-runs/$RUN_ID/resume" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "gate": "signoff",
    "decision": "approved"
  }'

An approved fight decision proceeds to file the response to the network; an accept/refund verdict routes to concede liability instead.

4. Outcome — parks again

After the response is filed, the run tracks network responses, assembles the pre-arbitration rebuttal, and parks again at prearb-signoff (gate:prearb-signoff) before the next irreversible network filing. Each irreversible filing is fronted by its own manager gate, so expect this run to park more than once.