Merchant services
Anyone Can Resell Payments. Almost No One Can Run a PayFac.
"Payment processing" sounds like a commodity. Plug in an API, take a few basis points, move on. Thousands of companies resell it that way, and from the outside a payment facilitator looks like one more of them.
In this article
It is not. A reseller may hand the merchant to another provider’s risk team, balance sheet and compliance program. A payment facilitator takes on responsibilities under its acquiring agreement.
What a PayFac actually carries
Every sub-merchant is a credit decision. If a merchant takes $80,000 in deposits for furniture and never ships it, responsibility for chargebacks and any shortfall follows the applicable account and acquiring agreements. Underwriting, reserves and exposure limits are not paperwork. They are the difference between a quarter and a bankruptcy.
Every sub-merchant also brings compliance responsibilities. Know-your-business checks, applicable screening, card network requirements, payment-data security and any required reporting depend on the account, the provider’s role and the governing rules.
Then there is the money itself. Where a facilitator receives pooled settlement, it has to split it across hundreds of merchants, net out fees, refunds, reserves and adjustments, fund each payout correctly and on time, and prove every cent of that math to the merchant, the bank, the auditor and, eventually, a regulator. Disputes arrive from issuers on their timelines, not yours, each with evidence requirements and deadlines. Multiply all of it by every day of the year.
Why so many get it wrong
The failure mode is predictable. A software company or marketplace sees the margin, licenses a PayFac-in-a-box, and treats the hard parts as a vendor's problem. Underwriting becomes a form. Risk becomes an automated score nobody on staff can explain. Reconciliation becomes a CSV someone opens at month-end. Compliance becomes a policy document written once.
It works until it doesn't. The first real fraud ring, the first merchant that grows ten times in a month, the first network audit, the first chargeback wave. At that point the facilitator does what it was never built to avoid: it freezes funds across the board, goes quiet, and lets the merchants absorb the cost of its own missing capability. Most of the merchant horror stories about frozen money and unreachable support are not stories about malice. They are stories about operators who took on a liability they did not have the organization to manage.
Doing it properly
Running a PayFac well means building the operating layer most entrants skip: a risk function staffed by people who read the merchant's file, not just the score. Reconciliation that ties every payout to its orders every day, not at month-end. Compliance that is monitored continuously, with evidence that can be handed to a bank or a network on request. Exposure limits that are set deliberately and communicated to the merchant before they matter. And a clear, honest line between what the facilitator controls and what the networks and issuers decide.
Etail Depot was built as that layer first and a payments company second. Our responsibility is to explain what we handle, what the account terms provide and who to contact when something needs attention.
Payment facilitation is not a feature you add. It is an operating responsibility you take on. The merchants who depend on it deserve a provider that understood that before taking their money.