A CFO’s guide to measuring payment leakage across the P&L

Finance can see what the business pays its payments providers. What is much harder to see is what payments cost the business as a whole.

Payment performance affects how much customer demand converts, how effectively acquisition spend works, and how much time Tech and Operations teams spend maintaining the infrastructure. When a provider underperforms, it can also put sales and customer relationships at risk.

For enterprise merchants, these effects sit across several budgets and reporting systems. Bringing them together gives Finance a clearer basis for deciding where to reduce costs, improve performance and invest.

What is the total cost of accepting payments?

The total cost of payments goes well beyond what a business pays its PSPs and acquirers and the internal resources needed to support them. A wider economic impact also considers the effect of payment performance on revenue, customer value and exposure to disruption.

To identify the total cost of payments, start by distinguishing what the business spends from what it could recover or protect.

This guide examines five key areas:

• Processing and provider costs: Charges for payment services, including fees that may apply when an attempt fails or is retried.
• Revenue conversion: The commercial opportunity from reducing avoidable payment failures.
• Customer value: The effect of payment experiences on first purchases, repeat business and retention.
• Operating costs: The resources required to maintain integrations, manage providers and support payment operations.
• Resilience: The value at risk when payment services become unavailable or perform below expectations.

Some of these are recorded expenses; others represent missed opportunities or potential losses. For example, revenue affected during an outage may also appear in the analysis of failed payments and should be counted once.

A declined payment may incur processing charges without representing recoverable revenue. Equally, a successful payment is not always revenue: an iGaming deposit, for example, needs to be assessed through the gaming activity and revenue it supports.

The purpose is to identify which costs and outcomes the business can influence, then assess their commercial significance.

Key Takeaways

• Payment fees tell only part of the story. Payment performance also affects revenue, acquisition efficiency, customer retention, operating costs and exposure to disruption.
• Include the cost of failed attempts. Cost per successful payment shows what you spend to achieve a completed payment, including fees for unsuccessful attempts and retries.
• Lower fees only help if the overall economics improve. For the volume being moved, compare the processing savings with any impact on conversion, contribution and operational workload.
• Focus on the payment failures you can influence. Use your own data to identify credible recovery opportunities, account for customers who complete another way and assess the resulting commercial value.
• Assess the effects together without counting them twice. The same failure can appear in conversion, customer-value and disruption analysis.
• Orchestration can improve the economics where there is a clear opportunity. Its net value depends on the problems it addresses, the full cost of change and how actively it is managed.

Where does the total cost of payments appear across the P&L?

Payment fees are usually easy to identify. The wider effects are harder to connect because different teams measure them for different purposes.

Payments track approval rates. Marketing measures acquisition and retention. Technology manages development capacity. Finance sees the resulting expenditure and commercial performance but may not have a consistent view of how payments contribute to either.

The table below shows where to look. The accounting treatment will depend on the business; customer value and resilience exposure are analytical measures rather than separate P&L lines.

How provider fees can affect the wider business

Consider an iGaming operator that moves UK card deposits to an acquirer offering lower fees. On paper, the decision works. A saving is applied to the volume moved. Whether the change improves the overall economics depends on what happens next.

If approval rates fall for some issuers, fewer deposits may complete and the economics change. If affected customers abandon rather than try again, the operator could lose that revenue.

The change may require integration and reconciliation work. And if it leaves the operator more dependent on one acquirer, more payment volume could be exposed when that provider has a problem.

These outcomes are not inevitable. They are the factors that need to be assessed alongside the initial fee saving. The decision is whether moving that volume improves the business’s overall return, after allowing for performance, operational effort and risk.

Bring the measures together

Each team can meet its own objectives while the wider economics deteriorate. Procurement may secure a lower rate while Operations takes on more manual work. Payments may improve approvals through retries that also increase processing charges.

Finance and Payments teams therefore need a shared view of the same transaction information, covering cost, successful transactions, recovery and commercial value. That makes the trade-offs visible before saving in one area creates a higher cost elsewhere.

Processing and provider costs: How should enterprises measure payment processing costs?

Start with the full cost of processing payments, including charges associated with successful transactions, unsuccessful attempts and retries. Then compare those costs by market, payment method, provider and route.

A headline provider rate is useful for procurement, but it does not show the full cost of achieving a completed payment.

Include the charges associated with payment attempts

Depending on the contract and payment flow, costs can include:

• PSP and gateway fees.
• Authorisation and authentication charges, including 3DS.
• Acquiring, interchange and scheme fees where applicable.
• FX and cross-border charges.
• Additional fees incurred through retries.

Not every fee applies to every attempt. Finance should use contractual terms and actual billing data to establish which charges apply when payments succeed, fail or are retried.

The location of acquiring also matters. Domestic acquiring can change both processing costs and approval performance, but the benefit should be assessed for the relevant market and card population.

Measure cost per successful payment

To understand what it costs to complete a payment, including the fees paid for unsuccessful attempts and retries.

For example, if you spend £10,000 processing payments and 5,000 payments complete, the cost per successful payment is £2. The £10,000 includes any fees charged for failed attempts and retries. A payment that succeeds after three attempts counts as one complete payment.

This helps explain why a provider with lower fees may still cost more overall: if few payments succeed, you spend more to achieve each completed payment.

When comparing providers, use similar payment types and values over the same period. Domestic debit payments and cross-border credit payments have different costs, so comparing them directly can give misleading results.

Assess fee savings alongside conversion

Routing through a cheaper provider makes commercial sense when the saving outweighs any reduction in contribution and any additional operating costs.

The practical comparison is straightforward: calculate the saving on the volume being moved, then assess whether the change affects successful completion, recovery, customer behaviour or internal workload.

If performance deteriorates, establish how many affected customers complete another way before assigning a revenue impact. Translate any remaining gap using the economics of the business, rather than treating failed payment value as lost revenue.

A lower rate is a useful saving only when the wider payment economics support it.That is why processing cost and payment performance should be reviewed together.

The revenue cost: What happens when payment intent does not convert?

A failed payment tells you that an attempt did not complete. Understanding its commercial impact requires knowing why it failed, whether the customer completed another way and what could have changed the outcome.

The opportunity lies in failures you can reasonably influence. These might include a provider performing poorly for particular issuers, an authentication problem or a recoverable decline that never receives an appropriate retry.

Separate the causes before assessing the opportunity

Different causes require different responses. Authentication failure, for example, needs a different approach from a customer abandoning checkout because their preferred payment method is missing.

These are areas to investigate, rather than guaranteed recovery opportunities. A different route cannot make every payment succeed, and repeated attempts can add cost without improving the outcome.

Use your own performance as the starting point

Your transaction data can show where a credible improvement opportunity exists.

Compare performance for similar traffic across providers or periods. Match the characteristics that influence approval, including market, issuer, card type, transaction type and authentication treatment.

A higher approval rate elsewhere is a useful signal. It is not proof that moving the traffic will reproduce the result. Provider selection, customer mix and timing can all affect the comparison.

For a suitably matched segment, an initial estimate is:

Using a value-based rate keeps the calculation consistent. If you use an approval rate based on transaction counts, estimate the additional successful transactions first, then apply an appropriate transaction value.

The result identifies payment value to investigate. To assess the commercial opportunity, allow for customers who complete another way and apply your business’s revenue and contribution assumptions.

Why small gaps matter at enterprise scale

An illustrative one-percentage-point improvement across £2bn of eligible attempted payment value represents £20m of additional completed payments, before adjusting for recovery elsewhere or translating that value into revenue.

For an iGaming operator, deposits support gaming activity rather than becoming revenue directly. For a ticketing business, the impact depends partly on whether another customer buys the ticket. For a subscription business, successful recovery may preserve an ongoing relationship.

The useful measure is the additional commercial value the business could retain, after accounting for what happens beyond the payment attempt.

Acquisition and retention: How does payment performance affect customer value?

By the time a customer reaches payment, the business may already have invested in advertising, promotions and the purchase journey. An avoidable payment failure can reduce the return on that investment.

The effect extends beyond the immediate transaction, particularly when it happens at the start of a customer relationship or interrupts an established one.

The first payment

A first-payment failure can prevent an acquired customer from becoming a paying customer.

In iGaming, that may happen at the first deposit. In ticketing, a customer may lose confidence or purchase elsewhere. The acquisition spend remains, but the expected commercial return may never follow.

That does not mean assigning the full acquisition cost to every failed attempt. Some customers retry successfully or use another method. The relevant question is whether customers who experience failure are less likely to convert and remain active.

Repeat payments

For returning customers, payment failure can interrupt repeat purchases or recurring services.

Stored credentials, card updates and appropriate retry strategies can help in some circumstances. Their value depends on the reason for failure and whether the customer can and wants to continue paying.

Payment-method availability matters too. A technically reliable checkout can still lose customers if it does not offer a method they are willing to use, particularly in a new market.

Measure the customer outcome

Compare customers who experience payment failure with similar customers whose payments complete. Look at subsequent conversion, repeat purchase, retention and contribution.

Allow for differences in acquisition channel, market and customer behaviour. An observed gap is a starting point for investigation; it does not establish that payment failure caused the entire difference.

Also check for overlap with the revenue-conversion analysis. If the immediate lost purchase is already included there, count only the additional customer impact here.

Customer value strengthens the payment economics case when it comes from observed behaviour and avoids counting the same loss twice.

Operating cost: What does the payment infrastructure require from the business?

Payment infrastructure consumes resources across Technology, Operations, Finance and Support. Provider invoices capture only part of that expenditure.

The work can include maintaining integrations, testing changes, reconciling transactions, investigating discrepancies, handling customer queries and responding to incidents. As the business adds providers and markets, the workload can grow even when transaction pricing improves.

Distinguish expenditure from capacity

Some improvements create identifiable savings, such as reducing external development work or removing a service the business no longer needs.

Others release time from existing teams. That time has value, but it does not automatically reduce expenditure.

If engineers spend less time maintaining payment integrations, the benefit may be faster delivery of product improvements. If Operations spends less time investigating discrepancies, it may support more volume without adding resources.

Finance should distinguish those outcomes clearly: expenditure removed, capacity released, and future costs avoided.

Assess what the work delays

Two measures help make the burden visible:

• The time teams spend maintaining and supporting payments.
• The lead time required to introduce a provider, payment method or routing change.

Where that work delays a launch, establish which parts of the delay payments actually caused. Attribute the commercial effect accordingly.

A stronger business case explains how released capacity will be used and who owns the resulting outcome. “Less integration work” becomes more meaningful when it supports a defined market launch or reduces an evidenced operational bottleneck.

Resilience: How should Finance assess payment disruption?

A provider can remain available while payment performance deteriorates. Approval rates may fall, responses may slow or authentication may become unreliable.

The commercial impact depends on the affected traffic, the severity of the problem and how quickly the business can respond.

Measure the effect, not just availability

Separate three questions:

1. What changed? Identify the outage or deterioration against an appropriate baseline.
2. What was affected? Establish the payment population and value exposed during the incident.
3. What happened afterwards? Measure rerouting, retries, later completion and abandonment.

This distinguishes payment value at risk from realised commercial loss.

Traffic passing through an affected provider is not automatically lost. Some payments may still complete, while others recover through another route or later attempt.

Response time changes the economics

Detecting a problem is useful only if the business can act.

An alternative provider needs to be available, configured and able to handle the relevant traffic. Stored credentials, authentication requirements and operational processes can all affect whether rerouting is practical.

Finance should therefore assess both the ability to detect deterioration and the time required to restore acceptable performance.

Incident losses may already appear in the conversion analysis. Record them consistently, then use the resilience assessment to understand exposure and response capability.

The wider commercial role of this capability is explored in The business value of payments resilience.

Why should payment costs be assessed together?

A payment change can improve one measure while weakening another. Reviewing each cost independently can conceal the overall result.

Four issues deserve particular attention.

Trade-offs. Lower provider fees may come with weaker conversion. Additional retries may recover payments while increasing charges. Assess the contribution retained after the associated costs.

Double-counting. The same failed purchase can appear in conversion, customer-value and incident analysis. Use a consistent attribution method so it is counted once.

Cost transfers. A provider change may reduce fees while increasing reconciliation or development work. Include the teams that will carry that workload.

Fragmented materiality. Several small effects may sit below individual review thresholds but become material when considered together. A shared view makes that combined impact visible.

Assess each provider’s role in the wider strategy

The cheapest provider is not necessarily the best choice for every transaction.

A more expensive route may perform better for a valuable customer segment. A secondary provider may justify its cost by offering a usable alternative during disruption. A new payment method may support growth in a market where cards alone perform poorly.

Each should be assessed against the role it serves, the value it supports and the cost of maintaining it.

The objective is to improve the economics of the payment strategy as a whole.

How can Finance and Payments establish a shared commercial view?

A shared view starts with consistent definitions and data that both teams can reconcile.

It should answer four questions:

Agree the definitions before combining the numbers

Define an attempt, a completed payment and a recovered payment consistently. Agree the reporting period and how costs are allocated.

Track the customer’s eventual outcome where possible. Several attempts may relate to one purchase, and an initial decline may later recover successfully.

Provider data can use different codes and conventions. Resolving those differences makes comparisons more useful and prevents apparent improvements caused by inconsistent reporting.

Keep the baseline current

Review the baseline at a cadence that suits the business, with additional checks around major launches, provider changes and peak trading periods.

External benchmarks can help identify questions to investigate. Internal evidence and controlled tests should establish what improvement is credible for your business.

This creates the foundation for Building the Internal Business Case for Payment Orchestration, where the opportunity is assessed alongside the full cost of change.

Where can payment orchestration improve the economics?

Payment orchestration connects providers and gives merchants a way to coordinate payment processing across them. Depending on the platform and configuration, that can include routing, recovery, monitoring and provider management.

Its commercial value depends on the problems it can address in your existing setup.

Multiple providers need active management

Adding providers creates options. Commercial value comes from using those options effectively.

That requires comparable data, appropriate rules and ongoing review. Routing decisions should reflect both processing cost and successful completion. Recovery should follow applicable rules and avoid unnecessary attempts. Alternative routes need testing before the business depends on them.

Provider and issuer performance can also change. Wider market intelligence may help identify patterns to investigate, but your own traffic should establish whether a proposed change improves results.

This is the commercial opportunity explored in Why payment orchestration is the most underused revenue lever for enterprise merchants.

Include the cost of orchestration itself

Any saving or improvement must be assessed alongside platform fees, implementation, migration, testing and ongoing management.

Some existing costs will remain. Others may fall only after a transition period. Capacity benefits also need a realistic plan for how that time will be used.

The relevant comparison is the expected net benefit against the other credible options available to the business.

What can payment orchestration not solve?

Orchestration gives merchants more control over processing, but it cannot resolve every cause of payment failure or commercial underperformance.

It cannot make an invalid payment legitimate, guarantee issuer approval or ensure a customer has funds available. Some circumstances may support a later attempt or another method, but recovery must remain appropriate and permitted.

It also cannot:

• Renegotiate provider contracts automatically.
• Replace a sound fraud strategy.
• Resolve product, pricing or customer-demand problems.
• Guarantee that additional payment methods improve conversion.
• Remove every integration, reconciliation or compliance task.
• Deliver sustained improvement without effective configuration and ownership.

These limits belong in the economic assessment. A credible case identifies where orchestration can improve outcomes, where other action is needed and which benefits remain uncertain.

Turning payment performance into a commercial decision

The processing bill is an important starting point. The fuller picture comes from connecting it to successful payments, customer outcomes, operational workload and disruption.

That view helps Finance and Payments identify which improvements deserve attention and which apparent savings weaken the overall result.

The strongest payment strategy makes those trade-offs visible and gives the business a practical way to act on them.

FAQs

What is the total cost of accepting payments?

It includes provider and processing charges, together with the internal resources required to operate payment services. A wider economic assessment also examines avoidable payment failures, customer outcomes and disruption. These effects should be measured separately before combining them, because missed revenue and value at risk are not recorded expenses and may overlap.

Do unsuccessful payments incur fees?

They can. Gateway, authorisation, authentication and other charges may apply even when a payment does not complete. Retries may incur further fees. The exact treatment depends on the contract and payment flow, so the assessment should use actual billing data and agreed terms.

What is cost per successful payment?

It is the processing and provider cost associated with a defined payment population, divided by the number of completed payments in that population. Include relevant failed-attempt and retry charges. Use it alongside transaction value and payment mix to make fair comparisons.

Should every failed payment be treated as lost revenue?

No. Some failures cannot reasonably be recovered, and others complete through another attempt or method. Payment value also differs from revenue in business models such as iGaming and marketplaces. Assess the final customer outcome and translate any remaining gap into the appropriate revenue or contribution measure.

How does payment performance affect acquisition costs?

A payment failure does not change the acquisition spend already incurred. It can reduce the number of acquired customers who become paying customers, affecting the return on that spend. Measure the relationship using comparable customer cohorts and account for subsequent recovery.

How should Finance measure payment disruption?

Assess the affected payment population, the deterioration against normal performance and the duration of the incident. Then measure recovery and eventual commercial loss. Keep value exposed separate from value lost, and avoid counting the same failures again in the conversion analysis.

Can payment orchestration reduce the total cost of payments?

It can improve routing, recovery, provider management and resilience where those capabilities address an evidenced problem. The net benefit depends on your payment mix, contracts, configuration and operating model. Include implementation and ongoing costs, and validate improvements against a consistent baseline.