RECLAIMâ„¢ Framework

Retail Commerce Leakage Assessment and Intervention Model.

A practical operating model for identifying, measuring, prioritizing, and reducing payment-related revenue leakage across ecommerce, mobile apps, and omnichannel retail.

Definition

Retail payment leakage is the measurable loss of earned or earnable revenue between customer purchase intent and final retained settlement.

The core idea: retailers do not only lose revenue because customers say no. They lose revenue after customers say yes.

The nine RECLAIM pillars

PillarLeakage typeExample metric
1Intent LeakagePayment-step abandonment
2Tender Fit LeakagePreferred tender coverage
3Authorization LeakageApproval rate and false decline estimate
4Authentication Leakage3DS, OTP, or login completion
5Recovery LeakageFailed-payment recovery value
6Fraud & Abuse LeakageFraud loss, chargebacks, false positives
7Loyalty & Stored Value LeakageSuspicious redemption and promo abuse
8Settlement & Fee LeakageFee variance and reconciliation breaks
9Omnichannel Operations LeakageBOPIS payment cancellations and refund mismatches

Maturity model

LevelNameDescription
1ReactiveIssues are found through complaints, finance misses, fraud spikes, or outage reports.
2VisibleBasic dashboards exist, but metrics are siloed across payments, fraud, product, and finance.
3ManagedLeakage is measured by pillar, ownership exists, and recurring reviews happen.
4OptimizedTeams actively test routing, recovery, authentication, fraud rules, checkout UX, and settlement controls.
5PredictiveLeakage is forecast, benchmarked, automated, and treated as a revenue growth discipline.

Scoring method

Each pillar is scored across five dimensions: visibility, measurement, ownership, control, and optimization. Each dimension is scored from 0 to 4. Each pillar has a maximum score of 20. The total RECLAIM score is the sum of all pillar scores divided by 180.

ScoreRating
0 to 25High Leakage Risk
26 to 50Fragmented Control
51 to 70Managed but Leaky
71 to 85Advanced
86 to 100Leakage Leader

Recommended actions by maturity level

  • Level 1: Build the leakage map and define common terms.
  • Level 2: Create dashboards by pillar and assign cross-functional owners.
  • Level 3: Quantify dollar impact and prioritize the top leakage pools.
  • Level 4: Run controlled experiments across routing, UX, fraud, recovery, and tender mix.
  • Level 5: Build predictive monitoring, benchmarks, and automated intervention.
Open industry resource

Help define the Retail Payment Leakage Benchmark.

Retailers, payment providers, fraud leaders, consultants, and commerce technology professionals are invited to contribute feedback and participate in the benchmark.

Participate in the Benchmark