Key takeaways
- Gross sales are not the same as realized payment economics when card fees, refunds, chargebacks, failed payments, and reserves are material.
- Payment method mix can change margin even when customer demand is stable.
- Chargebacks should be reviewed by reason code, channel, location, product, and customer type because the fix depends on the cause.
- Processor reserves and settlement timing can create working-capital pressure that is invisible in revenue reporting.
- Buyers test payment economics when card volume is high because leakage affects EBITDA, cash conversion, and customer quality.
A business can grow gross sales while quietly giving up more economics between the customer payment and the bank deposit. Card fees rise, card-not-present volume increases, refunds accelerate, chargebacks cluster in one channel, or the processor holds reserves after a risk review. The P&L may show revenue growth, but cash and margin tell a more complicated story.
For adjacent context, compare this with Contract Billing Leakage, Treasury Authority and Bank Signer Controls, and Customer Profitability vs. Customer Revenue. Those articles cover invoice completeness, cash-movement controls, and account-level economics; this article focuses on payment acceptance leakage below gross sales.
This matters most in consumer services, healthcare, memberships, e-commerce, home services, events, education, and any business where card payments represent a meaningful share of collections. Payment acceptance is not only a customer convenience decision. It is a margin, controls, and working-capital issue.
Payment leakage is the difference between gross customer demand and the net cash the business keeps after fees, refunds, disputes, failed payments, and reserves.
Gross sales
Customer purchases before payment costs and reversals
Processor fees
Interchange, assessments, processor markup, gateway, and monthly fees
Chargebacks
Customer disputes that reverse cash and add fees or monitoring risk
Net payment realization
Cash retained after refunds, disputes, fees, failed payments, and reserves
The payment leakage bridge
The cleanest way to manage payment economics is to build a bridge from gross sales to net cash collected. Start with gross card volume, then subtract refunds, chargebacks, processor fees, gateway fees, reserve holds, failed payment losses, and settlement timing differences. The bridge should be reviewed by channel and location, not only in total.
Payment method mix is often the hidden driver. A business that shifts from ACH or invoice payment to card payment may improve customer conversion but reduce contribution margin. A business that moves from card-present to card-not-present may see higher authorization friction, fraud exposure, and dispute rates. Those tradeoffs should be visible before management changes pricing or channel strategy.
What buyers test
Buyers ask for payment processor statements when payment costs are material because those statements show behavior that revenue reports can hide. They reveal fee rates, dispute activity, reserve balances, settlement timing, refunds, and sometimes channel mix. A seller that can reconcile those statements to revenue and cash receipts reduces uncertainty.
The diligence question is not whether card fees exist. The question is whether payment costs are understood, whether chargebacks are controlled, whether reserves are temporary or recurring, and whether reported revenue converts into cash at a stable rate.
A $24M multi-location consumer services company reported strong revenue growth, but payment analysis showed that online card-not-present volume had increased materially, processor fees were up, and refund plus chargeback rates had doubled in one channel.
The issue did not eliminate the growth story, but it changed the margin bridge.
Management separated gross demand from net cash realization, tightened cancellation documentation, and added channel-level payment KPIs before buyer diligence.
Frequently asked questions
When does merchant processing deserve its own review?
When card payments are material to collections, when online or card-not-present volume is growing, when refunds or disputes are increasing, or when processor reserves appear on the balance sheet.
What documents should be prepared?
Processor statements, gateway reports, refund logs, chargeback reports by reason code, settlement reconciliations, reserve balances, and payment method mix by channel.
Can card fees be passed through?
Sometimes, depending on state law, card network rules, customer contracts, and customer tolerance. The operating point is to model the economics before changing payment policy.
Work with Glacier Lake Partners
Analyze payment leakage
We help businesses connect gross sales, payment method mix, processor fees, chargebacks, reserves, refunds, and net cash collection into a practical margin view.
Explore Operational Advisory →Operating workflow scan
Find the reporting or execution workflow worth automating first.
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Research sources
Disclaimer: Financial figures and case-study details in this article are anonymized, composite, or representative examples based on middle market operating situations, and are not guarantees of outcome. Statistical references are drawn from cited third-party research; individual transaction and operational results vary based on business characteristics, market conditions, and deal structure. This content is for informational purposes only and does not constitute legal, financial, or investment advice. Consult qualified advisors for guidance specific to your situation.
Explore adjacent topics
