Every time a customer pays with a card, an invisible piece of infrastructure does the work of checking that the money exists, reserving it, and moving it from the customer’s bank to the merchant’s. That infrastructure is the payment processor. It is the engine that turns a tap, dip, or click into settled funds in a merchant’s account, and although customers never see it and most merchants rarely think about it, it sits in the path of every card transaction a business accepts.
Understanding what a payment processor does (and how it differs from the gateway, the acquirer, the card networks, and the payment service provider it is so often confused with) matters because the processor shapes the fees a business pays, the speed at which it receives funds, the share of transactions that get approved, and the reliability of the whole payment operation. What follows explains what a payment processor is, how it moves money step by step, the types and pricing models to know, and how to evaluate one.
A payment processor is the company that manages the movement of a card transaction between the merchant, the card networks, and the banks, handling the authorization of the payment and the settlement of the funds. When a customer pays, the processor is the party that carries the authorization request to the customer’s bank, relays back the approve-or-decline decision, and then, later, moves the actual money from the customer’s bank to the merchant’s account.
Where a payment gateway captures and transmits the payment information, the processor acts on it. It communicates with the card networks and the issuing bank to authorize the transaction, and it handles the settlement process that transfers the funds. The processor is the operational engine of the payment: the component that does the work of moving money, as distinct from the component that collects the payment details.
Well-known payment processors include companies such as Stripe, Square, and PayPal, though many of these bundle processing with other functions. The pure processing role (authorize the transaction, settle the funds) is the core of what defines a processor, whatever else a given provider packages around it.
The processor’s role is clearest when followed through a single card transaction, from the moment a customer confirms payment to the moment the money lands in the merchant’s account. Two distinct phases are involved: authorization (real-time) and settlement (which follows later).
Authorization, in real time:
1. The transaction reaches the processor. After the gateway captures and encrypts the payment data at checkout, it passes the transaction to the processor. In an in-person sale, the point-of-sale terminal performs the capture role and hands the transaction to the processor.
2. The processor forwards an authorization request. The processor formats the transaction and sends an authorization request through the appropriate card network (Visa, Mastercard, and others) to the customer’s issuing bank.
3. The issuing bank decides. The issuing bank checks that the card is valid and that funds or credit are available, runs the transaction against its fraud and risk rules, and returns an approve-or-decline response.
4. The processor relays the decision. The response travels back through the card network to the processor, which passes it to the gateway and the merchant. If approved, the sale completes for the customer and the funds are placed on hold in the customer’s account.
Settlement, which follows later:
5. Transactions are batched. The merchant’s approved transactions are collected, typically batched together at the end of the business day.
6. The processor initiates settlement. The processor works with the card networks and banks to move the actual funds. The issuing bank transfers the money, the card network routes it, and it flows toward the merchant’s acquiring bank.
7. Funds reach the merchant. After the acquiring bank processes the settlement (and the processor’s and networks’ fees are accounted for), the funds are deposited into the merchant’s account, usually within one to three business days.
The distinction between authorization and settlement is the key thing to hold onto. Authorization is the instant approve-or-decline that happens while the customer waits. Settlement is the actual transfer of money that happens afterward, in batches. The processor is central to both, which is why it is described as the engine of the payment: it does not merely carry information, it drives the movement of funds. Gr4vy’s guide on payment settlement covers the settlement phase in depth, and the guide on how a credit card scheme works explains the card network’s role in the middle.
The payment processor is constantly confused with the other components of the payment stack. Clean definitions of each:
A useful mental model: the gateway is the front door where the payment enters, the processor is the engine that carries the request to the banks and moves the money, the card network is the road the request travels, and the acquirer is the merchant’s bank where the money arrives. Many modern providers combine the gateway and processor roles (and sometimes the acquiring relationship), which is exactly why the terms blur together in everyday use.
Processors can be grouped in a few ways that matter to a merchant’s decision.
By pricing and relationship model:
By channel:
Many processors handle both the front-end and back-end roles, but the distinction matters for understanding where different parts of the process happen and where problems can arise.
By integration approach: some processors are tightly bundled with a specific gateway or platform, while others are provider-agnostic and can be connected through different gateways or an orchestration layer. This affects how easily a business can change processors later.
Pricing is where processors differ most in ways that directly affect a merchant’s costs, and understanding the models is essential to evaluating any processor. Three main structures dominate.
Interchange-plus. The processor charges the underlying interchange fee (set by the card networks and passed through to the issuing bank) plus a transparent, fixed markup. This is generally the most transparent model, because the merchant can see the true network cost separately from the processor’s margin. It tends to be the most cost-effective for higher-volume and established businesses.
Flat-rate. The processor charges a single, simple rate for all transactions (for example a fixed percentage plus a small fixed fee), regardless of the underlying card type. This is predictable and easy to understand, which suits smaller businesses, but it can be more expensive overall because the processor builds a cushion into the flat rate to cover its own costs across all card types.
Tiered. The processor sorts transactions into tiers (typically labelled qualified, mid-qualified, and non-qualified) and charges different rates for each. This model is the least transparent, because how a transaction gets categorized is not always clear to the merchant, and transactions can be shifted into more expensive tiers in ways that are hard to predict.
Underlying all of these is interchange, the fee set by the card networks and paid to the issuing bank, which the processor passes through in one form or another. Because interchange is a cost every processor faces, the real comparison between processors comes down to the markup and the transparency of the model rather than the interchange itself. Gr4vy’s guide on credit card processing fees breaks down the full fee structure a merchant encounters.
The processor is not a neutral pipe; its performance and terms feed directly into several things a business cares about.
Cost of accepting payments. The processor’s pricing model and markup are a direct input to the total cost of every transaction, which at scale is a meaningful line item.
Authorization rates. How a processor connects to the networks and issuers, and how it handles retries and declines, affects how many transactions get approved. A processor with weaker connectivity to certain issuers or geographies approves fewer transactions there.
Speed of funding. How quickly the processor settles determines when a business actually receives its money, which affects cash flow, particularly for businesses operating on thin margins or tight cycles.
Reliability. If the processor has an outage, transactions fail. A business dependent on a single processor has no fallback when that processor goes down, which is one of the reasons businesses with significant volume connect to more than one.
Supported methods and markets. The processor determines which card types, currencies, and markets a business can serve. A processor with narrow coverage constrains where and how a business can sell.
The right processor depends on the business, but a consistent set of criteria applies.
Pricing model and total cost. Understand which pricing model the processor uses and model the true total cost against the business’s actual transaction mix and volume. Interchange-plus tends to favor higher-volume businesses through transparency; flat-rate favors simplicity for smaller ones. Look past the headline rate to the complete fee schedule.
Authorization performance. Ask about approval rates, particularly for the card types, issuers, and markets that matter to the business. Small differences in approval rates compound into significant revenue over time.
Funding speed. Confirm how quickly the processor settles funds, and whether that cadence works for the business’s cash-flow needs.
Supported methods and geographies. Check that the processor supports the payment methods, currencies, and countries the business needs now and plans to need soon.
Reliability and support. Consider the processor’s uptime and the quality of its support, since processing failures directly stop revenue. For businesses where downtime is costly, consider whether relying on a single processor is acceptable.
Integration and flexibility. Assess how the processor integrates and how hard it would be to change or add processors later. A business locked to a single processor has less negotiating power and less resilience than one that can route across several.
That last point is where growing businesses often reach the limits of a single processor. Depending on one processor means one set of authorization characteristics, one pricing relationship, and one point of failure. As volume and complexity grow, businesses commonly connect to multiple processors and route transactions across them to improve approval rates, control costs, and add redundancy, which is the role a payment orchestration layer plays above the individual processors. Gr4vy’s guides comparing payment orchestration and a payment processor and the full orchestration versus gateway versus processor comparison cover how that layer works.
A payment processor is the company that moves a card payment through the system: it carries the authorization request to the customer’s bank, relays back the approve-or-decline answer, and then moves the actual funds from the customer’s bank to the merchant’s account. It is the engine that turns a card payment into settled money, handling both the real-time authorization and the later settlement of funds.
A payment gateway captures the payment details at checkout and transmits them securely. A payment processor acts on those details: it moves the authorization request through the card networks to the banks and handles the settlement of funds. The gateway handles the information; the processor handles the money movement. Many providers offer both, which is why the terms are often used interchangeably even though they describe different roles.
A card network (such as Visa or Mastercard) is the system that routes transaction data between the customer’s issuing bank and the merchant’s acquiring bank and sets the scheme’s rules. A payment processor is the company that manages the transaction on the merchant’s behalf, sending the authorization request through the network and handling settlement. The network facilitates the data transfer between banks; the processor manages the transaction and moves the money.
Processors earn revenue mainly through the fees they charge merchants for each transaction. Depending on the pricing model, this is either the interchange fee plus a transparent markup (interchange-plus), a single flat rate, or tiered rates. The interchange portion is set by the card networks and passed to the issuing bank; the processor’s own revenue comes from the markup it adds on top.
The three main models are interchange-plus (the network interchange fee plus a fixed, transparent markup), flat-rate (a single simple rate for all transactions), and tiered (transactions sorted into qualified, mid-qualified, and non-qualified tiers at different rates). Interchange-plus is the most transparent and often the most cost-effective at volume; flat-rate is the simplest; tiered is the least transparent.
Authorization is the real-time step where the processor asks the customer’s bank to approve the transaction and reserve the funds; it happens in seconds while the customer waits. Settlement is the later step where the actual money is transferred from the customer’s bank to the merchant’s account, typically processed in batches at the end of the day and completed within one to three business days. The processor is central to both.
For online payments, a business generally needs both functions: the gateway to capture and transmit the payment data, and the processor to authorize the transaction and settle the funds. They can come from separate providers or be bundled together in a single package, which is what many payment service providers offer. The functions are distinct even when one company provides both.
Most processors settle and deposit funds within one to three business days after the transaction, though the exact timing depends on the processor, the merchant’s account setup, and the batching schedule. Some offer faster or same-day funding options. Funding speed is worth confirming during evaluation because it directly affects a business’s cash flow.
Yes, and many growing businesses do. Using multiple processors provides redundancy so that a single processor outage does not stop all payments, lets a business route each transaction to whichever processor performs best for that card type or market, and preserves negotiating power. Connecting and routing across multiple processors is the role a payment orchestration layer performs above the individual processors.
A payment processor performs the specific function of authorizing and settling transactions. A payment service provider (PSP) is a company that bundles several payment functions together, typically including processing along with a gateway and an acquiring relationship, so a merchant can accept payments through one provider. A PSP includes processing as part of a broader package rather than being a distinct function.
Evaluate the pricing model and true total cost against your transaction mix and volume, the authorization performance for your key card types and markets, funding speed, supported payment methods and geographies, reliability and support quality, and how easily you could add or change processors later. For a business expecting growth, it is also worth considering whether a single processor will remain sufficient or whether routing across several will eventually be needed.
A payment processor is the engine of a card payment: the component that carries the authorization to the customer’s bank, brings back the decision, and moves the money to the merchant. It works alongside the gateway that captures the payment, the card networks that route the data, and the acquiring bank that receives the funds, and it is distinct from each of them even though modern providers often bundle several roles together. Its pricing model shapes what a business pays, its connectivity shapes how many transactions get approved, and its reliability shapes whether payments keep flowing.
For a single-market business, one well-chosen processor is often enough to start. The limits appear with growth, when depending on one processor means one set of approval characteristics, one pricing relationship, and one point of failure. That is when businesses tend to connect several processors and route across them, which is what a payment orchestration platform is built to coordinate: many processors and providers through one integration, with each transaction routed to the one most likely to serve it best.
Gr4vy is a cloud-native payment orchestration platform that connects merchants to more than 400 payment providers and methods through a single integration, sitting above individual processors to route, optimize, and add redundancy across all of them. To understand how processors fit into a broader payment strategy for your business, talk to our team.
San Mateo, July 28: Wizlo, the operating system powering end-to-end telehealth infrastructure for modern e-commerce…
Picture a large retailer on the busiest sales day of its year. Its single acquiring…
Payment orchestration is easier to understand through what it does than through how it is…
The second quarter of 2026 was packed with new capabilities across the Gr4vy platform, all…
By the time an enterprise sits down to evaluate payment orchestration platforms, the shortlist tends…
A payment gateway is the technology that captures a customer's payment details at checkout, encrypts…