What a payment processing company actually sells
Every company on this page sells the same underlying thing: the ability for a business to take money from a customer who is paying with a card, a bank account or a wallet, and to end up with that money in its own account a day or two later. What separates them is not the outcome. It is which parts of the chain between those two points each company owns, which parts it rents from somebody else, and which party is left holding the loss when a transaction goes bad.
That definition is doing more work than it appears to. A business can buy card acceptance from a company that is itself the acquiring bank, such as Chase Payment Solutions, where JPMorgan Chase is both the institution that underwrites the merchant and the processor that moves the transaction. It can buy from Elavon, the acquiring arm of U.S. Bank. It can buy from Adyen, which holds a Dutch banking licence and is a principal member of the card networks in its licensed markets. Or it can buy from a company that owns none of that and resells somebody else's sponsorship, which is what most merchant services providers, most independent sales organizations, and every high-risk broker are doing.
None of those arrangements is inherently better. A reseller with a good bank relationship can serve a merchant better than a direct bank channel with poor service. But a business that does not know which arrangement it has bought cannot predict what happens to it under stress, and stress is when the differences appear.
The distinction that decides everything: dedicated account or master account
The single most consequential question in this category is whether the business holds a merchant account in its own name, or is boarded as a sub-merchant under somebody else's master account. This is the difference between the traditional acquiring model and the payment facilitator, or aggregator, model.
The aggregator model exists because dedicated underwriting is slow and expensive. A traditional acquirer will ask for financial statements, processing history, a personal guarantee, and details of the business model before it agrees to carry the risk. That process takes days at best. An aggregator collects a name, a bank account and a category, checks it against automated rules, and turns acceptance on immediately. For a business selling its first product, that difference is not a nuance. It is the difference between launching this afternoon and launching next month.
The cost shows up later. Under an aggregator, the merchant has no account of its own and no direct relationship with the acquiring bank. Its acceptance can be suspended by a risk model rather than a conversation. Funds can be held while the aggregator assesses exposure, because the aggregator, not the merchant, is the party that owes the acquirer if refunds and chargebacks exceed what is left in the account. Under a dedicated merchant account the underwriting happened up front, a reserve was negotiated in writing, and a merchant that trips a monitoring threshold usually gets a risk review, a request for documentation, and a defined period to respond.
| Dedicated merchant account | Aggregator master account | |
|---|---|---|
| Who holds the account | The merchant, with an acquiring bank named in the agreement | The facilitator; the merchant is a sub-merchant |
| Underwriting | Before boarding, on documents | Largely automated, mostly after boarding |
| Time to first transaction | Days to weeks | Usually immediate |
| Reserve terms | Negotiated and written into the agreement | Imposed at the facilitator's discretion |
| When risk flags the account | Review, documentation request, notice period | Acceptance can stop first, discussion second |
| Typical fit | Established volume, thin margins, unusual model | New businesses, low volume, standard categories |
The mistake most businesses make here is treating the aggregator relationship as permanent infrastructure because it was easy to start. A company that grows from a hobby into real volume, and whose entire revenue depends on an account it does not hold and did not negotiate, has accumulated a risk it never priced.
Seven business models wearing the same job title
The 31 companies grouped here fall into seven working categories. They are not marketing segments; they describe what each company does inside a transaction and where its money comes from.
- Acquirers and large processors. The scale players that own the merchant relationship end to end. Fiserv, Global Payments, Worldpay, Elavon, Chase Payment Solutions, Heartland and North. These are the companies whose names appear on the settlement side of most US card volume, usually sold through banks, agents and independent sales organizations rather than direct.
- Payment service providers and aggregators. Stripe, Adyen, PayPal, Braintree, Checkout.com, Square, Nuvei and Paysafe. Fast onboarding, published or semi-published pricing, and strong developer tooling, with the master-account trade-off attached in most cases. Adyen and Checkout.com are the exceptions worth knowing: both hold their own acquiring permissions rather than sitting on a third party's.
- SMB merchant services. Helcim, Stax Payments, Gravity Payments and SumUp compete on published pricing and service rather than on scale. Helcim publishes its interchange-plus margins openly; Stax is built around a fixed monthly membership plus interchange at cost rather than a percentage markup. For a small business with steady volume, this group is frequently the most honest arithmetic available.
- Commerce and POS platforms. Toast, Clover and Shopify Payments sell software first and payments second. Payments are the module that pays for the rest, which is why leaving the payments product usually means leaving the platform. Shopify Payments is the clearest illustration of how deep the layering goes: it is Shopify's brand and Shopify's merchant agreement, processed by Stripe underneath.
- Gateways. Authorize.net, NMI and CardConnect provide the authorization layer between a merchant and a processor. Authorize.net is a Visa subsidiary and is most often used to connect an existing merchant account to a website or virtual terminal. NMI is sold white-label to independent sales organizations, software vendors and banks rather than to merchants. A gateway alone does not give a business a merchant account, and a merchant that thinks it has bought processing when it has bought a gateway will find out at settlement.
- High-risk specialists. PaymentCloud and Durango Merchant Services place merchants that mainstream aggregators decline. Neither underwrites or acquires; they broker placements with third-party acquiring banks and gateways, with Durango sponsored domestically by Fifth Third Bank, N.A. This is the least transparent corner of the industry and the one where reading the actual agreement matters most.
- Cross-border and global acquiring. dLocal, EBANX, Airwallex and Payoneer are organized around local acceptance methods, local settlement and foreign exchange rather than around one domestic card market. dLocal and EBANX exist because a card-first stack collects badly in markets where consumers pay by local instant transfer, cash voucher or domestic scheme.
Pricing models, and why the model predicts the bill
Card pricing has three components and only one of them is genuinely negotiable. Interchange is the portion that goes to the cardholder's issuing bank; it is set by the card network in published tables, it varies by card type and merchant category, and no processor, acquirer or merchant can negotiate it. Network assessments go to Visa or Mastercard themselves and are similarly fixed. The processor's markup is the third component, and it is the only line any provider actually controls.
The pricing model determines how much of that structure a business can see:
- Interchange-plus shows interchange and assessments at cost and states the markup separately. It is the only model in which a merchant can verify what it was charged.
- Flat-rate blends all three into one number. It is predictable and simple, which suits low volume and irregular card mixes, and it becomes expensive as volume grows and the mix stabilizes.
- Subscription or membership charges a fixed monthly fee plus interchange at cost plus a fixed amount per transaction. It performs well at higher volume with a low average ticket, and badly at low volume, where the fixed fee dominates.
- Tiered pricing sorts transactions into qualified, mid-qualified and non-qualified buckets defined by the provider. The definitions are not standardized and can be changed unilaterally. It is a bad deal for almost every merchant, and the mechanism is simple: the provider decides which bucket a transaction falls into, and the merchant has no way to audit the decision.
Comparing quotes across models is where businesses lose money. A flat rate looks cheaper than an interchange-plus quote until the mix shifts toward rewards and commercial cards, which carry higher interchange that the flat rate has been absorbing. The right comparison is not two headline numbers; it is a full month of the business's own transaction data run through both structures, plus every recurring item that never appears in a sales conversation — monthly minimums, statement fees, PCI compliance fees, batch fees, gateway fees, chargeback fees, and whatever the exit terms cost.
What happens when something goes wrong
Payment processing is a credit business dressed as a technology business. When a merchant accepts a card, the acquirer is effectively lending against the possibility that the customer will dispute the charge and the merchant will not be there to cover it. Everything that feels arbitrary about processor behavior follows from that single fact.
A chargeback is the cardholder's right to reverse a transaction through the issuing bank. The merchant loses the sale, the goods and a chargeback fee, and card network monitoring programs measure chargebacks as a ratio of transactions. Cross the thresholds and the merchant enters a remediation program with fines and timelines attached; stay there and the acquirer will terminate the account rather than keep paying penalties. A terminated merchant can be added to the industry's terminated merchant file, which makes obtaining a new account substantially harder for the years the listing persists.
The practical difference between the models shows up precisely here. Under a dedicated merchant account, the merchant is the acquirer's customer and the acquirer's exposure is documented; the process runs on notice periods and evidence. Under an aggregator, the facilitator carries the loss, and the fastest way for a facilitator to stop a loss is to stop the payouts. Businesses that discover this the hard way — a sudden pivot into a restricted product, a viral spike that looks like fraud to a model, a pre-order campaign that pulls settlement far ahead of delivery — are rarely victims of malice. They are on the wrong side of a risk arrangement they never read.
Businesses with genuine exposure to this should ask three questions before signing anything: who is the acquiring bank named in the agreement, what triggers a reserve or a hold and how is that communicated, and what is the documented process for getting funds released.
When a payment processing company is the wrong purchase
A reference that only flatters its subject is not useful. Several kinds of business arrive looking for a payment processor when the answer is somewhere else entirely.
Software platforms that want to monetize their customers' payments do not need a merchant account; they need embedded payments infrastructure. Signing up for a standard processing account and reselling it produces a compliance problem and no revenue share worth having. That work belongs to PayFac-as-a-service providers and acquirer-processors built for platforms.
Businesses whose problem is the invoice, not the authorization, are misdiagnosing. A company chasing net-30 payments from other companies has an accounts receivable workflow problem. Card acceptance is a small and expensive part of that, and B2B accounts payable and receivable platforms address it directly.
Healthcare providers billing through insurers need eligibility checks, claims, remittance and denial management before they need better card acceptance. General-purpose processing sits at the wrong end of that process. Utilities, municipalities and insurers collecting recurring non-discretionary bills need presentment and posting back into a billing system, which is an electronic bill presentment and payment product, not a merchant account.
Subscription businesses with billing complexity — proration, plan changes, dunning, revenue recognition, tax across jurisdictions — should be clear that no processor solves this. A billing platform sits above the processor and manages the customer relationship; the processor only moves the card transaction.
And a business that has been told it is high-risk should test that claim before paying for it. Category matters, but so does presentation. A business with clean history, documented delivery timelines and a coherent refund policy often gets a better answer from a mainstream provider than the first broker who quoted it a specialty rate.
How to evaluate a payment processing company
Most comparison exercises collapse into a rate hunt, which is the least informative dimension available. A more useful evaluation asks a short list of structural questions, and every provider in this category can answer them.
- Which entity is the acquirer? Ask for the name of the acquiring bank in the merchant agreement. A provider that will not answer plainly is a reseller that would prefer you did not know.
- Dedicated account or sub-merchant? Everything about holds, reserves, notice and portability follows from this answer.
- Is the pricing model auditable? Interchange-plus and subscription pricing can be checked against network tables. Tiered pricing cannot be checked at all.
- What is the total recurring cost? Ask for a written list of every fee that recurs, including the ones charged annually, and the conditions under which each applies.
- What are the exit terms? Contract length, renewal mechanics, early termination, equipment leases, and what happens to stored card credentials on the way out.
- Are the payment credentials portable? A merchant whose stored cards cannot be exported to another provider is locked in by data, whatever the contract says about notice periods.
- Who answers when settlement fails? Support quality is the most-cited complaint in this industry and the least-discussed line in a comparison table.
Then run the arithmetic against a real month of the business's own transactions rather than an assumed average ticket. Volume, average ticket, card mix, card-present share and refund rate change the answer more than any headline rate does, which is why two businesses with identical revenue can rationally choose opposite ends of this category.
Frequently asked questions
What is the difference between a payment processor and a payment gateway?
A payment gateway captures card details and passes an authorization request to a processor; it is the connection layer. A payment processor moves the transaction through the card networks and into settlement, and the acquiring bank behind it holds the merchant account and carries the financial risk. Authorize.net and NMI are gateways; a business using only a gateway still needs a merchant account underneath it. Many companies, including Stripe, Adyen and Checkout.com, provide both layers, which is why the terms get used interchangeably.
What is the difference between a merchant account and a payment aggregator account?
A merchant account is held in the business's own name with a named acquiring bank that underwrote the business before boarding it. An aggregator account, used by payment facilitators such as Stripe, Square, PayPal and Shopify Payments, boards the business as a sub-merchant under the facilitator's own master account. The aggregator model is faster to open and simpler to price; the dedicated account gives the business a documented reserve arrangement, a notice period and a direct relationship with the bank carrying its risk.
Are payment processing companies and merchant acquirers the same thing?
Not always. The acquirer is the licensed institution that holds the merchant account and carries the liability for chargebacks and merchant failure. A processor operates the technology that authorizes, clears and settles transactions. Some companies are both, such as Chase Payment Solutions, Elavon and Adyen. Many companies selling processing are neither, and are reselling an acquirer's sponsorship under their own brand.
Why do payment processors hold or freeze a merchant's funds?
Because the party settling the money is exposed until the customer's right to dispute the charge expires. If a merchant takes payment and does not deliver, the acquirer or payment facilitator refunds the cardholders out of its own pocket. Holds, rolling reserves and account suspensions are the tools used to cap that exposure, and they are triggered most often by sudden volume increases, an unusually high refund or chargeback rate, long delivery lead times, or a change in what the business is selling.
Does a business classified as high-risk need a specialist processor?
Only if mainstream providers decline it or terminate it. High-risk specialists such as PaymentCloud and Durango Merchant Services broker placements with acquiring banks that accept categories the large aggregators refuse, and that access is priced accordingly, often with reserves and longer contracts attached. A business should test whether mainstream underwriting will actually accept it, with clean documentation, before paying for specialist placement it may not need.
Is interchange-plus pricing always cheaper than flat-rate pricing?
No. Interchange-plus is more transparent because it separates the non-negotiable network costs from the provider's markup, but at low volume a flat rate can cost less once monthly minimums, statement fees and per-item charges are counted. The decision turns on monthly volume, average ticket, card mix and the share of card-present transactions. The only reliable comparison is running one real month of a business's own transaction data through both structures.