Payment processors and gateways operate the B2B infrastructure that merchants use to accept card payments. The customer is a business (online retailer, software platform, in-store merchant) rather than an end consumer. Revenue flows through interchange-plus pricing or merchant discount rate models, with the processor’s margin sitting between merchant fees collected and interchange plus card network costs paid out. The accounting work centers on gross-versus-net revenue presentation, settlement liquidity, merchant credit risk, ISO and ISV partner economics, and the high-volume reconciliation that comes with running merchant card processing infrastructure. The model differs from consumer-facing payments fintechs serving end users and from card issuing on the other side of the card flow. This page covers what makes payment processor accounting distinct, and the services available to address it.

Executive Summary

• Payment processors operate B2B infrastructure for merchant card acceptance, with revenue mechanics centered on interchange pass-through and processor margin rather than consumer-facing product economics.
• Gross-versus-net revenue presentation under ASC 606 principal-versus-agent analysis is the most consequential accounting question, with the choice materially affecting how the company’s revenue scale appears.
• Merchant credit risk and chargeback exposure create ongoing reserve and liquidity requirements that grow with merchant portfolio size and risk concentration.
• ISO (Independent Sales Organization) and ISV (Independent Software Vendor) partner revenue share arrangements add layered economics that require explicit accounting treatment.
• Settlement timing across card networks, acquirers, and merchant payouts creates working capital exposure that needs careful management to avoid liquidity gaps during transaction volume spikes.

What Payment Processors Look Like as a Business

Payment processors and gateways enable merchants to accept card-based payments. The category includes:

• Full-stack processors handling authorization, clearing, settlement, and merchant onboarding through direct acquiring or sponsorship relationships
• Payment gateways securely transmitting payment information between merchant systems and acquiring banks
• Payment facilitators (PayFacs) aggregating sub-merchants under their own master merchant ID
• Embedded payment platforms integrating processing into vertical software (restaurant POS, healthcare, hospitality)
• Specialty processors serving high-risk industries, recurring billing, or specific verticals
• Cross-border processors handling multi-currency settlement and international card acceptance
• Independent Sales Organizations (ISOs) and ISVs distributing processing services to merchants under partner relationships with full-stack processors

What distinguishes payment processors from other fintech is the merchant-facing role and the card network economics that drive revenue. Each card transaction generates interchange paid to the issuing bank, network assessments paid to Visa or Mastercard, and the processor’s margin (the difference between what the merchant pays and what flows out to interchange and networks). The accounting captures these flows across millions of transactions, with the principal-versus-agent question driving fundamental decisions about how revenue is presented in financial statements. Settlement liquidity, merchant credit risk, partner revenue share, and PCI compliance overhead all sit underneath the revenue economics.

What Makes Payment Processor Accounting Distinct

Gross versus net revenue presentation

The most consequential accounting decision for payment processors is whether to present revenue gross (showing total merchant payment volume with interchange and network fees as cost of revenue) or net (showing only the processor’s margin as revenue). The choice depends on principal-versus-agent analysis under ASC 606, which evaluates whether the processor controls the service before transferring it to the merchant. Gross presentation typically results in much larger revenue figures (often 10x or more) but with correspondingly thinner margin percentages. Net presentation results in smaller revenue figures with healthier reported margins. The decision affects valuation discussions, comparability with peer companies, and the analyst narrative about company scale. Companies often present both, but the primary GAAP presentation is one or the other.

Interchange-plus pricing and pass-through accounting

Most modern processors use interchange-plus pricing: the merchant pays the actual interchange cost plus a markup (basis points and per-transaction fee). The accounting needs to separate pass-through interchange from the processor’s earned margin. Interchange varies by card type, merchant category code (MCC), transaction size, and a hundred other factors. The pass-through component changes with each transaction and needs to be tracked precisely. Tiered pricing models (qualified, mid-qualified, non-qualified rates) and flat-rate pricing models (a single rate covering everything) have different accounting implications because the relationship between merchant revenue and interchange cost is structured differently.

Merchant credit risk and chargeback liability

If a merchant cannot cover chargebacks (because they go out of business, dispute deliberately, or face fraud-driven dispute spikes), the processor typically becomes liable. The accounting captures merchant credit exposure across the portfolio, with reserves for expected losses based on merchant risk profile, industry, transaction patterns, and dispute history. Credit losses on failed merchants are a recurring cost of operations that needs explicit reserves. High-risk merchant categories (gambling, adult content, certain travel verticals, some subscription businesses) carry elevated credit reserves. Merchant onboarding underwriting (KYB, risk assessment, financial review) becomes part of routine financial operations.

Rolling reserves and merchant collateral

For higher-risk merchants, processors often hold rolling reserves: a percentage of monthly processing volume held back as collateral against potential chargebacks. The accounting captures the rolling reserve balance per merchant, the ongoing additions and releases, and the relationship between reserve adequacy and actual chargeback experience. Some merchants object to rolling reserves and the processor’s ability to enforce them affects the quality of the merchant book. The reserve mechanics need clear documentation in merchant agreements and consistent application based on documented risk policy. Inconsistent reserve practices create both legal exposure and audit findings.

Settlement timing and liquidity management

Funds flow from cardholders through card networks to acquirers and ultimately to merchants. The processor sits in the middle of this flow with timing differences between when funds are received and when they’re paid out. Daily settlement obligations and merchant payout schedules create working capital exposure that grows during volume spikes. Some processors offer fast funding (next-day or same-day payouts) at premium pricing, which adds revenue but increases liquidity pressure. The accounting captures pending settlements, in-transit funds, and the operational reserves needed to maintain payout reliability. Liquidity facilities or credit lines are typically maintained as backstops. Rapid merchant onboarding outpacing liquidity has caused issues at multiple processors over the years.

ISO, ISV, and partner revenue share economics

Many processors operate through Independent Sales Organizations (ISOs) and Independent Software Vendors (ISVs) that distribute processing services to merchants. Each ISO and ISV has a contractual revenue share covering portions of processing margin. Tiered structures, residual payments, portfolio sales, and contingent compensation all add complexity. The accounting captures gross processing revenue, ISO/ISV revenue share owed, residual obligations on portfolios sold or transferred, and the net economics retained by the processor. Some ISVs receive equity-style compensation tied to volume thresholds. Inadequate accounting for partner economics has caused significant financial restatement events in the industry. As processors become more software-driven, ISV partnerships often replace traditional ISO relationships with different economic dynamics.

PCI DSS compliance scope and costs

Payment processors operate as Level 1 PCI service providers, requiring the highest tier of PCI DSS compliance: annual on-site assessment by a Qualified Security Assessor, quarterly network scans, ongoing security monitoring, and detailed documentation. PCI compliance costs are substantial and recurring. The infrastructure investments to maintain compliance (network segmentation, encryption, tokenization, access controls) represent meaningful ongoing expense. PCI failures can result in fines, increased liability for breaches, and removal from card brand programs. The accounting captures PCI-related capital expenditure, ongoing compliance costs, and the operational evidence required to support annual assessment.

Card-present versus card-not-present economics

Card-present transactions (in-person, EMV-chip enabled, contactless) and card-not-present transactions (e-commerce, mobile, MOTO) have different interchange rates, fraud profiles, and dispute mechanics. Card-not-present typically has higher interchange (driven by elevated fraud risk) and higher dispute rates. The accounting captures revenue and cost economics by transaction type, with explicit segmentation for portfolio analysis. Merchant pricing typically reflects the underlying interchange differences, and the relationship between transaction mix and overall portfolio margin is meaningful for revenue planning.

Payment facilitator (PayFac) and embedded payment models

Payment facilitators aggregate sub-merchants under their own master merchant ID, taking responsibility for sub-merchant underwriting, transaction processing, and the credit risk of sub-merchants who can’t cover chargebacks. The PayFac model has different accounting implications than standard processing: gross processing volume often runs through the PayFac’s accounts before payout to sub-merchants, requiring different ASC 606 analysis and different liquidity management. Embedded payment platforms in vertical software increasingly use PayFac structures because the unified merchant experience drives stronger software platform economics. The financial complexity of operating as a PayFac is substantial and often the financial readiness becomes a constraint on the strategic decision.

Services for Payment Processors

Fractional CFO leadership

Senior finance leadership for payment processor operations. Gross-versus-net revenue strategy oversight, merchant portfolio risk management, ISO and ISV partner economic structuring, settlement liquidity planning, fundraising support, M&A diligence response, and the institutional readiness work that scaled processors need. For broader fintech context, see the CFO role in fintech guide. For our general fractional CFO services, see the fractional CFO services page.

Accounting and bookkeeping

Day-to-day accounting work for payment processor operations. Interchange-plus revenue recognition with pass-through separation, gross-versus-net presentation maintenance, ISO and ISV revenue share accounting, merchant credit reserve tracking, rolling reserve liability accounting, settlement reconciliation across multiple acquirers and networks, and consolidated financial reporting that supports both internal management and external audit requirements. See startup accounting services for broader scope.

Consulting and advisory

Project-based engagements for specific payment processor challenges. ASC 606 principal-versus-agent analysis for revenue presentation. Interchange-plus pricing model design and accounting framework. Merchant credit risk policy and reserve framework. ISO and ISV partner economic analysis and contract structuring. PayFac model financial readiness assessment. Settlement liquidity and treasury planning. BSA/AML compliance program design. Audit readiness for processors preparing for first audit, IPO, or M&A diligence. SOX compliance readiness for processors approaching public-company status. See accounting consulting services for additional detail.

Frequently Asked Questions

How are payment processors different from payments fintechs?

Payment processors operate B2B infrastructure for merchants accepting card payments. The customer is a business. Payments fintechs serve consumers directly with apps for sending money or making purchases. The end customer differs (merchant vs. consumer), the revenue model differs (interchange-plus margin vs. free-tier monetization), and the unit economics differ. Payment processors compete on processing rates, technology, and merchant servicing. Payments fintechs compete on user experience, network effects, and consumer monetization.

Should processors present revenue gross or net?

The choice depends on principal-versus-agent analysis under ASC 606, which evaluates whether the processor controls the service before transferring it to the merchant. Gross presentation results in much larger revenue figures with thinner reported margins. Net presentation results in smaller revenue figures with healthier reported margins. The decision affects valuation discussions, peer comparability, and analyst narratives about scale. The analysis is fact-specific and needs to be documented in technical accounting memos supporting the chosen position.

How is interchange-plus pricing accounted for?

The accounting separates pass-through interchange (the actual cost of card network interchange paid by the merchant) from the processor’s earned margin (basis points plus per-transaction fee). Interchange varies by card type, merchant category code, transaction size, and other factors, requiring transaction-level tracking. Tiered pricing and flat-rate pricing models have different accounting implications because the relationship between merchant revenue and interchange cost is structured differently.

What is merchant credit risk for processors?

When a merchant cannot cover chargebacks (because they go out of business, dispute deliberately, or face fraud-driven dispute spikes), the processor typically becomes liable. The accounting captures merchant credit exposure across the portfolio, with reserves for expected losses based on merchant risk profile, industry, transaction patterns, and dispute history. High-risk merchant categories carry elevated reserves. Merchant onboarding underwriting (KYB, risk assessment, financial review) becomes routine financial operations.

How are rolling reserves accounted for?

Rolling reserves are amounts held back as collateral against potential chargebacks for higher-risk merchants. The accounting captures the rolling reserve balance per merchant, ongoing additions and releases, and the relationship between reserve adequacy and actual chargeback experience. Reserve mechanics need clear documentation in merchant agreements and consistent application based on documented risk policy. Inconsistent reserve practices create both legal exposure and audit findings.

How are ISO and ISV partner revenue shares accounted for?

The accounting captures gross processing revenue, ISO and ISV revenue share owed under contractual terms, residual obligations on portfolios sold or transferred, and the net economics retained by the processor. Tiered structures, residual payments, portfolio sales, and contingent compensation add complexity. Inadequate accounting for partner economics has caused significant financial restatement events in the industry. As processors become more software-driven, ISV partnerships often replace traditional ISO relationships.

What does PayFac mean for accounting?

Payment facilitators aggregate sub-merchants under their own master merchant ID, taking responsibility for sub-merchant underwriting, transaction processing, and credit risk. Gross processing volume often runs through the PayFac’s accounts before payout to sub-merchants, requiring different ASC 606 analysis and different liquidity management than standard processing. Embedded payment platforms in vertical software increasingly use PayFac structures. The financial complexity of operating as a PayFac is substantial.

Reviewed by YR, CPA
Senior Financial Advisor