Definition
Net revenue impact of the intelligent retry strategy per retried transaction: capturing both revenue recovered and costs imposed by retry-generated side effects including network fines, duplicate authorizations, issuer velocity flags, and cardholder friction.
The Measurement Gap
The Measurement Gap
No metric tells you the total downstream cost of aggressive transaction retry logic. Retry success rate is the standard metric, and it tells a simple story: what percentage of retried transactions eventually approve. But retry success rate systematically overstates the value of retries by ignoring every cost that retries impose on the broader payment ecosystem.
When the orchestration platform retries a declined transaction (whether on the same processor or routed to an alternative) it initiates a cascade of potential side effects that no standard metric captures. Card networks (Visa, Mastercard) impose fines for excessive retry attempts that exceed published thresholds. Duplicate authorizations occur when both the original and retry settle, creating double-charge events that require manual reversal. Issuer-side velocity triggers activate when multiple authorization attempts hit the same card in rapid succession, potentially flagging the cardholder for fraud investigation. Cardholder friction manifests as confused calls to customer service when they see multiple pending charges or receive fraud alerts triggered by the retry pattern.
Each of these costs accumulates in a different system and a different line item. Network fines appear in the compliance report. Duplicate auth reversals appear in the operations report. Customer complaints appear in the service report. Nobody aggregates them against the revenue recovered by the retry strategy, which means the retry engine may be destroying more value through side effects than it recovers through successful retries, and the retry success rate dashboard shows only the upside.
Decision Supported
Is the retry strategy a net-positive investment when all downstream costs (network fines, duplicate auths, issuer penalties, cardholder friction) are included?
Formula
Plain Language
Take the total revenue recovered by successful retries, subtract all costs generated by the retry process (network fines, duplicate authorization costs, issuer penalties, and estimated cardholder friction costs), and divide by total retry attempts. The result is the net dollar value generated per retry.
Notation
RNIS = [Σ(TxnAmount_recovered × Margin) − (NetworkFines + DuplicateAuthCosts + IssuerPenalties + EstimatedFrictionCost)] / Total_retries
Variables
| Variable | Definition | Unit |
|---|---|---|
| TxnAmount_recovered | Dollar amount of successfully approved retry transactions | $ |
| Margin | Revenue margin per transaction (interchange + processing fee) | Ratio (0–1) |
| NetworkFines | Card network fees assessed for excessive retry attempts | $ |
| DuplicateAuthCosts | Costs of duplicate authorization holds requiring reversal | $ |
| IssuerPenalties | Velocity violation penalties from issuer-side rules | $ |
| EstimatedFrictionCost | Retry-triggered complaint rate multiplied by average resolution cost | $ |
| Total_retries | Total retry attempts in the measurement period | Count |
Proposed formula, pending validation pilots.