Payment business performance metrics that explain results

Payment business performance metrics explain how transaction count and settled payment value turn into retained revenue and contribution. The essential measures are average ticket, net revenue yield, processing cost per transaction and the cost of supporting merchants. Review them together: a higher-value merchant segment can have a lower yield and still produce useful contribution.

Define the transaction population before measuring performance

The Federal Reserve Payments Study reports noncash payments using both number and value. A payment business needs the same distinction. Count explains transaction-driven workload; value provides the denominator for revenue yield.

Use a merchant settlement summary for the period, a fee report, processor expense detail and summarized merchant-support costs. Keep merchant segment, reporting date, transaction status, currency and fee category available on the underlying rows. Business summaries are sufficient for this analysis; the comparison does not require card details.

Decide whether payment value means settled purchases before refunds or another documented basis. In the example below it means settled purchases, with no refunds, chargebacks or failed attempts in the illustrated population. A live report should show their treatment explicitly rather than quietly mixing purchase count with a different value population.

Assign ownership before publishing the report. Finance owns revenue and expense treatment, payment operations validates settlement totals, and merchant-service leaders validate support costs. The guide to metric definitions and report ownership covers that responsibility in more detail.

Use a short set of connected formulas

Average ticket = Settled purchase value / Settled purchase count

Management net revenue = Merchant fees earned − Identified pass-through charges

Net revenue yield, basis points = Management net revenue / Settled purchase value × 10,000

Processing cost per transaction = Other processing expense / Settled purchase count

Segment contribution = Management net revenue − Other processing expense − Attributed support cost

Here, other processing expense excludes every pass-through charge already deducted from merchant fees. The retained revenue measure is a management definition; it does not establish whether a particular company's financial statements should present revenue gross or net.

The Federal Reserve's debit interchange tables distinguish average fees per transaction from fees relative to transaction value. That illustrates why the denominator must stay visible. Those interchange figures describe a specific fee category, rather than the full retained revenue of a payment processor.

Work the measures from the merchant segments

An illustrative US payment business reviews September 2026. The three segments are mutually exclusive, and all monetary amounts are USD. Merchant fees are earned transaction fees; separately priced subscriptions are outside this example.

Subtract the pass-through column from merchant fees on each row. Then calculate ticket size and yield using that same segment's settled population.

Ticket values are rounded to cents and yields to one decimal place. The total ticket is $14,000,000 divided by 150,000. The total yield is $96,000 divided by $14,000,000, multiplied by 10,000; neither total is a simple average of segment rates.

Add processing and support costs

The following expense rows come from the same month. Support costs are attributed using the firm's documented service-activity method. They are separate from processor expenses and from the pass-through charges above.

Processing cost per transaction is rounded to three decimal places. The total uses $25,000 divided by 150,000. Contribution dollars are unrounded: for online merchants, $36,000 minus $10,000 minus $8,000 equals $18,000.

Wholesale has the highest processing cost per transaction here, but it also has the largest ticket size. Looking only at unit expense would miss how much value each transaction carries. Looking only at yield would miss the contribution remaining after costs.

Contribution is before any remaining shared company expenses. Keep its meaning distinct from gross profit or net income, as explained in gross margin versus contribution margin versus net margin.

Show what a change in mix does

Suppose wholesale adds $1,000,000 of settled value at the same $500 average ticket. That adds 2,000 transactions. At its unchanged 40.0 basis-point yield, it adds $4,000 of retained revenue; at $0.300 processing cost per transaction, it adds $600 of processing expense. Assume support cost stays unchanged for this limited comparison.

The business earns more contribution while its blended yield falls. The explanation is the additional lower-yield segment volume. Test whether the unchanged support assumption remains credible before using this comparison in a staffing or merchant-growth decision.

Reconcile before making a comparison

For the original month, the segment counts must sum to the settlement report's 150,000 transactions and the values to $14,000,000. The fee report must support merchant fees of $325,000 and identified pass-through charges of $229,000.

The expense bridge is $229,000 plus $25,000 plus $18,000, totaling $272,000. Merchant fees of $325,000 less $272,000 must equal the same $53,000 contribution. If the income statement already presents the retained $96,000 as revenue, reconcile to that amount and avoid deducting pass-through charges again.

For external comparisons, use business performance benchmarking to check whether scope and definitions match. A peer's published volume or revenue yield may cover different transaction types and fee categories.

Where it goes wrong

• Attempts mixed with settlements. Failed authorizations or retries can inflate count without adding settled purchase value.
• Refund timing ignored. Refunds recorded in a later period can distort yield if the report switches between gross purchases and net payment value.
• Pass-through costs deducted twice. Keep the retained revenue bridge separate from other processor expense.
• Currencies combined without conversion. Convert value, fees and expenses consistently before comparing amounts or yields.
• Segment rates averaged equally. Divide the company totals, using value for yield and count for unit processing cost.

Compare your payment performance in Covirage

Bring a merchant settlement summary, fee export and summarized processing and support costs to Covirage. Covirage maps the columns, and its tools compute and check volume, retained revenue yield and contribution; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for financial services for the industry context.