An example of chargeback representment as a governed process: agents do the 13 steps, and a person signs 4 gates before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.
minctrl.process/v1 · hash 1731f3f67320…865b
Card disputes arrive by the tens of thousands per year, each demanding manual reason-code classification, winnability triage, and a hand-assembled compelling-evidence packet filed inside a hard network deadline. Analysts burn hours per case, miss filing windows, and lose winnable disputes by default while refunding ones they should have fought. Routine disputes are auto-classified, scored for winnability, and packaged into a network-compliant representment within deadline, with auto-submission below a value threshold. Only high-value, borderline, or customer-affecting fight-vs-refund calls reach a disputes manager, who signs the irreversible network filing.
Accepting a chargeback (writing off the disputed amount) or firing off representment evidence both foreclose options and can't be re-tried, so a disputes analyst signs off the accept/fight decision and the evidence package before it's submitted.
| Rule | What it requires |
|---|---|
| Visa / Mastercard dispute rules (VCR / Mastercard chargeback guide) | Representment must be filed within the network's response window (commonly around 30 days from the chargeback, varying by reason code and network) with compelling evidence matched to the specific reason code. |
| Reason-code-specific evidence | Each dispute reason code (fraud, product-not-received, not-as-described, etc.) requires a defined evidence package; mismatched or generic evidence loses the case. |
| Regulation E / Regulation Z (issuer side) | On the issuer/cardholder side, error-resolution timelines under Reg E (EFTs) and Reg Z (credit) constrain how and when disputes are handled. |
A summary for orientation, not legal advice.
A minctrl.process/v1 document: the graph and the hash of the process it becomes.
Import into Minctrl opens this example in your workspace; one click stores it as your first version. Import JSON does the same with the file, and a file changed after download is refused.
Every connector starts in shadow: steps run, nothing leaves Minctrl until you configure a connector and switch it live.
Change signers, time limits and steps on the canvas. Each save is a new version; a running case stays on the version it started with.
The example models the clock: each dispute is tracked against the network's response window, commonly around 30 days from the chargeback and varying by reason code and network, and the clock and every action are recorded as evidence. The windows that apply to you come from your acquirer and the current network rules, and filing on time remains your team's responsibility. Minctrl holds no certification, and this is not legal advice.
The AI agent reads the specific reason code, gathers the order, delivery and authorization evidence the network expects for that code, and assesses win likelihood. Because each reason code requires a defined evidence set, generic packages are flagged before submission.
A disputes analyst. Both accepting a chargeback (writing off the amount) and submitting representment foreclose options and can't be re-tried, so the accept/fight decision and the evidence package park at a human sign-off gate with a tamper-evident audit hash on the run.