Recovery Intelligence Help and Documentation

Learn how Zahlen turns decline records into retry guidance, explains each recommendation, compares recovery performance by code, issuer, country, and brand, and estimates the value associated with improved retry behavior.

Recovery Intelligence Overview

Recovery Intelligence explains the path from a declined transaction to a recommended retry action:

Decline → Retry Decision → Why?

The page uses tenant-scoped recovery observations to show what declined, what later recovered, when retries should occur, and how confident Zahlen is in the recommendation.

Recovery Summary Cards

DeclinesTotal decline records in the current tenant scope.
RecoveriesRecords that later recovered successfully.
Recovery RateRecoveries divided by declines.
Cards are summaries They describe the available recovery evidence. They are not buttons or filters.

Decision Explainability Panel

This panel explains one representative retry recommendation in detail.

It answers three operator questions:

  • Which decline is being evaluated?
  • What retry action does Zahlen recommend?
  • What evidence supports that recommendation?

Decision Explainability Fields

Order IDThe unique recovery observation or transaction reference.
Subscription IDThe subscription, merchant, or account context associated with the decline.
Processor Error CodeThe processor or Zahlen decision-output identifier.
Decline CodeThe numeric payment response code.
Decline DescriptionThe human-readable meaning assigned to the code.
Recovery ProbabilityThe calculated probability expressed as a decimal.
Recovery Probability LabelThe same probability displayed as a percentage.
Recommended Retry DayThe suggested day after the decline for the next retry.
Issuer RecommendationGuidance based on issuer-specific evidence.
Country RecommendationGuidance based on country-level evidence.
Brand RecommendationGuidance based on card-brand evidence.
Merchant RecommendationThe overall merchant-facing action.
ConfidenceThe strength of evidence supporting the recommendation.
Probability and recommendation are different concepts A displayed retry recommendation can exist even when observed recovery probability is currently 0%, especially when the available data represents initial declines and the configured decision policy still recommends a first retry.

Top Recovering Codes

This table compares decline codes by observed recovery performance.

Decline CodeThe payment response code.
Decline DescriptionThe governed human-readable explanation.
Recovery RateThe observed percentage that recovered.
RecoveredThe number of successful recoveries.
Retry DayThe recommended retry timing.
ConfidenceThe evidence-strength band.

Best Issuers

Ranks issuers by observed recovery performance.

The table uses Recovery Rate, Recovered count, Retry Day, and Confidence to explain each issuer's position.

“Best” is relative to available evidence When every issuer has a 0% recovery rate, the table is still structurally ranked, but it does not prove that any issuer currently outperforms another.

Best Countries

Compares recovery performance by country.

Use it to determine whether recovery timing or success differs geographically once enough recovered observations exist.

Best Brands

Compares recovery performance by payment-card brand.

This can reveal whether recovery behavior differs between brands such as Visa and Mastercard after sufficient retry outcomes have been observed.

Recommended Retry Actions

Converts recovery evidence into operator-facing retry guidance.

ActionThe recommended action and timing, such as RETRY Day 1.
ReasonThe evidence category supporting the action.
ConfidenceHow strongly the evidence supports the recommendation.
Expected RecoveryThe estimated recovery effect, when available.
Not available When Expected Recovery says “Not available,” Zahlen does not yet have enough observed outcome evidence to quantify the likely benefit.

Expected Revenue Recovery

This section connects recovery behavior to potential economic value.

Total DeclinesTenant-scoped decline observations.
Total RecoveriesRecovered observations in scope.
Observed Recovery RateRecovered observations divided by declines.
This version does not display a currency amount The section currently provides the recovery-volume foundation. A monetary estimate would require transaction-value or subscription-revenue data.

How to Interpret Zero Recovery

The supplied page shows 10,000 declines and zero recoveries. This is expected when the current scope contains an initial-decline file but not later retry outcomes.

In that situation:

  • Recovery Rate remains 0%.
  • Recovered counts remain zero.
  • Expected Recovery may be unavailable.
  • Retry guidance may still show the configured or evidence-supported first retry day.
  • Later retry files are needed to calculate actual recovery performance.
Do not treat 0% as a final issuer judgment Confirm whether the current data includes retry outcomes before concluding that a code, issuer, country, or brand never recovers.

Recommended Recovery Intelligence Workflow

  1. Review Declines, Recoveries, and Recovery Rate.
  2. Read the Decision Explainability Panel.
  3. Confirm the decline code and description.
  4. Compare issuer, country, brand, and merchant recommendations.
  5. Review Confidence before acting.
  6. Inspect Top Recovering Codes.
  7. Compare issuer, country, and brand performance.
  8. Review Recommended Retry Actions.
  9. Confirm whether Expected Recovery is available.
  10. Verify that later retry outcomes exist before interpreting zero recovery as final.