Skip to article
ecomservices.io
MIDs · How to run this
ApplicationsIdentityHealthCalculatorCapsNot on this page yetApprovalsCalculatorDescriptorsCalculatorEnrollmentNot on this page yetAllocationCalculatorProcessor ops

Library · MIDs · How to run this

When an ISV should register as a PayFac

How to run thisMIDs4 steps
GuideISV → PayFac — claim map · Calculator lives in the articleOpen

An ISV that embeds payments can stay on someone else’s PayFac, become a PayFac themselves, or push merchants to ISO/direct accounts. Registering as a PayFac means you board sub-merchants under a sponsor bank, run KYC, and take facilitator obligations. That is not when a seller leaves a PayFac. It is not another PayFac-versus-ISO table.

Pair: ISV → PayFac — claim map on MIDs.

Why ISVs register

Control of boarding and pricing for their software’s merchants.

Economics when facilitator markup beats referring everything out — only if you can fund underwriting, risk, and ops.

Product when the payment flow must live inside the ISV, not a redirect to a third-party checkout they do not control.

What you take on

Sponsor bank relationship and registration. You are not the network member; the bank is.

Sub-merchant KYC / underwriting at volume. Thin KYC is how platforms get shut down.

Capital, reserves, and loss liability the bank and networks require. We do not invent a dollar bar — get the bank’s written requirements.

MATCH and program risk for the portfolio you board. Seller MATCH letters still go to the bank; you sit in the middle.

What not to do

Do not call yourself a PayFac without registration. Do not treat “we use a PayFac API” as being one. Do not use this page as a seller graduation slogan to a direct MID.

Related: MIDs, sponsor bank, leave PayFac, Payments.

Procedure

  1. Name whether you will board sub-merchants under your own registration.
  2. Get sponsor bank requirements in writing.
  3. Cost the KYC and risk ops — not only the markup.
  4. Do not market as a PayFac until registered.

Failure modes

  • Calling an API integration a PayFac registration.
  • Skipping sub-merchant KYC.
  • Confusing seller leave-PayFac with ISV registration.
  • Inventing a volume trigger for registration.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

PayFac registration
ISV or platform registered under a sponsor bank to board sub-merchants. Using a PayFac API is not registration.

Work with us — We run this job on your accounts. Services

FAQ

Can an ISV become a registered PayFac?
Yes, by registering with a sponsor bank and meeting network / bank requirements. This page is the decision fork — not an application kit.
Is registering as a PayFac the same as leaving a PayFac as a seller?
No. [Leaving](/manuals/leave-payfac) is a sub-merchant exiting a platform. This page is an ISV becoming the platform.
Do I need another PayFac-vs-ISO explainer?
No. That shape is on [Payments](/payments). This page is why an ISV would take the registration path.