Payments Revenue Analysis: Pricing the Transaction and Keeping the Fee

A merchant payment creates several commercial relationships: the issuer, network, acquirer, processor and gateway may each earn a different fee. The amount paid by the shopper is a transaction value shared by the chain, while each provider's economics follow its own contract.

This article explains how to connect transaction count and payment value to fee-bearing events, then account for pass-through charges, incentives and risk. It uses evidence available through December 2025. The worked pricing example is deliberately hypothetical and is not a market take-rate estimate.

Transaction count, payment value and the reporting boundary

Write the counting rule beside every volume number. Payment volume may mean the value of card purchases, successful wallet payments, invoices paid through a business network, gross payment volume (GPV), total payment volume (TPV), gross dollar volume (GDV), payment spend, or the value of transactions submitted to a gateway. Some measures exclude reversals, cash transactions, gateway-only activity, or certain co-branded geographies. A similar acronym can hide a different population and boundary.

The Federal Reserve Payments Study estimates aggregate noncash payment volumes across cards and other payment methods. Its 2022 release reports general-purpose card payments of 153.3 billion transactions and $9.76 trillion in value. Those are economy-wide activity estimates, not revenue earned by a card network, an acquirer, a gateway, or a processor. Preserve the study population, method, year, and unit before using it as market context.

For a company metric, record the reporting entity, product scope, geography, period, currency conversion, success or authorization rule, treatment of reversals and refunds, and whether the number is gross or net of adjustments. A volume number without those fields is a lead for research, not a comparable revenue denominator.

Separate transaction count, payment value, and processed volume

Transaction count measures events. Payment value measures the money represented by those events. Processed volume can refer to activity that a platform accepted, switched, settled, or enabled through a partner. A processor can handle more small transactions while value stays flat, or value can grow because ticket size rises while event count barely changes.

The Visa 2025 Form 10-K explicitly separates payments volume from processed transactions. It describes payments volume as the aggregate dollar amount of purchases carried on Visa-branded forms and processed transactions as payment and cash transactions using its networks. Visa says payments volume is a primary driver of service revenue, while processed-transaction count is a primary driver of data-processing revenue. That relationship is useful, but neither metric is itself Visa revenue.

Build a three-column time series for transaction count, payment value, and recognized revenue. Add average ticket value as a derived diagnostic only when the numerator and denominator share the same scope. Do not divide one company’s broad volume by another company’s narrow transaction count and call the ratio a take rate.

The provider role determines the fee

Money can pass through a merchant, payment facilitator, gateway, acquirer, issuer, card network, wallet, fraud provider, settlement bank, and processor. The same payment can appear in several participants’ activity metrics. Each participant may charge a different customer for a different promise.

Start with a role map. Name the contractual customer, the end payer, the merchant or supplier, the network, the settlement account, and each outsourced service. Then identify who authorizes, routes, clears, settles, funds, stores credentials, manages disputes, and provides reporting. Volume is a shared observation across this chain; revenue belongs to the party that satisfies a defined performance obligation.

An enterprise platform may expose a single dashboard that combines gateway, fraud, acquiring, wallet, and software activity. Treat the combined volume as a platform indicator until the company explains which components are included and where revenue is recorded. A larger dashboard total does not mean the provider owns every fee in the flow.

Distinguish network, processor, acquirer, gateway, wallet, and issuer

The words “processor” and “payments company” are too broad for a revenue comparison. A network can charge assessments and cross-border fees while the issuer earns interest and interchange. An acquirer or merchant processor can charge a discount fee and pay network and interchange costs. A gateway can charge for routing or authorization without owning settlement. A wallet can monetize payments, balances, credit, subscriptions, or advertising.

The Mastercard 2024 Form 10-K discusses gross dollar volume, switched transactions, and payment-network net revenue as separate drivers. The filing also describes services and data as part of a broader value proposition. Use the network’s own role and metric definitions rather than assigning the whole merchant fee to the network.

For each company, create a role row with service, customer, fee basis, principal or agent assessment, and major cost recipients. If the row cannot be completed from the filing or contract, label the revenue bridge unresolved. A market-size estimate that collapses all roles into “processor revenue” will overstate some participants and understate others.

Issuer metrics and fee-bearing events

Company metrics are management-defined measures, even when they use common labels. PayPal defines TPV as the value of payments, net of reversals, successfully completed on its platform or enabled through a partner solution, excluding gateway-exclusive transactions. Block reports transaction-based revenue and transaction-based costs within a broader revenue mix. A merchant-acquiring platform may report GPV that includes payment volume processed for sellers but excludes products outside the seller ecosystem.

The PayPal 2024 Form 10-K shows why the metric should be read with the revenue table. PayPal discusses TPV, payment transactions, active accounts, transaction revenue, and other value-added services separately. Growth in TPV can support revenue growth while mix, pricing, partner economics, and non-transaction services change the relationship.

Keep a metric dictionary for every issuer: definition, inclusion rule, exclusion rule, period, currency, source page, and comparable prior period. Do not treat a disclosed management metric as GAAP revenue or as a fee rate unless the company explicitly defines it that way.

Use a signal ledger before building a revenue bridge:

Scroll horizontally to compare all columns.

Translate volume into fee-bearing events

Volume becomes a revenue opportunity only when a fee-bearing event is identified. Possible events include authorization, capture, clearing, settlement, cross-border conversion, recurring billing, tokenization, fraud screening, dispute handling, account funding, invoice payment, or access to a software feature. Some contracts price by value, some by event, some by account, and some by a fixed subscription.

Use the following sequence: eligible event → contracted price basis → discounts and incentives → amounts owed to other participants → retained consideration → recognized revenue. The sequence prevents a payment value from becoming a fictional percentage take rate. A flat fee can make small-ticket volume more valuable per dollar than large-ticket volume, while a percentage fee does the opposite.

The AvidXchange filing provides a useful disclosure pattern. It presents transactions processed, transaction yield, and total payment volume as separate metrics and defines transaction yield as total revenue divided by transactions processed. Even this company-specific yield is not portable to a card network or wallet with a different product mix and accounting boundary.

Gross charges, pass-through amounts and retained economics

Gross payment value can include money that a platform collects or routes for a merchant, supplier, issuer, network, tax authority, or other provider. Gross billings may describe the customer-facing charge, while net revenue describes the amount the reporting entity retains or is entitled to recognize. The difference is a boundary decision, not a cosmetic adjustment.

The FASB Revenue Recognition Implementation Q&As explain that transaction price excludes amounts collected on behalf of third parties and that principal-versus-agent analysis can determine gross or net presentation. Apply this guidance to the promised service and the contractual facts. Do not subtract every cost from volume, and do not assume that every amount billed belongs in revenue.

Create separate columns for customer charge, payment value, pass-through amount, incentive, processing cost, interchange or network cost, retained fee, and reported revenue. If the company discloses only one of those fields, preserve the missing fields as unavailable. A net revenue line cannot be reverse-engineered into a universal take rate without the relevant denominator and exclusions.

Apply the principal-versus-agent accounting boundary

A company that controls the specified payment service before transfer may recognize consideration on a gross basis. A company that arranges for another party to provide the service may recognize only its fee or commission. The conclusion depends on the arrangement, not on whether the company’s marketing page calls itself a processor.

The Block 2024 Form 10-K describes transaction fees collected from sellers as revenue on a gross basis when Block is the principal in delivering managed payments solutions. It also describes transaction-based costs and amounts paid to third-party processors and financial institutions. This is a company-specific accounting conclusion, not permission to apply gross revenue to every payments platform.

For a comparison, capture the promised service, contractual customer, control indicators, inventory or chargeback risk, price discretion, and whether the entity is principal or agent. Then compare like presentation with like presentation. A platform that reports net commissions can have high payment value and low reported revenue without having weak activity.

Account for incentives, interchange, network fees, and transaction costs

Payment economics are shaped by the amounts paid to issuers, networks, processors, fraud vendors, banks, and partners. Volume can rise while retained revenue or margin falls if incentives increase, pricing declines, the mix shifts toward costly methods, or fraud and dispute expense grows.

The CFPB cash-back fee analysis models merchant transaction costs across interchange, network, acquirer, and fraud-control components. It is a scenario analysis, not a processor income statement, but it shows why a merchant’s fee and a processor’s retained revenue are different measures. The CFPB electronic-payments analysis likewise separates fees collected from payment-processing costs in a sampled setting.

Build a cost waterfall by payment method and role. Identify network assessments, interchange, acquiring, partner residuals, fraud controls, chargebacks, funding, and support. Keep contract incentives separate from operating costs and from reductions of revenue. If an issuer or processor does not disclose the waterfall, do not fill it with an industry-average percentage.

Payment mix and adjacent services

A dollar of domestic debit volume, a cross-border card payment, an ACH transfer, a wallet payment, and a buy-now-pay-later transaction can carry different price, cost, risk, and settlement characteristics. Foreign exchange translation can change reported volume even when local activity is stable. A company may report nominal volume, constant-currency volume, or both.

The Visa filing distinguishes domestic and international volume and explains that nominal payments volume is translated into U.S. dollars using established exchange rates. Mastercard similarly reports domestic and cross-border drivers. Use those disclosures to segment the bridge by geography, currency, payment method, merchant vertical, ticket size, and customer type.

Do not infer a global take rate from a single quarter when the mix is changing. A region with higher cross-border activity may support additional international-transaction revenue while also carrying different incentives, compliance costs, chargeback exposure, and partner shares. The mix bridge is part of the revenue explanation.

Separate transaction revenue from subscriptions, lending, and other services

Payment platforms often monetize more than payment processing. Subscription and software fees, lending interest, credit products, foreign exchange, advertising, hardware, referrals, fraud tools, and data services can sit beside transaction revenue. A company’s total revenue can grow while payment volume is flat, or payment volume can grow while other revenue declines.

The Block filing presents transaction-based revenue, subscription and services-based revenue, hardware revenue, and other categories separately. PayPal also separates transaction revenue from value-added services and interest-related categories. Preserve those segments when testing a volume-to-revenue thesis.

For each company, build a revenue bridge with transaction fees, recurring software, financing, FX, hardware, services, and other items. Mark which lines are volume-linked, account-linked, contract-linked, or balance-linked. This keeps a payment-volume story from claiming credit for revenue that comes from lending or subscription expansion.

Risk costs and transaction timing

Volume is not equally attractive when the processor bears different risks. Card-not-present activity, cross-border transactions, new merchants, high-return categories, delayed settlement, and consumer credit can require underwriting, reserves, fraud controls, chargeback handling, or liquidity. A high-volume account may create a low-margin or negative contribution if risk costs absorb the fee.

Add risk fields to the account or segment record: authorization quality, fraud rate, chargeback rate, refund rate, reserve requirement, settlement timing, credit exposure, compliance burden, and who bears each loss. Keep observed risk, disclosed provision, and forecast assumption separate. A processor’s volume growth does not prove that risk-adjusted revenue or profit is growing.

The buyer should also distinguish a processor that merely routes a transaction from one that funds a merchant, extends credit, guarantees settlement, or provides a managed fraud service. Those roles change capital, expense, and revenue requirements even when the visible payment value is identical.

Align volume period, settlement, revenue recognition, and renewal

Payment volume is usually reported for a measurement period, while revenue may be recognized when a service is performed, when a transaction settles, over a subscription term, or when another performance obligation is satisfied. Reversals, refunds, delayed settlement, contract incentives, and currency conversion can move the amounts between periods.

The European Commission payment-services overview describes the regulatory environment for payment services and interchange-related rules. Regulation can affect pricing and fee ceilings, but it does not determine one company’s recognized revenue. Record jurisdiction, payment method, regulatory status, and effective date before comparing fee economics across markets.

Build a period bridge with authorization date, capture date, settlement date, service period, refund or reversal date, invoice date, recognition date, and renewal date. A contract may create recurring software revenue after an implementation, while transaction fees follow payment activity. The correct period matters for both forecasting and cohort comparison.

Test the opportunity at the merchant-contract level

A merchant strategy team may care about conversion, authorization, cost, reconciliation, settlement, and integration. An issuer may care about spend, interchange, fraud, and customer retention. A network may care about switched transactions, acceptance, cross-border mix, and services. An enterprise software buyer may care about APIs, reporting, and implementation cost. The same payment volume answers different commercial questions for each buyer.

Use a buyer filter with five required fields: target role, fee-bearing event, addressable volume, economic share, and decision trigger. Add the incumbent, contract term, technical dependency, procurement route, and measurable success condition. A broad volume estimate should be narrowed to the transactions that the buyer can serve and monetize under its actual product and geography.

The resulting opportunity statement should read like this: “Within a defined cohort, the target role can process a specified event type during a stated period, under a documented pricing and cost boundary, when a contract or renewal event is open.” If any part is missing, call the opportunity a hypothesis and state the evidence needed next.

A transparent transaction-pricing example

Assume a hypothetical provider processes 2.4 million successful transactions in one period, each with an average value of $180. Payment value is $432 million. Its illustrative contract charges $0.03 per transaction plus 0.40% of payment value. The fixed charge is $72,000; the value-based charge is $1,728,000; total contractual charges are $1,800,000.

If specified network and partner amounts total $1,350,000, the arithmetic leaves $450,000 before other operating and risk costs. This remainder is a pricing contribution under the invented assumptions, not an accounting conclusion about net revenue. Gross-versus-net presentation still depends on the provider's contractual responsibilities and applicable reporting policy.

Now hold payment value at $432 million but increase average ticket to $216: transaction count falls to 2 million, the fixed fee becomes $60,000, and the value fee stays $1,728,000. Charges fall to $1,788,000. Equal payment value can therefore produce different fee income because the fee-bearing event count changes. A real model also needs payment-method mix, reversals, discounts and each cost's charging basis.

Build the fee model from the contract at the provider layer you are studying. Validate both transaction count and value, then reconcile retained economics and accounting presentation. That makes changes in ticket size, payment method or cross-border mix visible in the commercial forecast.