The case for embedded finance ISV distribution as a genuine growth channel for banks got a detailed airing in a recent PaymentsJournal podcast, with George Malesky, Director of Partnership Development at Qualpay, and Don Apgar, Director of Merchant Payments at Javelin Strategy & Research, making the argument that independent software vendors (ISVs) have become the most important distribution layer in financial services. Which leaves an obvious question: if software companies are the new branch network, what does that mean for the banks sitting behind them?
The Four-Legged Table: How the Embedded Finance Model Actually Works
The embedded finance model, as Malesky and Apgar describe it, rests on four participants: sponsor banks, Banking-as-a-Service (BaaS) providers, ISVs, and end customers. Pull any one of them out and the structure collapses.
Sponsor banks supply the regulated foundation, deposit-holding, account issuance, access to payment networks, and the compliance obligations that come with all of it: anti-money laundering (AML), Know Your Customer (KYC), and financial risk management. BaaS providers build the technology layer on top, delivering APIs for digital onboarding, payment orchestration, underwriting automation, and settlement. ISVs take those capabilities and put them directly in front of businesses, while also holding the customer relationship and the data that flows from it.
‘Banks don’t naturally have these workflows,’ Malesky said. ‘An accounting software knows exactly when a business sends invoices; a healthcare platform knows when patients are going to make payments; a property management platform knows when rent’s going to be collected. They have a more intimate knowledge, and that context allows financial services to appear exactly when and where they are needed.’
The end customer validates the whole system. Without adoption, there is no revenue and no reason for any of the other three participants to stay at the table. ‘You can think of it as a four-legged table,’ Malesky said. ‘Take out one leg and make it wobbly. There’s no independence here, each one of those legs makes it all come together and makes it work.’
Embedded Finance ISV Distribution: Why ISVs Hold the Strongest Position
ISVs sit closest to the end customer, and that proximity translates into concrete advantages. The most direct is revenue diversification: rather than relying on subscription fees alone, ISVs can participate in payment processing income and layer in treasury services, lending, referrals, and deposit programmes.
The stickiness argument may be more powerful still. Apgar described the dynamic plainly: ‘Once that software is wrapped into the business, it’s very hard for a business owner to change software platforms. They basically have to start over, not just with their menu if they’re a restaurant, but with all of their suppliers, recipes and inventory levels. Unless the software is flat-out not working, there’s very little incentive.’ For banks riding along inside that software, the implication is straightforward. ‘You’ve acquired not just a customer, but a very sticky and stable customer,’ Apgar said.
Malesky framed the user-experience shift in similarly practical terms. A restaurant owner who once had to physically leave the premises to visit a bank between shifts can now handle supplier payments through the same platform they use to run the business. ‘Banking simply happens in the background of everything else they do,’ he said. ‘The software becomes a more complete and holistic operating system for the business, and it’s a workflow instead of a destination.’
What Banks Need to Provide, and Why Compliance Is the Heaviest Lift
For banks, the opportunity has moved upstream from individual financial products toward the infrastructure that embeds those products in software. Malesky described the ideal offering as ‘an acquirer-in-a-box, giving an ISV, PayFac, or fintech everything they need to launch financial services quickly, without building that additional infrastructure themselves.’ That means API-first architecture, digital onboarding with KYB and KYC built in, white-label capabilities so the bank’s branding stays invisible to the end user, and merchant portfolio management tools extended to ISV partners.
Compliance, Malesky said, is consistently underestimated by those coming in from outside banking. ‘AML, OFAC, KYB, transaction monitoring, risk scoring, the list goes on and on. It is an expansive requirement, for good reason, that outside of banks becomes a difficult and expensive challenge.’ Handling that burden is, in practice, a large part of what banks bring to the partnership.
The commercial structure matters too. Clear revenue-sharing arrangements give both banks and ISVs a shared incentive to deepen the relationship over time, while the transaction data generated through the partnership can sharpen underwriting and working-capital decisions in ways that a traditional lending relationship rarely allows.
A Real-World Signal: Synovus and the Maast Platform
The model is already moving from theory to practice. According to Qualpay, Synovus has chosen to leverage Qualpay’s payments technology as an integral part of Maast, the bank’s new money-as-a-service offering planned to launch later this year. Maast will combine embedded payments and embedded banking on one platform, accessed through a common integration layer, which is a reasonably concrete illustration of what the ‘acquirer-in-a-box’ concept looks like when a regional bank commits to it. Qualpay’s CEO Craig Gass is named in connection with the partnership.
For community and regional banks watching from the sidelines, the Synovus move sets a reference point. Malesky put the capability in straightforward terms: ‘With the right platform, banks can onboard partners in weeks instead of years, and automate all the things that we process to make the experience so seamless for their customers. The technology becomes a multiplier. Embedded finance-era technology isn’t just an enabler of growth, it is the distribution strategy.’
