There’s a phrase in payments that sounds almost poetic if you don’t know what it means, and faintly alarming once you do: the merchant of record.

It’s the entity that, legally and financially, is on the hook for a transaction. The name on the customer’s bank statement. The party responsible if a chargeback comes in, if a refund is owed, if a regulator asks who actually sold this product to this customer. In a normal transaction, that question has an obvious answer. You bought a book from a bookstore; the bookstore is the merchant of record. Simple.

Here’s the concept this piece is actually about, and the reason it matters: in a growing share of high-risk payment relationships, that question doesn’t have an obvious answer anymore. And the moment it stops having an obvious answer is the moment a payment facilitator either does its job properly — or quietly stops being one at all, and becomes something card networks have very specific, very unforgiving rules against.

What a Payment Facilitator Actually Is

A payment facilitator — PayFac, in industry shorthand — is a business that sits between an acquiring bank and a group of smaller sub-merchants, handling onboarding, payment collection, and risk management on their behalf so those sub-merchants never need their own individual, bank-negotiated merchant account. This is, genuinely, one of the most useful inventions in modern payments. It’s why a small Etsy seller doesn’t need to negotiate their own contract with an acquiring bank. It’s why a marketplace can onboard ten thousand vendors without ten thousand separate underwriting conversations.

But that convenience comes with a formal, non-optional obligation. Visa and Mastercard both require any business acting as a payment facilitator to be registered as one — a distinct process from simply getting a merchant account for your own business. Registration means the facilitator takes on real, auditable responsibility: verifying the identity of every sub-merchant it onboards, monitoring their transaction patterns individually, maintaining the ability to identify precisely which sub-merchant generated which transaction, and reporting that structure transparently to its own acquiring bank.

In other words: if you’re going to stand between other businesses and the card networks, the card networks require you to actually know who those businesses are. That’s the whole deal. That’s the thing that makes payment facilitation legitimate instead of just a layer of fog.

The Five-Message Version of How It Breaks

Now here’s how that entire framework can quietly evaporate, in real conversations, without anyone using the words “payment facilitator” even once.

It starts with a description, offered plainly, early in a conversation between a prospective merchant and a processor: we want to connect institutions with each other. We’ll develop merchants who interface with our API, and those merchants won’t directly contact you.

That sentence, translated, says: I intend to be a payment facilitator. Nobody in the conversation calls it that. It’s just described as a “co-op model.”

The response that matters most doesn’t come as a rejection or a redirect toward proper PayFac registration. It comes as a logistics answer: since you’re an aggregation platform, your merchants will not connect directly with us — they’ll be routed through your API, and you’ll manage the transaction flow on your end. We’ll provide the main gateway/API access, which you can distribute to your sub-merchants.

Read closely, that’s an acceptance of the aggregation model — without any accompanying registration process, sub-merchant KYC framework, or individualized risk monitoring structure being put in place. The processor isn’t unaware that sub-merchants exist. It’s actively agreeing to a structure where those sub-merchants will remain permanently invisible to it.

Then the follow-up question, a few messages later, seals it: if I have other product categories, do I need to report them separately, or can I use the same MID?

You can use the same MID. Just inform us and get approval once before adding new categories.

One merchant ID. Multiple unrelated product categories. An unknown, unbounded number of sub-merchants behind an API the processor will never see into directly. This is not payment facilitation done properly. This is the shortcut version — all of the convenience, none of the actual registered accountability — and it happened in the space of about ten chat messages, with nobody involved using a single word that would flag it as unusual.

Why “Just Tell Us Later” Isn’t a Compliance Framework

The phrase that does the most damage in this kind of conversation is almost always some version of “just let us know before you add anything new.” It sounds responsible. It sounds like a check is being performed. It is, functionally, closer to an honor system than a control.

Proper sub-merchant onboarding under a registered PayFac structure requires the facilitator to independently verify each sub-merchant’s identity, business model, and risk profile before that sub-merchant starts processing — not to wait for a heads-up message after the fact, from the aggregator itself, whose financial incentive is volume, not disclosure. Asking the aggregator to self-report new categories “before processing” puts the entire compliance function in the hands of the party with the least incentive to slow down and flag anything.

This is why the distinction between “you can use the same MID, just tell us first” and actual PayFac registration isn’t pedantic. It’s the entire difference between a system built to catch problems and a system built on the hope that nobody brings one to you.

What the Card Networks Actually Require

For context on how seriously this is treated at the network level: Visa’s and Mastercard’s payment facilitator programs require registered facilitators to maintain detailed sub-merchant records, conduct due diligence proportional to each sub-merchant’s risk level, monitor transaction activity at the sub-merchant level (not just in aggregate), and be able to produce that sub-merchant-level detail on demand during an audit or dispute investigation. Facilitators that fail to do this — or that never registered as facilitators in the first place while functionally operating as one — can face termination of their own processing relationship, financial penalties, and in serious cases, placement on industry blacklists that make it extremely difficult to obtain payment processing anywhere else afterward.

None of that risk sits with the sub-merchants hiding behind the aggregator’s API. All of it sits with the aggregator, and by extension, with the processor that agreed to look the other way on “same MID, just tell us later.”

Why This Keeps Happening Anyway

If the rules are this clear and the consequences this severe, why does this pattern keep showing up in real onboarding conversations? A few honest reasons, none of them exotic:

Speed is a competitive advantage, and registration is slow. Formal PayFac registration with a card network is a real process — documentation, technical requirements, ongoing compliance obligations. A processor that skips it and just extends an existing merchant account to cover aggregation activity can say yes to a prospect in days instead of months. In a market where prospects are actively shopping between providers, that speed is worth real money.

The language never has to be explicit. Nobody has to say “we’re going to operate as an unregistered payment facilitator” for this to happen. It happens entirely through euphemism — “co-op model,” “connecting institutions,” “same MID, just tell us.” The absence of the technical term makes it easier for everyone involved to avoid confronting what’s actually being agreed to.

The risk is deferred, not eliminated. In the moment, nothing bad happens. The account gets approved, the integration works, transactions flow. The consequences — an audit, a dispute investigation that can’t identify which sub-merchant actually generated a transaction, a card network discovering an unregistered facilitator relationship — arrive later, sometimes much later, disconnected enough from the original onboarding conversation that nobody thinks to trace it back.

What Legitimate Payment Facilitation Actually Looks Like

It’s worth being clear that none of this is an argument against aggregation models generally. Marketplaces, platforms, and aggregators are a completely normal, valuable part of how modern commerce works, and plenty of them do this correctly. The difference between doing it correctly and doing it the way described above isn’t subtle once you know what to look for:

  • Formal registration with the relevant card networks as a payment facilitator, not an informal extension of a standard merchant account.
  • Per-sub-merchant KYC, completed before that sub-merchant processes a single transaction, not disclosed after the fact.
  • Individual risk monitoring at the sub-merchant level, so a spike in one sub-merchant’s chargeback rate is visible independently, not buried in an aggregate number covering ten unrelated businesses.
  • Distinct identification of which sub-merchant generated which transaction, available on demand, not reconstructed after an audit request forces the question.

If a processor offers you an aggregation arrangement and none of these four things come up unprompted, that absence is the actual signal — not proof of wrongdoing, but proof that the shortcut version is being offered instead of the real one.

The One-Sentence Test

If you’re ever on either side of a conversation like this — building an aggregator, or evaluating one as a processor — there’s a single question that cuts through the euphemisms faster than anything else: who verifies the identity of the business at the very bottom of this chain, and when?

If the honest answer is “nobody, until something goes wrong” — that’s not a payment facilitation model. That’s a blind spot with an API in front of it, and blind spots in payments don’t stay small. They just stay invisible, right up until an audit, a dispute, or a regulator finds the one thread that unravels all of it at once.

This piece is an explanatory feature drawing on patterns observed in a real, anonymized onboarding conversation, used here for illustrative purposes only. No company is named or identified. It is offered as educational content on payment facilitation compliance and is not legal or regulatory advice — businesses considering an aggregation or sub-merchant model should consult a payments attorney and review the specific card network registration requirements that apply to them.