{ "slug": "payments", "name": "Payments", "sector": "finance-insurance", "summary": "Payment firms move instructions and money between customers, merchants and banks. Authorization, clearing, settlement and dispute handling are distinct stages with different risks.", "scope": "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.", "aliases": [ "Payment processing", "Merchant acquiring", "Payment networks" ], "segments": [ { "name": "Merchant services", "description": "Gateways and processors connect checkout to financial institutions, provide reconciliation and manage fraud tools." }, { "name": "Card ecosystems", "description": "Issuers, acquirers and networks coordinate authorization and financial obligations; a single provider can perform several roles." }, { "name": "Account-to-account transfers", "description": "Bank-based rails move funds through batch or instant processing with their own return, settlement and participation rules." } ], "flow": [ { "name": "Initiate", "description": "A customer presents credentials or authorizes a transfer. The merchant attaches the payment to an order and amount." }, { "name": "Authenticate and authorize", "description": "Identity and risk checks determine whether to proceed. A card approval is not the same as final settlement." }, { "name": "Capture and clear", "description": "Participants exchange transaction details and calculate obligations. Separate capture permits some merchants to charge after fulfillment." }, { "name": "Settle and reconcile", "description": "Funds are transferred according to rail rules, and ledger entries are matched to orders, fees and payouts." }, { "name": "Resolve exceptions", "description": "Refunds, failed transfers and disputes create additional messages, evidence and possible reversals after the original sale." } ], "economics": { "revenueUnit": "A fee per transaction, a percentage of payment value, recurring service charges, or a combination.", "payers": "Merchants often pay acceptance fees; banks and other participants pay network or processing charges. Fee allocation depends on the rail and commercial agreement.", "costs": [ { "name": "Pass-through charges", "explanation": "Network, bank or interchange-related charges can consume much of the merchant-facing fee." }, { "name": "Risk losses", "explanation": "Fraud, merchant failure and disputed payments can create losses beyond the processing cost." }, { "name": "Reliable operations", "explanation": "Security, uptime, support, reconciliation and compliance require continuous investment." } ], "capital": "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.", "workingCapital": "Settlement timing, payout schedules and reserves determine when money reaches merchants. Client funds and payment volume are not automatically the processor’s revenue.", "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." }, "operations": { "activities": [ "Merchant onboarding and monitoring", "Routing and authorization handling", "Settlement reconciliation", "Dispute evidence management" ], "assets": [ "Bank and network connections", "Transaction ledger", "Risk models and reliable processing infrastructure" ], "roles": [ "Payments operations analyst", "Fraud specialist", "Compliance officer", "Reliability engineer" ], "records": [ "Authorization and capture record", "Settlement batch", "Merchant payout ledger", "Dispute file" ], "software": [ "Gateway APIs", "Ledger and reconciliation", "Fraud screening" ], "metrics": [ { "name": "Authorization rate", "definition": "Approved payment attempts divided by relevant attempts, with retry handling specified.", "why": "Distinguishes checkout friction from successful sales; repeated retries can distort the number." }, { "name": "Net revenue yield", "definition": "Provider revenue after defined pass-through costs divided by processed value.", "why": "Shows monetization without mistaking gross payment volume for revenue." }, { "name": "Fraud loss rate", "definition": "Fraud losses divided by relevant processed value.", "why": "Tests whether higher acceptance creates acceptable risk." } ] }, "structure": [ "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." ], "risks": [ { "risk": "Ledger mismatch", "mechanism": "A successful user-facing status is not matched by the expected settlement or payout." }, { "risk": "Merchant failure", "mechanism": "A merchant receives money before delivering goods, then cannot fund refunds or disputes." }, { "risk": "Common infrastructure outage", "mechanism": "A network or bank dependency interrupts many merchants simultaneously." } ], "dependencies": { "upstream": [ { "slug": "commercial-banking", "label": "Commercial banking", "relationship": "Banks provide accounts and settlement access." }, { "slug": "telecommunications", "label": "Telecommunications", "relationship": "Transaction messages require secure connectivity." } ], "downstream": [ { "slug": "ecommerce", "label": "E-commerce", "relationship": "Online sellers need checkout, refunds and payouts." }, { "slug": "restaurants", "label": "Restaurants", "relationship": "Merchants accept cards and reconcile terminal sales." } ], "substitutes": [ { "label": "Cash and direct bank arrangements", "relationship": "Can settle purchases without the same merchant-processing stack, while introducing different costs and risks." } ] }, "workedExample": { "title": "Payment volume versus retained revenue", "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." ], "takeaway": "A $4m payment flow produces $12,000 in this illustrative contribution calculation, before fixed overhead and tax." }, "scenario": { "change": "The processor relaxes fraud screening to approve more orders.", "effects": [ "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." ], "watch": [ "Approval rate by merchant and method", "Matured fraud losses", "Dispute and refund rates" ] }, "misconceptions": [ { "claim": "A payment marked authorized is irrevocably received cash.", "correction": "Authorization, capture, settlement and dispute resolution are separate; reversibility depends on the rail and rules." } ], "sources": [ { "id": "fed-ach", "title": "Automated Clearinghouse Services", "organization": "Federal Reserve Board", "url": "https://www.federalreserve.gov/paymentsystems/fedach_about.htm", "supports": "U.S. ACH batch credit/debit transfer structure." }, { "id": "fednow", "title": "FedNow Service", "organization": "Federal Reserve Board", "url": "https://www.federalreserve.gov/paymentsystems/fednow_about.htm", "supports": "Near-real-time interbank clearing, settlement and liquidity support." }, { "id": "stripe-intents", "title": "The Payment Intents API", "organization": "Stripe", "url": "https://docs.stripe.com/payments/payment-intents", "supports": "A provider-specific example of payment lifecycle and authentication states." }, { "id": "stripe-disputes", "title": "How disputes work", "organization": "Stripe", "url": "https://docs.stripe.com/disputes/how-disputes-work", "supports": "Provider-specific card dispute flow, evidence and debits after payment." } ], "evidence": { "scope": [ "fed-ach", "fednow" ], "flow": [ "stripe-intents", "stripe-disputes" ], "economics": [ "stripe-disputes", "fednow" ], "operations": [ "stripe-intents", "stripe-disputes" ], "structure": [ "fed-ach", "fednow" ], "risks": [ "stripe-disputes" ] }, "relatedConcepts": [ "network-effects", "unit-economics", "working-capital" ], "classification": [], "editorialNote": "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.", "companies": { "selectionNote": "Illustrative examples distinguish card networks, merchant payment platforms and consumer payment services. This alphabetical selection is not a transaction-volume, revenue or quality ranking.", "verifiedOn": "2026-10-26", "entries": [ { "name": "Adyen", "kind": "Company", "segment": "Integrated merchant payments", "description": "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.", "url": "https://www.adyen.com/about" }, { "name": "American Express", "kind": "Company", "segment": "Integrated card network", "description": "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.", "url": "https://www.americanexpress.com/en-us/company/our-business/" }, { "name": "Block", "kind": "Company", "segment": "Seller and consumer ecosystems", "description": "Operates businesses including Square and Cash App, connecting merchant tools with consumer financial applications. Its portfolio illustrates distinct entry points into everyday payment activity.", "url": "https://block.xyz/" }, { "name": "Checkout.com", "kind": "Company", "segment": "Online payment processing", "description": "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.", "url": "https://www.checkout.com/" }, { "name": "Fiserv", "kind": "Company", "segment": "Merchant and bank payment technology", "description": "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.", "url": "https://www.fiserv.com/en/about-fiserv.html" }, { "name": "Global Payments", "kind": "Company", "segment": "Merchant payment technology", "description": "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.", "url": "https://investors.globalpayments.com/" }, { "name": "Mastercard", "kind": "Company", "segment": "Payment network", "description": "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.", "url": "https://www.mastercard.com/global/en.html" }, { "name": "PayPal", "kind": "Company", "segment": "Consumer and merchant payments", "description": "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.", "url": "https://about.pypl.com/about-us/default.aspx" }, { "name": "Stripe", "kind": "Company", "segment": "Developer-oriented payment infrastructure", "description": "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.", "url": "https://stripe.com/" }, { "name": "Visa", "kind": "Company", "segment": "Payment network and services", "description": "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.", "url": "https://corporate.visa.com/en/about-visa.html" } ] }, "published": "2026-10-26", "canonical": "https://industrywiki.org/industry/payments/" }