Merchant onboarding is the end-to-end process of getting a merchant approved, configured, and processing live payments inside an ISV’s software platform. For integrated software vendors, the quality of that process directly affects merchant activation rates, payment revenue timelines, and long-term retention. Merchant onboarding tends to get pushed to the back of the list behind processing rates, integration timelines, and revenue share. But it is often where things go wrong. A slow approval process, a confusing setup, or a gap in support doesn’t just delay activation. It creates doubt. And doubt in the first week of a merchant relationship is hard to recover from.
Here’s a closer look at what merchant onboarding actually involves, why the experience matters more than most software vendors realize, and what to look for in a payment partner that gets it right.
What Does Merchant Onboarding Actually Involve for ISVs?
Merchant onboarding covers everything that happens between a merchant signing on to your platform and their first real transaction. It’s more involved than most people expect, and each step is a potential place for friction to build.
It starts with application and underwriting. The merchant submits their business details, including legal name, ownership structure, processing history, and business type, and the processor reviews it for risk and compliance.
This is where KYB and KYC requirements come in: the identity and business verification that every payment processor is legally required to complete before a merchant can go live. How fast this moves depends almost entirely on your payment partner’s underwriting setup.
Next is account provisioning. Once approved, the merchant account needs to be created, credentials configured, and the connection to your platform established. In a well-built integration, most of this happens automatically. In a clunky one, it turns into a back-and-forth chain between your team, the merchant, and the processor.
For merchants who need physical hardware, there’s also equipment provisioning: getting the right terminal or reader shipped, configured, and ready for their specific environment.
Finally, there’s training and go-live. Merchants need enough guidance to actually start processing with confidence. Depending on your platform and your payment partner, that might be self-serve documentation, hands-on support, or some combination.
Every one of those steps is a place where things can slow down or fall apart. And when they do, it’s not the processor who hears about it. It’s you.
Why Do Merchant Onboarding Problems Fall on the ISV?
When a merchant has a rough onboarding experience, they don’t typically point the finger at the processor in the background. They point it at the platform they signed up for. From their perspective, payments is a feature of your product. If activating that feature takes two weeks, requires submitting the same documents multiple times, or involves getting bounced between support contacts, that’s a product problem, regardless of where the actual bottleneck lives.
The downstream effects tend to snowball. 90% of companies lose potential customers during the digital onboarding process, and payments is no exception. Merchants who struggle through activation are slower to adopt the payments feature fully, less likely to grow their processing volume, and quicker to start looking at alternatives. In fact, bad onboarding accounts for nearly a quarter of all customer churn, making it one of the most preventable causes of lost revenue.
There’s also a hidden support cost. Every stuck application and every merchant who can’t get set up without help becomes a ticket for your team. Time that could go toward growth ends up going toward cleanup.
What Good Merchant Onboarding Looks Like for ISVs
The gap between a slow onboarding and a smooth one usually comes down to a few things done consistently well.
How fast should merchant underwriting take?
Merchants shouldn’t have to guess what’s happening with their application. A well-run underwriting process is upfront about requirements from the start, only asks for what it actually needs, and keeps applicants informed. A payment partner with ISV-specific underwriting should give you a clear, vertical-specific timeline upfront. If they cannot, that is a sign their process was not built around ISV programs. Processors who build their underwriting around the specific verticals their ISV partners serve tend to move faster, because they are evaluating the right risk signals for the right merchant types.
What does automated merchant account provisioning look like?
Strong integrations automate the provisioning process by creating the account, setting permissions, and connecting to your platform, so the merchant can get to their first transaction faster and with fewer chances for something to be misconfigured. Celero Fusion automates account provisioning for software vendors, giving merchants a cleaner path from approval to live processing. For ISVs looking to go deeper on how this works technically, a boarding API is one of the most effective ways to build that automation directly into your platform.
What is ISV-specific payment support?
Generic support doesn’t work well for ISV onboarding. The questions your merchants have are usually specific to how your software and payments connect. A support team that doesn’t understand your platform can’t answer those questions effectively. The right payment partner has support built around the ISV relationship, not a general merchant helpdesk that happens to take your merchants’ calls.
How does onboarding handle different merchant types?
Your merchants aren’t all the same. A high-volume multi-location business has different needs than a solo service provider. A good onboarding process handles that range without requiring your team to manage a different workflow for every merchant type. The payment partner should absorb that complexity, not pass it up the chain.
Questions Worth Asking Your Payment Partner
Onboarding quality is worth probing directly when you are evaluating payment partners. A few questions that will tell you a lot:
Q: What does your underwriting timeline typically look like for merchants in my vertical?
A payment partner built for ISV relationships should give you a specific number of business days, not a range. If they cannot answer by vertical, their underwriting is not built around ISV programs.
Q: How much of the provisioning process is automated versus manual?
The majority of provisioning should be automated. If the answer involves significant manual steps between your team, the merchant, and the processor, that complexity will land on your support queue.
Q: What does your support model look like specifically for ISV partners?
ISV-specific support means the team understands how your software and payments connect. A general merchant helpdesk that happens to take your merchants’ calls is not the same thing.
Q: What happens when an application gets flagged or delayed? Who handles it, and how fast?
There should be a named process and a clear owner. You want a partner who can tell you exactly what happens next and in what timeframe.
Q: Can you walk me through what the merchant-facing setup experience actually looks like?
Ask them to show you, not just describe it. A partner confident in their onboarding process will walk you through it step by step.
A payment partner that has built their onboarding around ISV relationships will have direct, specific answers to all of these. One that treats software vendors the same as any other merchant account won’t. If you want a broader view of what to evaluate in a payment partner beyond onboarding, our full payment processing partner checklist covers everything from technical fit to revenue structure.
How Does Merchant Onboarding Affect Long-Term ISV Growth?
How a merchant gets onboarded shapes how they feel about your platform for a long time. It’s one of the clearest signals of whether your payments integration was built with their experience in mind or just bolted on to check a box.
Merchants who get through onboarding quickly tend to start processing sooner, build confidence in the platform faster, and are less likely to churn before they ever hit their stride. They are also more likely to bring other businesses in their network onto your platform.Merchants who had a rough activation carry that forward, and it shows up in lower engagement, more support requests, and harder renewal conversations. 89% of consumers who have a poor experience with a brand turn to a competitor as a result.
Payments is consistently one of the top factors merchants weigh when choosing a software platform, which means the onboarding experience isn’t just an operational detail. It’s an early test of whether the platform lives up to what it promised.
Choosing a Payment Partner Built for ISV Merchant Onboarding
Merchant onboarding isn’t just an ops task. It’s the first real proof point your merchants have that your payments integration actually works. Slow approvals, manual setup, and generic support don’t just create delays. They create doubt, and doubt at activation is hard to undo.
Not every payment partner is built for ISV relationships. A partner whose onboarding process was designed for direct merchant acquisition will pass the complexity of ISV-specific setup back to your team, which is the problem you are trying to avoid.
Celero Fusion was built specifically for integrated software vendors, which means our onboarding process is designed around the complexity of the ISV relationship, not borrowed from a direct merchant model. We bring the underwriting expertise, provisioning infrastructure, and ISV-specific support to help your merchants get live faster and stay on your platform longer.
If you’re ready to see what that looks like, contact us today to learn more about Celero Fusion.