Not affiliated with Lyzr.

Card-dispute operations · US issuers

Card disputes, resolved inside the policy your CRO sets.

ResolveIQ works each dispute end to end: evidence, fraud and sanctions checks, the network-correct reason code, the Reg E or Reg Z clock. Inside policy, it posts the money and files with Visa or Mastercard. Outside it, it stops and hands an analyst a written recommendation. Every case leaves a sealed record an examiner can replay.

  • Policy-gated autonomy
  • Network-correct filing
  • Denials never automated
  • Sealed, replayable record
DSP-44910Visa 13.1$842.17Resolved in policy

“Ordered a monitor 3 weeks ago - never arrived, merchant unresponsive.”

evidence score 0.99threshold 0.95
Executed by the agent
Credit $842.17 and file Visa 13.1 via VROL
Posted: disputes suspense $842.17 (DR 1855 / CR 2201), then chargeback recovery receivable $842.17 (DR 1310 / CR 1855).
DSP-44927Visa 13.1$1,310Needs an analyst

“Says the laptop never showed up and wants a full refund.”

evidence score 0.41threshold 0.95
Recommended to an analyst
Deny the claim - cardholder liable
Evidence score 0.41 is below the 0.95 auto-resolve threshold. Amount $1,310 exceeds the $1,000 autonomous-credit ceiling for Mass cardholders.
The answer in one screen
27 of 38
demo disputes resolved inside the default policy
authored demo book
87.8%
of autonomous credits went to valid claims, across 1,000 labelled disputes
backtest · synthetic labels
$37 → $18
blended cost per dispute, manual vs governed
modeled · illustrative
0
denials executed without an analyst
policy control, by design

For the Head of Disputes

Analysts touch only the cases that need judgment - 11 of 38 here - and each arrives with the recommended action, the money it moves, the consumer notice and the deadline.

For the CRO and Model Risk

Autonomy is a versioned policy you set and can test first: threshold, ceilings by segment, file floor, categories. The score is backtested and calibrated, and an independent re-check must agree before money moves.

For the Examiner

A per-case record of every step, control, model call, analyst decision and posting - chained, server-sealed, and replayable from the recorded inputs.

Why disputes, why now

Volume is rising, the clock is fixed, and the money has to reconcile

106M

disputes Visa processed globally in 2025, up 35% since 2019

Source: Visa, 1 Apr 2026
$15.3B

projected US chargeback value in 2026, across ~146M disputes

Source: Datos Insights projection
10 business days

to resolve a debit-card dispute or provisionally credit the account

Source: 12 CFR 1005.11(c)
How a dispute moves

Six specialists, one policy gate, one record

  1. Intake
  2. Evidence
  3. Fraud + OFAC
  4. Evidence score
  5. Rules + reason code
  6. Post + file
inside policyscore ≥ 0.95, within ceiling, no stop → the agent posts and files
outside policyany stop condition → a written recommendation for an analyst
Where it stops

The agent knows the limits of its authority

Evidence below threshold

Score under 0.95 on hand-weighted, visible factors - calibrated against labelled history.

Amount above the ceiling

The CRO sets the autonomous-credit ceiling per segment (default $1,000).

Sanctions match

An OFAC potential match blocks all funds movement until Compliance acts.

No recovery right

Lapsed network window or a 3-D Secure liability shift: someone must own the loss decision.

Adverse to the cardholder

Denials are only ever recommended - an analyst decides, with the notice and documents right attached.

Evidence missing

Delivery proof against the claim, an unmatched transaction, or a “not as described” claim without documents.

Architecture

A manager agent, specialists, and code that decides

The design follows the manager-agent pattern Lyzr describes in its BFSI dispute-management playbook. This build runs that pattern on its own TypeScript engine - no Lyzr runtime is called. Everything that decides or moves money is deterministic code; a language model only narrates the result for the analyst, and every line it writes is checked against the engine's facts before it is shown.

Risk Scoring

Builds the evidence score from transparent factors and applies the policy gate.

Tools: Scoring engine · Control: Reflection

Watch one resolve, and watch one stop.

Run DSP-44910 through the agents and see the money post and the chargeback file. Then run DSP-44927 and approve - or override - the recommendation yourself.

Synthetic bank, cases and history. Connectors to core banking, OFAC and the networks are simulated and labelled as such in the console; the engine, rules, ledger, grounding check and audit seal execute.