Vendor view · DisputeFlow
Scope & Rules
What this evaluation is and the buyer's locked criteria. You can't change them; every vendor faces the same ones.
- Evaluation · fictional sample
- CE 3.0 Chargeback Automation
- Vendor
- DisputeFlow
- Use case
- Chargeback automation
- Decision it informs
- Fictional buyer: whether DisputeFlow qualifies for a pilot, and what that pilot should cover.
Locked by the buyer
These requirements are locked. Every vendor faces this exact bar. Deal-breakers must be met; other misses are disclosed as conditions.
| Criterion | Target | Deal-breaker |
|---|---|---|
| ≥ 98% | Yes | |
| ≥ 99.5% | Yes | |
| ≤ 800 ms | No | |
| ≥ 150 cases/min | No | |
| ≥ 95% | No | |
| ≤ 1% | No |
Locked 2026-10-13 16:05:02 UTC. Nobody, including the buyer, can change these criteria.
simulation · how a vendor can respond to criteria before they are frozen.
Declared limits (sample)
What the vendor states it doesn't support, recorded before testing so gaps inside these limits aren't surprises.
- No support for legacy Discover dispute rails
- Maximum 200 concurrent cases per tenant
- English and Spanish case narratives only