By Clayton Smith | Head of Operations at Payabli
I’ll be upfront. I didn’t come up through the payments industry. My background is operations and strategic leadership – the discipline of taking something that works inconsistently and making it work every time, at scale.
When I joined Payabli nearly four years ago, the company was a small group of scrappy entrepreneurs and a few early adopter partners that believed in the future of embedded payments. Today we’re moving hundreds of billions of dollars across over 100 vertical software platforms serving industries from property management to field services to legal.
I’ve had a front-row seat to what separates embedded payments programs that scale from ones that stall. It almost always comes down to four things:
- How you implement
- How you onboard
- How you scale
- What you do after go-live
Here’s what I’ve learned about each.
Integration: Implementing for the Long Haul
The first place a payments partnership is won or lost isn’t at the signing table. It’s in the integration.
Every week a partner spends in an integration cycle is a week their merchants are still on a legacy processor, not processing on your platform, and not generating revenue for anyone. Delayed launches don’t just push timelines. They erode confidence. Merchants who expected to go live in October and are still waiting in December start questioning whether they made the right call. Some of them churn before they ever process a single transaction.
The root cause is almost never a bad API. It’s an incomplete product:
- Documentation that doesn’t match live behavior
- Sandbox environments that don’t reflect production edge cases
- A support model that treats integration questions like tickets in a queue instead of blockers with real business impact
At Payabli, our solutions engineering function exists to close that gap before it opens. We scope integrations before a line of code is written, and we ask harder questions upfront:
- What does your merchant population look like at scale?
- What billing models do you need to support?
- What does your support team need to handle merchant issues without escalating to us?
Those answers define the integration. Skip them, and you ship something that works in a sandbox and breaks in production. Speed without completeness isn’t a win – it’s a delayed problem. At Payabli, we don’t trade one for the other.
Merchant Onboarding: From Application to Activation
Once the integration is live, the clock starts again – this time on every merchant waiting to go live.
Merchant onboarding is not just a compliance function. It’s a revenue acceleration function. Every merchant sitting in a pending queue is lost volume. Every onboarding flow that requires manual and time-consuming steps to complete is a merchant who might not finish. Configuration matters here just as much as speed: the right MCC codes, the right processing limits, the right fee structure tied to the partner’s program – these aren’t back-office details, they’re the foundation of a strong merchant relationship.
Underwriting plays a central role that often gets undersold. The goal isn’t just to approve merchants – it’s to approve the right merchants quickly and catch the wrong ones cleanly. A well-structured underwriting policy can clear the majority of merchants automatically, based on defined risk thresholds and data signals, without human intervention. That’s not cutting corners. That’s building a system that scales without adding headcount every time a partner adds merchants.
The outcome of a well-run onboarding process is a merchant who is approved, configured, and activated – processing their first transaction within days of applying, not weeks. Activation rate is the metric we obsess over because it’s often the first signal of whether a payments program is actually working.
Scaling Merchant Migrations: The Bulk Boarding Advantage
Bulk boarding is what happens when a platform has a mature merchant base and needs to move fast. It’s not a variation of standard onboarding – it’s a different operational model entirely, and one of the most powerful capabilities in embedded payments when it runs right.
It’s built for platforms migrating off legacy processors, launching payments to an existing customer base, or absorbing merchants from an acquisition. The merchant list already exists. The business relationship is established. What’s needed is a fast, clean path from data submission to live processing – at volume.
The difference between bulk boarding done well and done poorly is almost entirely operational.
Done poorly: a partner submits a merchant file, gets a spreadsheet back days later with 40% flagged for manual review and no explanation, and starts fielding support calls they can’t answer.
Done well: a clean intake template, automated validation, an intelligent underwriting layer that approves the majority instantly, and real-time visibility into every merchant’s status.
For Payabli, bulk boarding is a genuine competitive differentiator. It’s what lets a partner with 2,000 merchants convert their entire base in weeks instead of quarters. Whether it’s 30 new customers or 30,000+ migrating at once – I’ve seen it, and we’ve executed.
Post-Live Enablement: The Metrics That Matter
Most implementation conversations end at go-live. Ours don’t.
Getting merchants live is the prerequisite. The actual value of an embedded payments program is built in the months after launch – and it’s measurable:
- Activation rate tells you if merchants are crossing the threshold from approved to processing.
- Ninety-day volume tells you if they’re ramping or stalling.
- Feature adoption – ACH, recurring billing, payouts – tells you how deeply payments are embedded in the merchant’s workflow.
Merchants who use two or more payment rails have materially higher retention than those who only accept card. That’s not an accident – it’s a function of how integrated payments become in their day-to-day operations. Chargeback rate and dispute patterns are merchant experience signals, not just risk metrics. When dispute rates spike for a cohort, there’s usually friction in the payment flow that nobody’s reported yet. Finding that early keeps merchants on the platform – and keeps partners from getting uncomfortable calls.
At Payabli, we help our partners track all of this – not as a reporting exercise, but because these metrics are the early warning system for churn and the playbook for growth. Vertical SaaS platforms who know their activation rate, 90-day volume, and product adoption curve can have confident conversations with their own leadership. Platforms who don’t are flying blind.
The Takeaway
Implementation is the moment of truth in any payments partnership. The platforms that win in embedded payments are the ones that treat implementation as a competitive advantage, not a line item.
If you’re reading this and thinking “I wish our current payments provider talked like this” – let’s have a conversation. That’s exactly where we should start.