SAMPLE CASE · dp_4a8F2kL9
recovered
Fraudulent chargeSettled by StripeMar 27 → Apr 22, 2026
Sample only. This is not proof of live recovery in your workspace, and some real disputes still require manual review when evidence is missing.
JOURNEY
From detection to recovered revenue
Every event is logged. Every step is deterministic. The final outcome is the only place the colour green appears on this page.
- 01DetectedFraudulent charge
- 02Evidence6 of 6 fields matched
- 03DecisionFIGHT · auto-submit
- 04Submitted18d before deadline
- 05WonStripe ruled: recovered
DECISION ENGINE
The system decided to fight.
All six required fields were present and matched to the fraudulent-charge reason code. This sample case never needed merchant input.
DecisionFIGHT
Evidence strength6 of 6 fields
ActionAuto-submit
Deadline margin18 days
EVIDENCE EVALUATION
Complete6 of 6 fields matched
Transaction receiptMATCHED
Delivery confirmationMATCHED
Customer correspondenceMATCHED
Refund policyMATCHED
Product descriptionMATCHED
Billing address matchMATCHED
OUTCOME
You got your money back.
Recovered from Stripe$347.00
Recovra fee · 20%−$69.40
You kept$277.60
This sample case required zero merchant action.
AUDIT LEDGER
Every event, timestamped
Mar 27 · 09:14Dispute detectedLOGGED
Mar 27 · 09:16Evidence matched (6 of 6)LOGGED
Mar 27 · 09:16Decision: FIGHTLOGGED
Mar 27 · 09:18Response submitted to StripeLOGGED
Apr 14Deadline (18d margin)DEADLINE
Apr 22Stripe ruled: recoveredRECOVERED
THIS IS ONE SUPPORTED PATH
Same truth model.
Not every dispute follows this path.
Connect Stripe, finish activation, and supported cases can move forward automatically when evidence is sufficient. Cases with missing evidence surface for input instead of being submitted.