Chargeback representment
Turn an inbound dispute into a filed representment packet or a clean refund on the chargeback-representment vertical — a disputes manager signs every fight-vs-refund call and every network filing.
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). Low-value or clearly-losing disputes route to
accept-signoff (gate:accept-chargeback-signoff) instead.
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"
}
}')
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.
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 — may park again
After the response is filed, the run tracks network responses. On issuer
pre-arbitration it assembles a rebuttal and parks again at prearb-signoff; if the issuer
escalates past pre-arb, it parks at arb-signoff before filing to network arbitration.
Each irreversible filing is fronted by its own manager gate, so this run typically parks
several times before it terminates.
Governance note
The submit, prearb-submit, arbitration-file, and accept-chargeback steps are
reversible: false — a filing to a card network can't be recalled — and stay shadowed
until a connector opts in. Every one is protected by a manager gate
(signoff → prearb-signoff → arb-signoff) so no irreversible network filing fires
without a signed human verdict.
Debt collection
Run compliant outreach and negotiate a plan on the collections vertical — a manager signs legal escalation and settlements before any adverse action is executed.
Governance model
How Minctrl decides when a step runs on its own and when it parks for a human — risk-tiered gates, the judge panel, calibrated confidence, and a tamper-evident audit trail.