Picture an ISO owner with eighty merchants and a reputation that took twelve years to build. Last year a software platform started offering payments inside its product, and three of his restaurants moved over without so much as a phone call.
So he did what everyone told him to do. He hired developers. He built a merchant portal, then an onboarding flow, then a reporting dashboard. Eighteen months and a small fortune later, he owns software that does roughly what the big fintechs shipped years ago.
He didn't lose because he was lazy. He lost because he accepted the wrong question.
Why should an ISO have to become a software company to compete with a fintech?
Somewhere along the way, our industry decided the answer to fintech was to imitate fintech. Build the API. Ship the dashboard. Hire a CTO.
But a fintech is a software company that happens to move money. An ISO is a relationship business that happens to need software. Those are different animals, and pretending otherwise is how good sales organizations bleed out.
An ISO is a relationship business that happens to need software.
The giants have thousands of engineers and years of head start. You will not out-build them. You don't need to. Nobody asks a great restaurant to forge its own pans.
What an ISO needs is access: to modern onboarding, to many acquiring programs, to the tools merchants now expect, without carrying the cost of building and maintaining all of it alone. Your edge is the person who answers the phone. Spend your money there.
What would acquiring look like if changing processors didn't mean rebuilding your business?
Ask any ISO what it takes to move a portfolio and watch their face. New contracts. New boarding. Re-papered merchants. Integrations rewritten. Residuals in limbo.
That's not an accident. Lock-in is a business model. When leaving costs more than staying, your processor no longer has to compete for you. Pricing drifts. Support slips. Your leverage disappears, and nobody sends a memo announcing it.
Now imagine the opposite. One integration that reaches hundreds of acquiring programs. Merchants boarded once, placed wherever the economics and the risk profile fit best. Contracts written so that your portfolio is actually yours to move.
Portability has two halves, and you need both. A clean API means nothing if the paperwork chains your residuals to one shop. A fair contract means nothing if moving requires a six-month rebuild.
When switching is cheap, everyone has to earn the business every single day. That's what competition is supposed to look like.
Who really owns the merchant relationship in embedded payments?
Embedded payments changed the room. The software platform holds the daily login. The PayFac or processor holds the funds and the risk. The ISO often brought the deal, trained the staff, and still takes the angry call.
So who owns the merchant?
Read the contracts and you'll often find an answer nobody said out loud. Data rights. Portability clauses. Non-solicits. Residual terms. That's where ownership really gets decided, usually long before anyone thinks to fight over it. Too many ISOs and SaaS partners find out they were renting the relationship only when they try to leave.
Too many ISOs and SaaS partners find out they were renting the relationship only when they try to leave.
This is a fear both groups share, and it's why they should stop treating each other as threats. The SaaS platform wants payments revenue without becoming a bank. The ISO wants to keep the relationship it earned. Both lose if the merchant quietly becomes the property of whoever owns the rails.
The thread that ties it together
All three questions point the same direction. The infrastructure underneath acquiring should be shared and neutral, so the people on top can compete on what they do best.
ISOs sell and support. SaaS platforms build software merchants love. Acquirers and sponsor banks manage risk and capital. None of them should have to rebuild the plumbing to stay in business. None of them should be held hostage by whoever owns it.
That's the thinking behind NGnair's acquiring cloud. One integration. Hundreds of acquiring programs. Room for everyone in the chain to stay relevant without having to become somebody else.
Three questions before your next signature
Before you sign another processor agreement, approve another engineering hire, or let a software partner embed payments into your merchants' day, ask yourself three things.
Am I building something only I can build, or rebuilding something I could plug into?
If I had to move this portfolio tomorrow, what would it cost me?
Who does this contract say owns the merchant?
If you don't like the answers, you're not alone. And you don't have to accept them.
The tools exist to compete without turning yourself into a fintech. Use them while the choice is still yours.
See how NGnair approaches portable, shared infrastructure for ISOs.
