8 min read
PayFac vs. Merchant Acquirer: Who Holds the Account and Who Carries the Risk
PayFac vs. merchant acquirer explained: the acquirer is the bank that settles with the card networks, the payfac sits under it with one master account. How money flows, who underwrites whom, and who pays when a merchant fails.

Quick answer: A merchant acquirer is the bank (or licensed institution) that is a member of Visa and Mastercard, holds merchant relationships, and settles card payments with the networks. A payment facilitator (payfac) is a company that holds one master merchant account with an acquirer and signs up many businesses underneath it as sub-merchants. The acquirer underwrites the payfac. The payfac underwrites its sub-merchants. The two aren't competing options. A payfac can't exist without an acquirer sponsoring it.
That's why "payfac vs. acquirer" is a slightly odd question. You never really choose between them. You choose whether you have a direct relationship with an acquirer (your own merchant ID, usually through an ISO) or an indirect one through a payfac like Stripe, Square or PayPal. The acquirer is in the chain either way.
What a merchant acquirer does
An acquirer, sometimes called an acquiring bank or merchant bank, is the party the card networks hold responsible for the merchants it brings in. Chase, Worldpay, Fiserv and Elavon (through U.S. Bank) are acquirers you've heard of. Adyen and Stripe both hold acquiring licenses in some markets, which is part of why the labels get blurry.
The acquirer's job comes down to three things:
- Membership. It's a principal member of Visa and Mastercard, so it can submit transactions to the networks and receive settlement.
- Settlement. It receives the money from card issuers (minus interchange) and pays it out to merchants.
- Liability. If a merchant goes bust with $200,000 of chargebacks it can't cover, the networks look to the acquirer to make the issuers whole.
That last point drives everything. Because the acquirer carries the loss, it underwrites carefully, asks for financials, sets reserves, and takes days or weeks to approve a new merchant. Underwriting is slow because the acquirer is the one paying for its mistakes.
What a payfac does
A payfac takes on the work the acquirer would rather not do for small merchants. It holds a single master merchant account with a sponsoring acquirer, registers with the card networks as a payment facilitator, and then onboards sub-merchants under that account using its own KYC and risk systems.
The result is the Stripe experience. You sign up, enter a bank account and a tax ID, and take a payment the same afternoon. The acquirer never looked at your business individually. It looked at Stripe.
For a full walkthrough of the model, see what a payment facilitator is.
PayFac vs. merchant acquirer side by side
| Merchant acquirer | Payment facilitator (payfac) | |
|---|---|---|
| What it is | Network member bank or licensed institution | Company sponsored by an acquirer |
| Card network relationship | Direct principal member | Registered through its sponsor acquirer |
| Merchant account | Issues individual merchant IDs (MIDs) | Holds one master account; merchants are sub-merchants |
| Who it underwrites | Each merchant (or the payfac) | Each sub-merchant, with its own rules |
| Onboarding time | Days to weeks | Minutes to a day |
| Settlement | Receives funds from the networks | Receives funds from the acquirer, then pays sub-merchants |
| Ultimate liability to the networks | Yes | No, but it's contractually liable to its acquirer |
| Pricing to merchants | Usually interchange-plus, negotiable | Usually flat blended rate |
| Examples | Chase, Worldpay, Fiserv, Elavon | Stripe, Square, PayPal, Shopify Payments |
How the money actually moves

Say a customer buys a $100 annual plan from a small SaaS company that uses a payfac.
- The card is authorized through the payfac's gateway, which routes it to the processor and on to the card network and the customer's issuing bank.
- The issuer approves it and later settles about $98 to the acquirer. The other $2 or so is interchange and network fees.
- The acquirer credits the payfac's master merchant account.
- The payfac takes its margin (its blended rate minus what it actually paid) and pays out the SaaS company on its own schedule, often two business days.
A merchant with its own MID skips step 4. The acquirer (or its processor) pays the merchant directly.
That extra step explains why payfac payouts can be paused or held. The funds sit with the payfac before they reach you, and the payfac's risk team decides when they move.
Who pays when something goes wrong

This is where the relationship gets interesting. Picture a sub-merchant that sells $300,000 of preorders and then disappears. Customers file chargebacks.
The issuers pull the money back from the acquirer, because that's who the networks hold responsible. The acquirer then recovers it from the payfac under their sponsorship agreement. The payfac tries to recover it from the sub-merchant's reserves, future payouts, or (good luck) the sub-merchant itself. Whatever it can't recover, the payfac eats.
So risk runs down a waterfall. The acquirer is liable to the networks, the payfac is liable to the acquirer, and the sub-merchant is liable to the payfac. That chain is why payfacs freeze accounts that look unusual. They're protecting their master account, and with it their sponsorship.
Visa's rules also cap how big a sub-merchant can get before the acquirer needs a direct agreement with it. Historically, that threshold is around $1 million in annual Visa volume. Past that point, a growing business usually moves to its own merchant account. The compliance work involved is covered in our guide to payment facilitator compliance requirements.
Acquirer vs. processor vs. payfac
People mix these up constantly, partly because one company often plays all three roles.
The processor is the technical layer that moves authorization and settlement messages between the merchant side and the networks. The acquirer is the regulated, network-member layer that carries liability and settles the money. Many acquirers run their own processing (Fiserv, Worldpay), and many processors work with partner banks for acquiring. The payfac sits on top of both and onboards sub-merchants. For more on how the layers stack, see payfac vs. payment processor.
Which one should your business deal with?
If you process under about $1 million a year in card volume, you'll almost certainly be on a payfac, and that's fine. You get speed and a simple price.
Above that, or if your average transaction is large, a direct acquiring relationship (usually through an ISO; see payfac vs. ISO) gets you your own MID, negotiated interchange-plus pricing and a more stable account. Software platforms that want to embed payments for their own customers face a third question, which is whether to become a payfac, use PayFac-as-a-Service, or refer merchants. PayFac vs. ISV covers that decision.
Notice that neither the acquirer nor the payfac makes you any less the seller. Both leave you as the merchant, so sales tax, VAT and consumer-law obligations stay with you. Only a merchant of record takes those on, because only the MoR becomes the legal seller.
Frequently Asked Questions
What is the difference between a payfac and a merchant acquirer?
A merchant acquirer is the card-network member bank that holds merchant relationships, settles payments and carries ultimate liability to the networks. A payfac holds one master merchant account with an acquirer and onboards many sub-merchants beneath it. The acquirer underwrites the payfac, and the payfac underwrites its sub-merchants.
Is a payfac an acquirer?
No. A payfac is sponsored by an acquirer and can't process card payments without one. Some large payment companies hold acquiring licenses in certain markets and also run payfac programs, which is why companies like Stripe and Adyen are sometimes described as both.
Is Stripe a payfac or an acquirer?
For most businesses, Stripe works as a payfac. You're a sub-merchant under Stripe's account rather than having your own merchant ID. Stripe also works with acquiring banks and holds acquiring licenses in some regions, so the label depends on the market.
What is a sponsor bank?
A sponsor bank is the acquirer that sponsors a payfac's registration with the card networks and holds its master merchant account. It's responsible to the networks for the payfac's activity and oversees how the payfac underwrites and monitors sub-merchants.
Who is liable for chargebacks, the payfac or the acquirer?
Both, in sequence. The networks recover chargebacks from the acquirer. The acquirer recovers them from the payfac, and the payfac recovers them from the sub-merchant if it can. If the sub-merchant can't pay, the payfac absorbs the loss.
Is a merchant acquirer the same as a payment processor?
Not exactly. The acquirer is the regulated entity that holds the merchant relationship and settles funds. The processor is the technical layer that routes transactions. Many companies are both, which is why the terms often get used interchangeably.
The bottom line
The acquirer is the bank-level foundation, and the payfac is a faster on-ramp built on top of it. Pick a payfac for speed at low volume and a direct acquiring relationship for control at scale. Then remember that tax and legal-seller liability aren't covered by either. If you sell software or digital products internationally and want those handled too, Comecero acts as your merchant of record for verified customers, after review, or runs billing on top of the acquiring relationship you already have.




















