“You cannot control what you cannot measure”
This applies directly to payments. The payments stack is growing more complex, and the margin for visibility gaps is shrinking. Cash flows have a direct impact on the bottom line, and accountability in payments is not optional.
When customers on your platform click Pay Now, it signals more than a transaction. It reflects trust, intent, and the potential for lifetime value. Yet payment failures and inefficiencies silently erode revenue and inflate operational costs, often without clear financial visibility.
The scale of the problem is significant. Globally, failed payments cost businesses an estimated $118.5 billion every year. For a digital platform with Rs. 10 crore in monthly GMV, an 8% failure rate means Rs. 80 lakh in blocked revenue per month, not because of demand issues but because of infrastructure gaps that proper metric tracking can identify and fix.
For digital platforms in e-commerce and fintech, tracking payment performance is how finance teams quantify leakage, control costs, and protect profitability. Here are the 7 payment metrics and payment KPIs every finance leader should monitor, report, and act on.
1. Payment Success Rate (%)
Payment success rate measures the percentage of payment attempts that result in completed transactions. A high success rate directly correlates with higher realised revenue and a better customer experience.
Formula: Payment Success Rate (%) = (Successful Transactions / Total Payment Attempts) x 100
Example: 10,000 attempts, 9,200 succeed = 92% success rate. At Rs. 1,200 AOV, this is Rs. 1.10 crore in revenue. A drop to 85% costs Rs. 8.4 lakhs monthly.
Track: Daily for real-time trends. Weekly to compare by payment method and gateway.
Decision Trigger: Investigate gateways, issuers, or payment methods contributing to dips. Consider smart routing via a payment orchestration layer.
Benchmark: A payment success rate above 95% is considered strong for most digital commerce platforms. Rates between 90% and 95% indicate room for optimisation. Rates below 90% represent material revenue leakage requiring immediate infrastructure review.
2. Payment Failure Rate (%)
The payment failure rate captures the proportion of attempts that do not complete. Each failure represents lost sales, abandoned carts, and higher support volume.
Formula: Payment Failure Rate (%) = (Failed Transactions / Total Payment Attempts) x 100
Example: 8% failure on 10,000 attempts at Rs. 1,200 AOV = Rs. 9.6 lakhs in potential revenue lost every month.
Track: Daily and weekly to catch sudden spikes early.
Decision Trigger: Identify root cause: customer errors, bank downtimes, payment gateway issues, or mobile UX friction. Each failure reason requires a different fix.
Benchmark: An 8% failure rate is materially damaging. Industry top performers target failure rates below 5%. Failure rates above 10% are a structural infrastructure problem, not a normal operating condition.
3. Acceptance Rate (%)
Acceptance rate measures the percentage of payment transactions successfully approved or authorised by issuers or PSPs out of total attempts. This is distinct from success rate, which includes all post-authorisation steps.
Formula: Acceptance Rate (%) = (Approved Transactions / Total Transaction Attempts) x 100
Example: 9,000 authorised out of 10,000 attempted = 90% acceptance rate.
Track: Daily. Compare by payment method, issuer bank, and geography.
Decision Trigger: A low acceptance rate with high attempt volume points to issuer-side friction. Use this data to negotiate with bank partners or route traffic to higher-performing payment rails.
Key distinction: acceptance rate measures issuer-side approval. Success rate measures end-to-end completion. A transaction can be accepted by the issuer but still fail during processing, which is why acceptance rate is typically higher than success rate. Tracking both together reveals whether failures are issuer-side or platform-side.
4. Revenue Lost to Payment Failures (Rs.)
This metric converts the failure rate into a rupee figure, making the business impact visible to leadership and justifying investment in better infrastructure.
Formula: Revenue Lost = Number of Failed Transactions x Average Order Value
Example: 8% failure on 10,000 transactions at Rs. 1,200 AOV = Rs. 9.6 lakhs in lost revenue per month.
Track: Monthly for cumulative impact reporting. Include in board-level financial dashboards.
Decision Trigger: Use this number to build the business case for payment orchestration, smarter retry logic, or gateway diversification. This is the metric that turns infrastructure investment from a technical request into a finance decision.
5. Revenue Recovery Rate (%)
Not every failed payment is a permanent loss. The recovery rate tracks what percentage of failed transactions were successfully retried and completed, making it a direct measure of your retry and recovery infrastructure.
Formula: Revenue Recovery Rate (%) = (Recovered Transactions / Total Failed Transactions) x 100
Example: 800 failures, 400 recovered = 50% recovery rate, equating to Rs. 4.8 lakhs in salvaged revenue.
Track: Weekly and monthly to monitor retry strategy effectiveness.
Decision Trigger: Low recovery rates signal the need for auto-retries, alternative payment method prompts, or improved failure communication to the customer.
Benchmark: Industry top performers recover between 40% and 70% of failed transactions through automated retry logic. A recovery rate below 20% signals the absence of any meaningful retry infrastructure. For subscription platforms, a low recovery rate is the primary driver of involuntary churn, where customers are lost not because they chose to leave but because their renewal payment silently failed. Industry data shows up to 40% of subscriber loss stems from this cause.
6. Payment Gateway Cost per Transaction (Rs. / %)
Gateway fees are often invisible in the P&L until they accumulate. This metric makes the cost of each successful transaction explicit, enabling finance teams to optimise gateway selection and negotiate better rates.
Formula: PG Cost per Transaction = Total Gateway Fees / Total Successful Transactions
Example: Rs. 18 fee on Rs. 1,200 transaction = 1.5% per transaction. Across 9,200 transactions = Rs. 1.65 lakhs in monthly gateway fees.
Track: Monthly, broken down by gateway.
Decision Trigger: If payment gateway cost is high relative to success rates, renegotiate fees or diversify gateway usage through intelligent routing to lower-cost rails.
Benchmark: Standard MDR (Merchant Discount Rate) for card payments in India ranges from 1.5% to 2.5%. UPI transactions currently have zero MDR for most merchants, making UPI routing a direct
cost lever. PG costs above 2% on a high-volume platform represent a significant opportunity for renegotiation or routing optimisation.
7. Refund and Chargeback Rate (%)
This metric captures the percentage of completed transactions subsequently reversed through refunds or chargebacks. High rates signal customer dissatisfaction, product issues, or fraud exposure.
Formula: Refund and Chargeback Rate (%) = (Refunded or Charged-back Transactions / Total Successful Transactions) x 100
Example: 180 out of 9,200 transactions refunded = 1.95% rate, amounting to Rs. 2.16 lakhs in lost revenue.
Track: Weekly for B2C platforms. Monthly for B2B.
Decision Trigger: Rising chargeback rates should prompt a review of fraud controls, billing descriptor clarity, product quality, and customer support response time. Monitor by reason code to distinguish fraud-driven chargebacks from service-driven ones.
Benchmark: Keep chargeback rate below 0.6%. Visa’s monitoring programme activates above 0.65%, and Adyen suspends merchant accounts above 0.5%. The industry standard danger threshold is 1%. Globally, chargebacks will cost ecommerce $33.79 billion in 2025, projected to reach $41.69 billion by 2028 (Chargeflow, 2025). Friendly fraud now accounts for 75% of all chargeback cases.
Bonus Metrics
Bonus 1. Cost per Payment Failure (Rs.)
Beyond lost revenue, each failed payment carries operational costs including support tickets, reconciliation effort, and processing overhead.
Formula: Cost per Payment Failure = Total Operational Cost of Failures / Total Number of Failed Transactions
Example: Rs. 40,000 spent managing 800 failures = Rs. 50 per failure.
Decision Trigger: Rising cost per failure builds the case for automating support, streamlining payment reconciliation, or fixing core payment infrastructure issues.
Bonus 2. Time to Settlement (Days / Hours)
Time to settlement is the duration between a customer completing a payment and the merchant receiving funds. For UPI, this is near real-time. For card payments, it is typically T+1 to T+3 days.
Formula: Time to Settlement = Settlement Date minus Transaction Date
Example: UPI: near real-time. Cards: T+1 to T+3 depending on acquiring bank.
Decision Trigger: Delays affect cash flow liquidity and increase reconciliation complexity. Monitor by payment method to identify which rails create bottlenecks.
Bonus 3. Dispute Win Rate (%)
Dispute win rate measures the percentage of chargeback disputes your team successfully contests and wins. This metric matters because losing a chargeback does not just mean losing the transaction value. It means losing the chargeback fee and eroding your standing with card networks.
Formula: Dispute Win Rate (%) = (Disputes Won / Total Disputes Contested) x 100
Example: 60 disputes won out of 100 contested = 60% win rate.
Decision Trigger: AI-assisted evidence collection boosts dispute win rates by at least 25% (Ethoca, 2025). A win rate below 40% signals weak dispute documentation processes.
Bonus 4. Settlement Accuracy (%)
Settlement accuracy compares the funds actually deposited in your bank against what gateway and processor reports say should have arrived. Discrepancies caused by misapplied fees, delayed payouts, or ledger mismatches are a major source of hidden revenue leakage that most finance teams underestimate.
Formula: Settlement Accuracy (%) = (Actual Settlement Amount / Expected Settlement Amount) x 100
Example: Rs. 9,82,000 deposited vs Rs. 10,00,000 expected = 98.2% accuracy. The 1.8% gap represents Rs. 18,000 in unreconciled funds.
Decision Trigger: Accuracy below 99% should trigger an immediate audit of fee structures, reserve adjustments, and payout timing across all PSPs.
Making Metrics Actionable: Track by Segment
High-level metrics like ‘overall payment success rate’ compress the complexity of your entire payment ecosystem into a single number that is too broad to act on. The most impactful finance teams break each metric down by the following dimensions:
* Payment method: UPI vs card vs wallet vs net banking. Each has different failure patterns and cost structures.
* Gateway: Compare success rates across PSP A, PSP B, and PSP C to identify underperformers.
* Geography: Metro vs Tier 2 vs Tier 3 cities often show material differences in UPI success rates.
* Device: Mobile payment failure rates are typically 2 to 4 percentage points higher than desktop due to network variability and UI friction.
* Time of day: Bank-side declines spike during peak load periods such as salary dates and festive season sales.
A payment health dashboard that segments these dimensions in real time converts metric monitoring from a monthly reporting exercise into a daily operational tool.
Reporting and Decision Framework
Finance teams should integrate these payment metrics into monthly performance reviews, ensuring alignment with product, operations, and growth teams. A payment health dashboard centralises this visibility for both real-time monitoring and strategic decision-making.
Metric |
Track Frequency |
Key Finance Actions |
|---|---|---|
| Payment Success Rate, Failure Rate, Acceptance Rate | Daily, Weekly | Monitor for trends; trigger gateway and bank optimisations |
| Revenue Lost to Payment Failures | Monthly | Build ROI cases for infrastructure improvements |
| Revenue Recovery Rate | Weekly, Monthly | Improve retry strategies; introduce alternative payment methods |
| Payment Gateway Cost per Transaction | Monthly | Optimise payment mix; renegotiate gateway fees |
| Refund and Chargeback Rate | Weekly (B2C), Monthly (B2B) | Strengthen fraud detection; review product quality |
| Cost per Payment Failure | Monthly | Automate support; optimise operational costs |
| Dispute Win Rate | Monthly | Improve evidence documentation; consider AI-assisted tools |
| Settlement Accuracy | Monthly | Audit fee structures; reconcile PSP and bank reports |
Conclusion
Payments are the frontline of revenue capture, not a backend function. For finance teams, tracking these payment metrics and KPIs provides a strategic lever to recover lost revenue, control payment gateway costs, reduce chargebacks, and enhance customer experience.
Every payment failure is not just a missed transaction. It is a missed opportunity to grow. The platforms that instrument their payment performance correctly are the ones that turn payments from a cost centre into a competitive advantage.
