The four parties, and the fifth one you actually talk to
A card payment looks like one event. A customer taps a card, a terminal beeps, and a few days later money appears in a bank account. Underneath that single event sit four separate companies with four separate contracts, none of which is a contract between the customer and the business. Understanding which company holds which relationship is the prerequisite for understanding every fee, every hold, every chargeback, and every sales pitch a business will ever hear about payments.
The company most businesses actually deal with is often none of those four. It is the processor — the technology and service layer that connects a merchant to an acquirer, boards the merchant, sends transactions to the network, reconciles the returns, and produces the monthly statement. Some processors are also acquirers, holding their own bank licence or being owned by a bank. Many are not, and instead resell acquiring capacity sponsored by a bank. Fiserv, Global Payments, and Worldpay are large processors that reach merchants through direct sales, bank referrals, independent sales organizations, and software vendors, which is why two businesses on identical hardware can be on entirely different contracts. Elavon and Chase Payment Solutions are cases where the acquiring bank and the processor are the same institution, which shortens the chain but does not change its shape.
The mistake most businesses make here is assuming the company on the statement is the company holding the risk. It usually is not. The name on the statement is frequently a sales organization; the bank that answers to Visa for that merchant's chargebacks may be an institution the merchant has never heard of and can find only by reading the merchant agreement.
What each party actually does
The clearest way to hold this in your head is to ask, for each party, three questions: whose customer are you, what does the party earn, and what happens to that party if the transaction goes wrong.
| Party | Role | Earns | Relationship |
|---|---|---|---|
| Merchant | Sells goods or services and accepts the card | The sale, minus all card costs | Contracts with the acquirer or the processor |
| Acquirer (acquiring bank) | Underwrites the merchant, holds the merchant account, is financially liable to the network for that merchant | A share of the markup on each transaction | Licensed member of the card network |
| Processor | Boards merchants, routes transactions, handles settlement files and reporting | Markup, per-transaction fees, monthly fees, software | Contracts with the acquirer, the merchant, or both |
| Card network | Operates the switch, writes the rulebook, sets default interchange, arbitrates disputes | Assessment and switching fees from both banks | Licenses issuers and acquirers, not merchants |
| Issuer (issuing bank) | Issues the card, funds the purchase, decides whether to approve it | Interchange, plus interest and cardholder fees | Contracts with the cardholder |
Two things in that table surprise people. The first is that the card network does not take interchange. Visa and Mastercard set the default interchange schedule but the money passes through them to issuers; the networks earn their own assessment, service, and data-processing fees, which are separate and much smaller. The second is that neither network signs merchants. Visa does not board a coffee shop, does not hold its funds, and does not decide whether its application is approved. It writes the rules that oblige the acquirer to do all three, and fines the acquirer when the merchant misbehaves.
Authorization: the two-second conversation
Authorization is a question, not a payment. When a card is presented, the merchant's terminal or gateway sends a message up the chain — processor, acquirer, network, issuer — asking whether the issuer will stand behind a transaction of a given amount at a given merchant. The issuer checks the available credit or balance, runs its own fraud scoring, and returns an approval code or a decline. On the network's own systems this round trip is measured in milliseconds; the delay a customer perceives is mostly the terminal, the connection, and the chip.
An approval does two things. It reserves the amount against the cardholder's line, which is why a hold appears on the customer's account immediately, and it produces an authorization code that the merchant must keep. What it does not do is move a single dollar. No money leaves the issuer at authorization. This is the single most common misunderstanding in the whole system, and it is the reason a business can see approvals all day Saturday and still have nothing in the bank on Monday.
Authorizations also expire. Each card type and merchant category has a window after which an unused authorization goes stale, and a merchant that captures a sale after that window risks a downgrade to a more expensive interchange category or an outright chargeback. Businesses that authorize at order time and ship days later — furniture, custom manufacturing, made-to-order goods — need to understand their authorization windows precisely, because that gap is where avoidable cost accumulates.
Clearing: the batch that turns an approval into a receivable
Clearing is the step where the merchant tells the system that the sale really happened and should now be paid for. In practice it means capturing the authorization and submitting a batch — usually once a day, at a cutoff time the merchant sets or the processor sets by default. The acquirer assembles the batch into a clearing file, sends it to the network, and the network sorts every transaction to the correct issuer and calculates what each bank owes.
Clearing is also where the transaction's cost is finally determined. The interchange category a transaction qualifies for depends on the data present at clearing, not at authorization: whether the card was physically read, whether address verification ran, whether the authorization code matches, how many days elapsed between authorization and capture, and for commercial cards, whether the merchant supplied the enhanced line-item data known as Level 2 and Level 3. A transaction can be authorized cleanly and still clear into an expensive category because a field was missing.
Where money is lost quietly. Late batching is the most common and most preventable cost in card acceptance. A merchant that leaves transactions uncaptured over a weekend can watch a portion of its volume clear into a higher-cost category for no reason other than elapsed time. Automatic daily batch closing is a setting, not a negotiation, and it is worth checking on day one.
Settlement: where the money actually moves
Settlement is the movement of funds between banks. Once the network has cleared the day's transactions, it calculates a net position for every issuer and every acquirer and instructs the actual transfer of funds through settlement banks. The issuer pays the acquirer the transaction amount minus interchange. The network collects its assessments from both sides. The acquirer then pays the merchant the transaction amount minus everything — interchange, assessments, and its own markup — either by deducting fees per transaction or by depositing gross and debiting total fees once a month.
Those two funding conventions matter more than they sound. Under daily net funding, the deposit arriving in the bank account is already net of that day's card costs, so the bank statement never shows what processing cost. Under gross funding with monthly debit, the deposit matches the day's sales and a single fee debit lands at month end, which makes cost visible and reconciliation far easier. Businesses that want to control payment costs should ask for gross settlement with a monthly fee debit, because you cannot manage a number you never see on its own line.
Settlement is also when a transaction becomes final in an accounting sense and not before. The distinction between authorized, captured, settled, and funded is the distinction between four different numbers that will never agree on any given day, and reconciling them is the daily job of every finance team that takes cards at volume.
Where your money sits, and for how long
Between the customer's tap and the merchant's usable balance, funds pass through and rest in several places. The typical sequence, in order:
- The issuer's books. From authorization until settlement, nothing has moved; the amount is simply held against the cardholder's line.
- Network settlement. Funds move between the issuer's and acquirer's settlement banks, usually one business day after clearing, and typically not on weekends or bank holidays.
- The acquirer's or processor's settlement account. Funds sit here while the processor applies fees, holds back reserves, and prepares the payout file. This float is real, and for large processors it is a meaningful part of the business.
- A reserve, if one applies. High-risk merchants, new merchants with no processing history, and merchants that deliver goods long after payment are commonly placed on a rolling reserve: a stated percentage of each day's volume withheld for a stated number of months, then released on a rolling basis.
- The merchant's bank account. Standard funding is generally next business day or two business days, with same-day and instant options usually priced as an extra.
Payment facilitators — Stripe, Square, PayPal, and every software platform that boards businesses as sub-merchants — insert one more custody step, because funds land with the facilitator and are then paid out to the sub-merchant on the facilitator's schedule and at the facilitator's discretion. That discretion is the trade for instant onboarding, and it is why account freezes are a facilitator phenomenon far more than a traditional merchant account phenomenon.
Who carries which risk
Every party in the chain is exposed to a different failure. Confusing them produces bad decisions, most often the belief that the processor is somehow absorbing losses on the merchant's behalf.
| Risk | Who carries it | What it looks like in practice |
|---|---|---|
| Cardholder does not pay their bill | Issuer | Credit loss on the issuer's book; the merchant was already paid |
| Card was used fraudulently | Issuer or merchant, depending on liability shift | Chip-read in person tends to sit with the issuer; card-not-present and non-EMV in-person tend to sit with the merchant |
| Customer disputes the sale | Merchant first | Chargeback: funds are pulled back from the merchant, plus a fee, and the merchant must produce evidence |
| Merchant cannot cover its chargebacks | Acquirer | The acquirer must make the network whole; this is why underwriting, reserves, and personal guarantees exist |
| Merchant breaks network rules | Acquirer, then passed to the merchant | Network fines the acquirer under its brand-protection programs; the acquirer bills the merchant |
| The switch or settlement system fails | Network | Operational and reputational, not credit |
The line to remember is that the acquirer's core business is not technology, it is credit. An acquiring bank is extending unsecured credit to every merchant it boards, because it has guaranteed the network that refunds and chargebacks will be honored even if the merchant is gone. Everything a merchant experiences as friction at signup — the underwriting questions, the personal guarantee, the reserve, the volume cap, the sudden review when a good month arrives — is that credit exposure being managed.
Where the model bends: gateways, PayFacs, and three-party networks
Three common structures sit on top of the four-party model without replacing it.
Gateways
A gateway is the piece that captures card data securely and hands it to a processor. It is not an acquirer and holds no money. Historically gateways were separate companies sold separately; today most full-stack providers bundle one, which is why the word appears on invoices as a line item that some merchants pay twice for without noticing.
Payment facilitators
A payment facilitator, or PayFac, holds one master merchant account with an acquirer and boards businesses underneath it as sub-merchants. That is why a business can sign up with a facilitator in minutes while a traditional merchant account takes days: the underwriting has already been done at the master level, and the facilitator is accepting the risk of its own portfolio. The trade-off is control. The facilitator can hold funds, cap volume, or close an account on its own terms, and the sub-merchant has no direct relationship with the acquiring bank.
Three-party networks
American Express historically operated as a three-party network, issuing its own cards and acquiring its own merchants, which is why its economics have always been described as a discount rate rather than as interchange plus a markup. Discover has a similar heritage. Both now also work through third-party issuers and acquirers, and both are commonly presented to merchants inside a single blended rate, which conceals rather than removes the difference.
What to check before signing anything
Once the chain is clear, due diligence becomes a short list of factual questions rather than a rate comparison. Ask a prospective provider each of these and insist the answer be in writing:
- Who is the acquiring bank? Every legitimate merchant account has one and it must be named in the agreement. A provider that cannot answer plainly is a reseller that does not want you to know how many parties are taking a cut.
- Am I a merchant or a sub-merchant? A direct merchant account and a facilitator sub-account behave completely differently under stress, and stress is exactly when it matters.
- What is the funding timeline, and does it change? Get the standard business-day figure, the cutoff time, the weekend behavior, and the conditions under which funding can be delayed.
- Is there a reserve, and on what terms? Percentage, duration, release schedule, and what triggers an increase.
- Gross or net funding? Ask for gross deposits with a monthly fee debit if the volume justifies it.
- What ends the contract? Term, auto-renewal, early termination amount, and notice period. These live in the program guide, not the pricing page.
None of those questions is about price, and all of them determine what the relationship costs. A business that understands the difference between authorization, clearing, and settlement — and knows which party is exposed at each step — is already better equipped than most of the salespeople it will meet.
Frequently asked questions
What is the difference between an acquirer and a processor?
An acquirer is a bank licensed by the card networks that underwrites the merchant, holds the merchant account, and is financially liable to the network for that merchant's chargebacks. A processor is the technology and service layer that routes transactions, boards merchants, and produces statements. Some companies are both, but many processors and independent sales organizations resell acquiring sponsored by a bank the merchant never speaks to, and that bank must still be named in the merchant agreement.
Does money move when a card payment is authorized?
No. Authorization only asks the cardholder's issuing bank whether it will stand behind the transaction, and an approval reserves the amount against the cardholder's line without transferring anything. Funds move later, at settlement, after the merchant captures the transaction and the batch clears through the network. This is why a merchant can have a day of approvals and no deposit yet.
What is the difference between clearing and settlement?
Clearing is the exchange of transaction records: the merchant submits its batch, the network sorts each transaction to the right issuer, and the final interchange category and cost are determined from the data present at that point. Settlement is the actual movement of funds between the issuing bank and the acquiring bank, which typically happens the following business day. Clearing decides what is owed; settlement pays it.
Who is liable for a chargeback?
The merchant is liable first: the funds are debited back out of the merchant's account along with a chargeback fee, and the merchant must supply evidence to contest it. If the merchant cannot cover the amount, the acquiring bank absorbs the loss because it has guaranteed the card network that the transaction will be made good. That exposure is the reason acquirers underwrite merchants, take personal guarantees, and impose reserves.
How long does it take to get paid after a card transaction?
Standard funding is commonly one to two business days after the batch settles, with weekends and bank holidays excluded, though the exact timeline depends on the provider, the batch cutoff time, and the merchant's risk profile. Same-day and instant deposit options usually exist and are priced as an add-on. Merchants on a reserve receive only part of each day's volume until the reserve period elapses.
What is a rolling reserve?
A rolling reserve is an amount the acquirer or facilitator withholds from each day's settlement, expressed as a percentage of volume and held for a stated number of months before being released on a rolling basis. It exists to cover chargebacks and refunds if the merchant stops trading. Reserves are most common for high-risk categories, brand-new merchants with no processing history, and businesses that take payment long before delivering.
Do Visa and Mastercard collect interchange?
No. Visa and Mastercard set the default interchange schedules and operate the systems that move the money, but interchange passes through them to the card-issuing banks. The networks earn their own revenue from assessment, service, switching, and cross-border fees charged to issuers and acquirers. Neither network signs merchants, holds merchant funds, or sets a merchant's price.