Trydence

Chargeback automation · DisputeFlow

Sign in

Trydence · Evaluation report

Results

Assessment findings and next steps against buyer-locked criteria.

Evaluation
CE 3.0 Chargeback Automation
Evidence source
Illustrative sample, not measured
Example
EX-DF-01 · Sample assessment
Date
2026-10-14
Software version
Not recorded
Locked criteria
6 · c09a3fd84133…

Fictional completed assessment of “DisputeFlow”, with invented batch-level figures. The 24-case reference rehearsal is a separate measurement, not the source of these percentages.

Verdict

Conditional Fit

Deal-breakers

2 of 2 met

Criteria

4 of 6 met

Remaining gaps (2)

Every deal-breaker is met. The remaining gaps are disclosed as conditions rather than ending the deal.

  • Conditionp95 decision latency912 ms · target ≤ 800 ms
  • ConditionHuman escalation routing accuracy93.1% · target ≥ 95%

Recommended next step

Agree how the pilot covers each condition, for example a human review step or a fix date with a re-test.

Decision still required from the buyer

Whether the conditions are acceptable, and whether the pilot should test them directly.

Way forward

The findings stay unchanged. Use this simulated workflow to propose how a pilot could address the remaining gaps.

Simulation · EX-DF-01Planning status:Draft proposals · Not submitted· Verdict stays Conditional Fit

The vendor's proposals are drafts and have not been submitted for review yet.

Results by criterion

Each row compares the locked target with the example's observed value.

MetricAgreed targetObservedDeltaStatusDB
CE 3.0 eligibility accuracy>= 98%98.6%+0.6 ptsPass●
PII redaction recall>= 99.5%99.7%+0.2 ptsPass●
p95 decision latency<= 800 ms912 ms+112 msConditional
Throughput>= 150 cases/min171 cases/min+21 cases/minPass
Human escalation routing accuracy>= 95%93.1%-1.9 ptsConditional
Error rate<= 1%0.4%-0.6 ptsPass

Discrepancy analysis

2 metrics fell below the agreed acceptance standard.

p95 decision latency

Conditional

observed 912 ms · target <= 800 ms

Latency rose above target once concurrent load passed roughly 180 cases. Below that level, p95 stayed near 640 ms.

Within the vendor’s declared scope (“Maximum 200 concurrent cases per tenant”), so this miss counts.

Human escalation routing accuracy

Conditional

observed 93.1% · target >= 95%

In this fictional scenario, Spanish-language narratives with mixed merchant descriptors were sent to the automated queue instead of an analyst.

Within the vendor’s declared scope (English and Spanish), so this miss counts.

Evidence source: Fictional sample scenario, not a real vendor run

Buying committee briefings

Reviewer-specific summaries of the evaluation findings for executive, security and legal review.

A memo for Executive / CFO, written from the locked criteria and results.