Blog · Finance metrics and formulas · Financial services
Fintech unit economics measures what each transaction contributes after processing, losses and servicing. Follow a worked US payments example, reconcile the totals, and see how product and customer cohorts change the result.
Fintech unit economics shows how much revenue a transaction earns and how much remains after processing, losses and servicing. For a payments business, calculate contribution per settled transaction separately for each product, then compare customer cohorts within it. Payment volume alone cannot show whether growth earns enough to cover its costs.
A card issuer, merchant payment provider and transfer service earn different fees and bear different risks. Start with the company whose economics you are measuring. Interchange received by an issuer can be an expense elsewhere in the payment chain.
The Federal Reserve's debit card fee methodology defines average interchange per transaction as total interchange fees divided by settled purchase transactions. It also cautions that a network average does not establish what a particular issuer earns. Use your contractual revenue and actual transaction mix rather than adopting an industry fee as your own yield.
This example uses settled transactions as the unit. Failed attempts have no place in that denominator, but their attributable processing costs still belong in the numerator. Keep refunds and reversals identified so the same payment does not become several successful transactions.
The broader unit economics guide covers customer contribution, acquisition costs and payback. Here the question is narrower: what does delivering payment activity contribute before acquisition spending and fixed corporate expenses?
Transaction contribution = Recognized transaction revenue − Processing expense − Net transaction losses − Attributable servicing expense
Contribution per transaction = Transaction contribution / Settled transactions
Net transaction losses = Gross losses borne by the business − Recoveries
Revenue means the amount recognized by the business, after applicable fee refunds. Customer funds moving through the service are not revenue. Where a report starts with revenue already net of a bank partner's share, do not subtract that share again.
Processing expense includes relevant network, processor and settlement charges. Servicing includes identifiable support, dispute handling and account operations assigned to the activity. Document the driver when a cost cannot be matched directly, such as support minutes by product. An allocated servicing cost may not disappear immediately when transaction volume falls.
Loss ownership matters. The Federal Reserve's report on debit card costs and fraud losses separates authorization, clearing and settlement costs from issuer fraud losses, and distinguishes losses absorbed by issuers, merchants and cardholders. That is a useful boundary for an internal report: count the amount your business bears, rather than every disputed dollar passing through it.
This is a management contribution measure. It is not automatically the gross profit line in the financial statements. Keep a bridge between the two if their cost classifications differ; the gross margin and contribution margin comparison explains that distinction.
Bring the settled transaction register, fee revenue detail, processor statement, loss and recovery register, and servicing cost export for the same reporting period. The transaction register should identify transaction ID, customer ID, product, settlement date, currency, amount and status. Add the customer's activation cohort if you want to compare acquisition groups later.
Summarize costs at their available level before joining them to transaction totals. A monthly processor charge repeated against every transaction would multiply the expense. Keep unmatched costs visible instead of dropping them.
Use one currency throughout. Separate original transaction dates from loss recognition dates, and label which basis the report uses. A current-period ledger view can reconcile cleanly while still carrying losses from older activity.
Consider an illustrative US payments company reporting August 2026 in USD. Revenue below is the company's recognized revenue after partner revenue shares and fee refunds. Processing is a separate expense. The losses are those booked to this business during August; servicing includes documented operating cost allocations.
| Product | Settled transactions | Revenue (USD) | Processing (USD) | Gross losses (USD) | Recoveries (USD) | Servicing (USD) |
|---|---|---|---|---|---|---|
| Debit issuance | 100,000 | 45,000 | 18,000 | 4,000 | 1,000 | 6,000 |
| Merchant acceptance | 40,000 | 64,000 | 28,000 | 9,000 | 1,000 | 10,000 |
| Domestic transfers | 10,000 | 18,000 | 5,000 | 1,500 | 500 | 4,000 |
| Total | 150,000 | 127,000 | 51,000 | 14,500 | 2,500 | 20,000 |
Calculate the loss deduction first, then contribution:
| Product | Net losses calculation (USD) | Contribution calculation (USD) | Contribution (USD) |
|---|---|---|---|
| Debit issuance | 4,000 − 1,000 = 3,000 | 45,000 − 18,000 − 3,000 − 6,000 | 18,000 |
| Merchant acceptance | 9,000 − 1,000 = 8,000 | 64,000 − 28,000 − 8,000 − 10,000 | 18,000 |
| Domestic transfers | 1,500 − 500 = 1,000 | 18,000 − 5,000 − 1,000 − 4,000 | 8,000 |
| Total | 14,500 − 2,500 = 12,000 | 127,000 − 51,000 − 12,000 − 20,000 | 44,000 |
Divide each amount by its own settled transaction count. Amounts below are rounded to four decimal places; calculations use unrounded values.
| Product | Revenue per transaction (USD) | Processing per transaction (USD) | Net losses per transaction (USD) | Servicing per transaction (USD) | Contribution per transaction (USD) |
|---|---|---|---|---|---|
| Debit issuance | 0.4500 | 0.1800 | 0.0300 | 0.0600 | 0.1800 |
| Merchant acceptance | 1.6000 | 0.7000 | 0.2000 | 0.2500 | 0.4500 |
| Domestic transfers | 1.8000 | 0.5000 | 0.1000 | 0.4000 | 0.8000 |
| Total divided by total transactions | 0.8467 | 0.3400 | 0.0800 | 0.1333 | 0.2933 |
The proof is the reverse calculation: 100,000 × 0.18 + 40,000 × 0.45 + 10,000 × 0.80 = $44,000. Dividing by 150,000 returns $0.2933 per transaction after rounding. Do not average the product rates; the guide to count-weighted and value-weighted ratios explains why the denominator sets the weights.
Reconcile $127,000 to the relevant revenue accounts, $51,000 to processing expense, $12,000 to booked losses less recoveries, and $20,000 to the servicing allocation schedule. Separately reconcile the settled count to the transaction register. A correct division cannot repair a missing cost file.
Domestic transfers have the highest contribution per transaction here, but debit issuance and merchant acceptance each contribute more total dollars. Product leaders need both views when evaluating pricing or expansion. They also need to know which processing and servicing costs actually change with the proposed volume.
Test a loss change before assuming volume will improve the result. If merchant gross losses rise from $9,000 to $13,000, with all other inputs unchanged, net losses become $12,000. Contribution becomes $64,000 − $28,000 − $12,000 − $10,000 = $14,000, or $0.35 per transaction. That decline from $0.45 comes entirely from the additional $4,000 of losses.
Finance owns definitions and reconciliation. Payments operations validates settled activity and processing charges. Risk owns loss attribution and recoveries; customer operations owns servicing drivers. Product managers use the agreed report to assess fee changes, partner terms and customer segments.
For cohort comparisons, repeat the calculation within each product using the same observation window after activation. This August ledger example is not a lifetime cohort result: older transactions can produce losses now, while recent transactions may produce losses later.
Upload your transaction, revenue and cost files or a Google Sheet, including product and customer cohort identifiers. Covirage maps the columns; its tools compute and check the figures, and the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own export; creating the account takes about a minute.
See Covirage for financial services for the industry context.
Choose the unit that matches the decision. Settled transactions help evaluate payment pricing and processing costs. Active accounts help evaluate ongoing account servicing. Customer cohorts help assess acquisition spending. Keep each denominator consistent and explain any costs that span more than one unit.
Payment volume is the money customers move through a service. Revenue is the fee, interchange share or other amount the business recognizes for providing that service. Dividing payment volume by transaction count measures average transaction size, not revenue per transaction.
Include the losses your business bears, with recoveries shown separately and a consistent recognition policy. Do not deduct a merchant's or partner bank's loss unless your business is responsible for it. Explain whether the report uses booked losses or an estimate for unresolved cases.
Positive transaction contribution means revenue covers the costs included in that measure. Acquisition spending, corporate overhead and other excluded expenses can still exceed that contribution. Reconcile the transaction report to the company income statement before treating it as a profitability result.