Payments: how the industry works
Payment firms move instructions and money between customers, merchants and banks. Authorization, clearing, settlement and dispute handling are distinct stages with different risks.
Scope and segments
Payment processing, acquiring, gateways and payment networks. Card payments and bank transfers illustrate different operating models; credit underwriting and deposit-taking belong primarily to banking. U.S. ACH and FedNow are named examples, not global standards.
- Merchant services
- Gateways and processors connect checkout to financial institutions, provide reconciliation and manage fraud tools.
- Card ecosystems
- Issuers, acquirers and networks coordinate authorization and financial obligations; a single provider can perform several roles.
- Account-to-account transfers
- Bank-based rails move funds through batch or instant processing with their own return, settlement and participation rules.
10 companies to know
Illustrative examples distinguish card networks, merchant payment platforms and consumer payment services. This alphabetical selection is not a transaction-volume, revenue or quality ranking.
Listed alphabetically. Names link to official sources. Checked . How we select examples.
-
Adyen
Integrated merchant payments
Provides businesses with payment capabilities, data tools and financial products through one platform. Its integrated approach illustrates combining payment acceptance with supporting services for merchants.
-
American Express
Integrated card network
Connects card members and merchants through its payment network and card products. It illustrates a model combining customer relationships, merchant acceptance and payment-processing capabilities.
-
Block
Seller and consumer ecosystems
Operates businesses including Square and Cash App, connecting merchant tools with consumer financial applications. Its portfolio illustrates distinct entry points into everyday payment activity.
-
Checkout.com
Online payment processing
Helps businesses accept and optimize digital payments, with tools for payment performance and disputes. It illustrates the operational importance of successful authorization and managing exceptions.
-
Fiserv
Merchant and bank payment technology
Provides merchant commerce systems and payment technology for banks and other financial institutions. Its product range illustrates infrastructure serving both payment acceptance and financial-service providers.
-
Global Payments
Merchant payment technology
Provides payment acceptance and software for businesses operating online and in stores. It illustrates how payment processing can be combined with tools that support merchant operations.
-
Mastercard
Payment network
Provides technology connecting participants in digital payments. Its network role illustrates a business that enables transactions across institutions and merchants rather than operating every customer relationship itself.
-
PayPal
Consumer and merchant payments
Provides digital payment services connecting consumers and businesses. Its model illustrates the role of a recognizable payment account and checkout option within wider commerce transactions.
-
Stripe
Developer-oriented payment infrastructure
Provides tools for businesses to accept payments and manage billing and revenue processes. It illustrates payment infrastructure embedded into software products and online commercial workflows.
-
Visa
Payment network and services
Facilitates digital payments among consumers, merchants, financial institutions and governments. Its network and supporting services illustrate transaction infrastructure spanning many independently operated customer and merchant relationships.
How it works
Follow the main sequence. Actual operating models may combine or outsource individual stages.
- 1
Initiate
A customer presents credentials or authorizes a transfer. The merchant attaches the payment to an order and amount.
- 2
Authenticate and authorize
Identity and risk checks determine whether to proceed. A card approval is not the same as final settlement.
- 3
Capture and clear
Participants exchange transaction details and calculate obligations. Separate capture permits some merchants to charge after fulfillment.
- 4
Settle and reconcile
Funds are transferred according to rail rules, and ledger entries are matched to orders, fees and payouts.
- 5
Resolve exceptions
Refunds, failed transfers and disputes create additional messages, evidence and possible reversals after the original sale.
How money moves
- Revenue or funding unit
- A fee per transaction, a percentage of payment value, recurring service charges, or a combination.
- Who pays
- Merchants often pay acceptance fees; banks and other participants pay network or processing charges. Fee allocation depends on the rail and commercial agreement.
Main costs
- Pass-through charges
- Network, bank or interchange-related charges can consume much of the merchant-facing fee.
- Risk losses
- Fraud, merchant failure and disputed payments can create losses beyond the processing cost.
- Reliable operations
- Security, uptime, support, reconciliation and compliance require continuous investment.
Assets and investment
Processors need resilient systems and, depending on their role, liquidity, reserves or regulatory capital. A software gateway has a different balance sheet from a bank acquirer.
The cash cycle
Settlement timing, payout schedules and reserves determine when money reaches merchants. Client funds and payment volume are not automatically the processor’s revenue.
The economic mechanism
Higher transaction volume can spread fixed infrastructure costs, but low-value transactions, fraud-heavy merchants and expensive payment methods can change contribution per transaction. Improving approval rates is valuable only if incremental fraud losses remain acceptable.
Inside the operation
Measures that matter
| Measure | What it measures | Why it matters |
|---|---|---|
| Authorization rate | Approved payment attempts divided by relevant attempts, with retry handling specified. | Distinguishes checkout friction from successful sales; repeated retries can distort the number. |
| Net revenue yield | Provider revenue after defined pass-through costs divided by processed value. | Shows monetization without mistaking gross payment volume for revenue. |
| Fraud loss rate | Fraud losses divided by relevant processed value. | Tests whether higher acceptance creates acceptable risk. |
What shapes the industry
Payments are interconnected networks: customers need reachable merchants and merchants need reachable customers. Existing connections and integrations can matter more than a marginally faster API.
Different rails trade off cost, speed, reach and recovery mechanisms. FedNow offers near-real-time interbank settlement, while ACH uses batches. The user experience can appear instant even when underlying obligations are settled later.
Who it connects to
These relationships describe typical flows. They are not a list of every supplier or customer.
Buys from / depends on
- Commercial banking
Banks provide accounts and settlement access.
- Telecommunications
Transaction messages require secure connectivity.
Supplies / serves
- E-commerce
Online sellers need checkout, refunds and payouts.
- Restaurants
Merchants accept cards and reconcile terminal sales.
Substitutes and alternatives
- Cash and direct bank arrangements
Can settle purchases without the same merchant-processing stack, while introducing different costs and risks.
Payment volume versus retained revenue
Illustrative calculation
The inputs below are hypothetical. They explain a mechanism and are not industry benchmarks or a forecast.
Assumptions
- Illustrative processor handles 100,000 transactions averaging $40.
- Merchant fee is 2.5%; pass-through charges are 1.9% of value.
- Risk losses and direct processing costs total $12,000.
Calculation
- Processed value = 100,000 × $40 = $4m.
- Merchant fees = $100,000; pass-through charges = $76,000.
- Contribution after stated direct costs = $100,000 − $76,000 − $12,000 = $12,000.
A $4m payment flow produces $12,000 in this illustrative contribution calculation, before fixed overhead and tax.
What changes when…
The processor relaxes fraud screening to approve more orders.
- Fewer legitimate buyers are blocked, increasing completed sales.
- More fraudulent attempts may also pass; losses emerge through later disputes.
- The decision must be evaluated over a full loss-observation period, not just same-day approval counts.
What to watch
- Approval rate by merchant and method
- Matured fraud losses
- Dispute and refund rates
A qualitative scenario based on the operating model, not a quantitative prediction.
Risks and misconceptions
- Ledger mismatch
- A successful user-facing status is not matched by the expected settlement or payout.
- Merchant failure
- A merchant receives money before delivering goods, then cannot fund refunds or disputes.
- Common infrastructure outage
- A network or bank dependency interrupts many merchants simultaneously.
Sources: [4]. See source scope below.
Common misconceptions
- A payment marked authorized is irrevocably received cash.
- Authorization, capture, settlement and dispute resolution are separate; reversibility depends on the rail and rules.
Sources and scope
Primary references anchor the factual mechanisms below. Operating models, relationship choices, and worked examples are editorial synthesis. Linked sources do not constitute endorsement.
- Automated Clearinghouse ServicesFederal Reserve Board
U.S. ACH batch credit/debit transfer structure.
- FedNow ServiceFederal Reserve Board
Near-real-time interbank clearing, settlement and liquidity support.
- The Payment Intents APIStripe
A provider-specific example of payment lifecycle and authentication states.
- How disputes workStripe
Provider-specific card dispute flow, evidence and debits after payment.
The operating model and causal analysis are editorial synthesis. All worked-example figures are invented assumptions for explanation, not industry benchmarks. Regulations and payment conventions vary by jurisdiction.
From understanding to operating
Try this workflow with ERP.AI
Prepare bank instructions, obtain independent authorization, retain provider settlement evidence, and reconcile account movements for the treasury workflow supporting a payment business’s financial operations.
2 Run it with Proto
Get the desktop agent, then return to the app page to continue setup.