Library · MIDs · Guide
ISV → PayFac — claim map
GuideISV → PayFac — claim mapBack to article
Registering as a PayFac means boarding sub-merchants under a sponsor bank. Filter the claim. Not leave-PayFac.
| Claim | Reality | Get in writing | Do not |
|---|---|---|---|
| Using a PayFac API means we are a PayFac | No. That is someone else’s registration. You are still a platform customer or connector | Whether you are listed as a registered facilitator under a sponsor bank | Market yourself as a PayFac without registration |
| Becoming a PayFac is the same as leaving one as a seller | No. Leaving is a sub-merchant exit. Registering is becoming the platform | N/A — different job | Use the leave-PayFac calculator for an ISV registration decision |
| We can skip sub-merchant KYC if the software collects cards | No. Facilitator obligations include boarding KYC at the bank’s bar | This sponsor bank’s KYC / underwriting requirements | Thin KYC to grow volume faster |
| The ISV becomes the acquiring bank | No. The sponsor bank holds the network seat. You sit under them | Sponsor bank legal name and registration status | Promise merchants you are the member bank |
| Any volume justifies registration | No. Capital, risk ops, and bank bars decide — not a slogan | Written capital / reserve / portfolio requirements from the bank | Invent a typical volume trigger |
| This is another PayFac-vs-ISO table | No. That shape is on Payments. This map is the ISV registration fork | N/A | Rewrite PayFac-vs-ISO 101 here |
Filter the claim. Becoming a PayFac is registration under a sponsor bank with sub-merchant KYC. Using someone else’s PayFac API is not that.
Pairing procedure: When an ISV should register as a PayFac. Topic: MIDs.
Work with us — We run this job on your accounts. Services