The approval queue

Why we require approval

Surprise auto-submission is a common complaint cluster against the competing chargeback tools (see /compare). Once Stripe accepts your evidence, you can’t pull it back. So Victava starts in manual review: every defense stops for your approval. Auto-Pilot is a separate, explicit opt-in for merchants who want hands-off filing, and it submits only cases that pass the score, amount, timing, deadline, and packet-validation limits you configure.

What you see when a dispute is ready

The /disputes dashboard shows the dispute card with:

• A status badge (ready_for_review) and a deadline badge counting down to the evidence deadline.
• The agent’s recommendation: represent, needs_info, or accept.
• The numeric win probability (0.0–1.0).
• A reasoning paragraph explaining what the agent considered.
• The full evidence package with provenance shown per item, and the drafted rebuttal text with Exhibit citations.
• A recovery + fee preview (recovery amount, success fee, net to you) on the approve confirmation modal.

Approve, edit, or skip

You can edit any line of the rebuttal before approving, swap an Exhibit for one you upload, or skip the dispute entirely. Skipping means we do not submit evidence; the dispute reaches the evidence deadline and resolves as expired. You owe $0 on a skip.

Deadlines and reminders

Victava runs a scheduled task (deadline-reminders) that emails you when a dispute is approaching its evidence deadline. The cadence is approximately 72h, 48h, and 24h before the deadline (max three reminders per dispute). If you stay in manual mode and don’t act by the deadline, the dispute auto-expires; Victava does not submit merely because a deadline arrived. Auto-Pilot can file only when you enabled it and the case passes every configured guardrail.

What gets locked at approve time

The exact evidence_drafts.evidence_payload shown on screen is what gets sent to Stripe. The pipeline runs a final drift check (compileStripeEvidencePayload + validate-evidence) before submission to confirm the payload hasn’t changed between approve and submit. Drift means we error out instead of submitting unverified content.