Ask a payment business how growth is going, and you'll usually hear about leads, signed contracts, and pipeline. Fewer teams can tell you how long it takes a signed merchant to push its first live transaction, or how much of its volume actually shows up after that. Those two numbers say far more about next quarter's revenue.Both are decided during merchant onboarding. KYB verification, merchant underwriting, the contract, the merchant ID (MID) from the acquirer, and the technical integration all have to happen before a single payment goes through. At most payment service providers (PSPs) and independent sales organizations (ISOs), they happen one after another. Different teams handle each step, and none of them sees the whole picture.A merchant stuck in that queue almost never sends a cancellation email. It keeps processing with the providers it already has. By the time you go live, your share of its volume is smaller than the one you pitched for.Why onboarding speed decides how much volume you getVery few merchants rely on one provider now. In our 2025 Payment maturity research, which covered 672 merchants, 2 out of 3 (66.5%) worked with more than one. Businesses with a global presence often have many more: 24.5% of them use 10 or more providers. Among merchants processing over 500000 transactions a month, it's 43.5%. In high-risk verticals, 3 in 4 have moved past a single provider, and 28% run 10 or more.So when you sign one of these merchants, you usually join a line-up. The merchant sends you a slice of traffic, watches your approval rates and uptime, and adjusts. You can't win that comparison while you're still collecting documents. Meanwhile, the incumbent keeps earning on the traffic you came for.Merchants also have a clear sense of how long adding a provider should take. In the same study, 43.9% of businesses said they can connect a new provider or payment method almost instantly or within a few days. Only 27% said it takes them months. If a merchant's own team can plug in a provider in a week, a five-week onboarding on your side is hard to explain.Why the merchant onboarding process drags onMost delays come from running every step in sequence. A typical merchant onboarding process looks like this:ApplicationKYC for payments on the owners and directorsKYB verification on the companyUnderwritingContractMID request to the acquirerCredentialsIntegration and testingGo-liveEach step waits for the one before it.That order makes sense. You don't hand live credentials to a company you haven't verified, and acquirers won't issue a MID before underwriting. The trouble is that the same logic gets applied to work that has nothing to do with risk, like building an integration against a sandbox.When we look at stalled onboardings, the same few things keep showing up.Document back-and-forth. The merchant sends what was asked, compliance finds something missing, another email goes out, and each round adds two or three days. The checks may be completely justified. But from the merchant's side, it looks like you don't know what you need.Underwriting with half the picture. The risk team gets a folder of documents but not the things that matter for the decision: processing history, target markets, average ticket size. So they either play it safe and decline, or send another list of questions.Waiting on the acquirer. A merchant can be approved internally and still wait weeks for a MID. Or it gets turned down because the acquirer doesn't want that vertical or country. The merchant is approved but still can't take a single payment.Integration starts last. Development begins only after the contract is signed. So two weeks of it get added on top of three weeks of review instead of running at the same time.No overall owner. Sales hands over to compliance, compliance to operations, operations to tech support. Each team does its part on time, and the merchant still waits six weeks because no one is responsible for the date of the first live transaction.How to speed up onboarding without loosening the checksEvery check below stays in place. What changes is the timing, and how your team splits its effort. For the basics, such as which documents to collect and who does what at each stage, see our step-by-step guide to the merchant onboarding process.Sort merchants by risk before asking for documentsBefore requesting anything, run a short pre-screen. Look at the merchant category code (MCC), target countries, expected volume, business model, and the website. That's usually enough to put the merchant into a rough tier: standard, enhanced or high-risk.The tier tells you which documents to ask for, how deep the review goes, and which acquirers are likely to say yes. An online clothing shop selling in the EU and an iGaming operator entering Brazil shouldn't get the same checklist. Send the full list for that tier in one go, on day one, and most of the back-and-forth disappears.Give sandbox access on day one and verify in parallelSandbox credentials don't move money, so there's no reason to hold them back. Let the merchant's developers start building straight away.While they do, compliance runs KYB verification:Company registry checksTracing ultimate beneficial owners (UBOs) down to actual peopleSanctions and politically exposed person (PEP) screeningKYC on directors and principals happens at the same time.For standard-tier merchants, most of this can be automated, which leaves manual review for the cases that need it. If it works as intended, the integration is already tested by the time compliance signs off. Going live then comes down to switching credentials.Use underwriting to set conditionsA strict yes-or-no approach hurts young businesses most. A company registered six months ago may have experienced owners and a perfectly clear model, but no processing history. So it gets declined or left in limbo.Merchant underwriting has more options than that. The merchant can go live with a rolling reserve, a processing limit, delayed settlement, or a volume cap that rises after a few clean months. The merchant starts earning, and you keep the risk under control. After 60–90 days, you have real transaction data to base the next decision on.Check early which acquirers will take the merchantAt the pre-screen stage, find out which of your acquiring and alternative payment method (APM) connections accept this MCC, these countries, and this volume.If only one acquirer fits and it's known to be slow, tell the merchant the real timeline upfront. That's a much easier conversation in week one than in week five. And if you have several acquirers connected, a declined MID request means trying the next one rather than starting from scratch.Track onboarding the way you track salesIf onboarding decides revenue, it needs its own numbers and one person responsible for them. We'd start with these:The share of applications that get completedTime to decision for each risk tierHow often documents have to be re-requestedTime to first live transactionThe share of approved merchants processing within 30 daysVolume at day 90The last two tend to be uncomfortable because they show how many approved merchants never turned into revenue.What this means for your platformAll of this is hard to do if your platform treats every merchant the same way:Tiering means setting payment methods, routing, fees, limits, and reserves for each merchant separately.Parallel integration needs a sandbox that behaves like production.Quick acquirer matching needs several providers already connected, rather than a new integration for each vertical.That's the problem we set out to solve with Corefy's white-label payment gateway. Payment businesses launch under their own brand with 650+ providers already integrated. Connecting a merchant to the right acquirer or APM is usually a settings change.With our merchant management system, teams configure methods, routing, fees, limits and rolling reserves for each merchant, without touching the rest of the portfolio. That's what makes conditional approvals workable day-to-day.Key takeawaysIn a multi-provider market, merchant onboarding decides your share of a merchant's volume, not only whether you sign it.Most delays come from sequential design: gates that block low-risk work such as sandbox integration.Tier merchants before collecting documents, run KYB verification alongside integration, and match acquirers early.Use merchant underwriting to set terms such as reserves, limits, and graduated caps, rather than issuing a flat yes or no.Measure time to first transaction and 90-day volume ramp, and give one person ownership of both.Some payment businesses treat onboarding as a revenue process with risk built in, rather than a risk process that occasionally produces revenue. Their merchants go live first. In a market where merchants route volume by performance, going live first is how you earn the chance to keep it. Yes#paymentsAlexandra Potapska Head of Customer SuccessCorefy23 Sep, 2026