The embedded finance market has reached a strategic inflection point for mid-market SaaS firms. Companies with annual recurring revenue between £10m and £100m are increasingly expected to offer payment acceptance, account issuance or lending products directly within their platforms. The question is no longer whether to embed financial services, but how.
The two dominant paths are Banking-as-a-Service (BaaS) APIs, which provide modular access to regulated banking infrastructure, and licensed partnerships, where a SaaS firm works with a chartered bank or lender under a formal programme management agreement. Each approach carries distinct implications for speed to market, regulatory exposure, revenue share and long-term strategic control.
This article examines the trade-offs, the commercial calculus and the emerging consensus among operators who have already made the choice.
The Strategic Context
Embedded finance is not a new phenomenon. Stripe and Shopify normalised embedded payments for e-commerce years ago. What has changed is the breadth of products now being embedded. Lending, deposit accounts, card issuance and insurance are all being integrated into vertical SaaS platforms serving industries from property management to healthcare.
For mid-market SaaS firms, the pressure comes from two directions. Customers increasingly expect a unified experience where financial transactions are handled inside the software they already use. At the same time, investors are rewarding platforms that increase revenue per user by adding financial services margins to existing subscription fees.
A 2023 report from Bain & Company estimated that embedded finance revenues in the US alone could exceed $7tn in transaction value by 2030. While that figure is widely cited, the path to capturing that value is uneven. Mid-market firms lack the balance sheets and legal teams of enterprise players, but they have more flexibility than early-stage startups.
The BaaS API Route: Speed and Modularity
Banking-as-a-Service providers such as Synapse, Unit, Treasury Prime and Railsbank (now part of the Railsr group) offer APIs that allow SaaS companies to issue virtual cards, open accounts and originate loans without applying for a banking licence. The model is attractive because it promises rapid integration and variable cost structures.
A typical BaaS arrangement involves the SaaS firm paying per-account or per-transaction fees, plus a share of interchange or interest income. The provider handles the underlying banking licence, compliance monitoring and regulatory reporting. The SaaS firm retains the customer relationship and controls the user interface.
For a mid-market SaaS company with 50,000 active users, launching a basic payments feature via BaaS can take as little as three to six months. The upfront engineering cost is modest relative to building a proprietary financial stack. The variable pricing model aligns with usage, so the SaaS firm does not carry fixed infrastructure costs.
However, the BaaS model carries significant dependency risk. The provider is a single point of failure for compliance, uptime and regulatory relationships. If the provider loses its banking partner or faces regulatory action, the SaaS firm's financial products can be disrupted with little notice. The collapse of Synapse in 2024, which left several fintech partners unable to access customer funds, is a cautionary example.
The Licensed Partnership Route: Control and Credibility
The alternative is to form a direct partnership with a regulated bank or lender, often through a programme management agreement. In this model, the SaaS firm does not need its own banking licence, but it enters a formal contractual relationship with a chartered institution that oversees compliance, capital adequacy and risk management.
Examples include partnerships between mid-market SaaS platforms and banks such as Cross River, WebBank or Celtic Bank in the US, or ClearBank and Starling in the UK. These arrangements typically involve revenue sharing, with the bank taking a percentage of net interest income or interchange fees in exchange for regulatory infrastructure and balance sheet capacity.
The licensed partnership route takes longer to negotiate. Legal and compliance due diligence can take six to twelve months. The SaaS firm must demonstrate adequate compliance controls, data security and financial stability. The upfront legal costs are higher, often running into six figures for contract negotiation and regulatory filings.
Once operational, however, the partnership offers greater strategic control. The SaaS firm can customise product terms, pricing and risk parameters more deeply than with a standardised BaaS API. The bank's regulatory credibility also provides a stronger foundation for scaling into new products or geographies.
Commercial Impact: Unit Economics Compared
The commercial calculus differs materially between the two models. Under a BaaS arrangement, the SaaS firm typically earns a smaller per-transaction margin because the provider takes a cut for compliance and infrastructure. For a payments product, the SaaS firm might retain 60-70% of the interchange fee after the BaaS provider's fee and card scheme costs.
Under a licensed partnership, the SaaS firm can negotiate a higher share of the economics, sometimes retaining 80-90% of the net interest margin on loans or 70-80% of interchange on card transactions. The trade-off is the higher fixed cost of compliance and the longer time to revenue.
For a SaaS firm with £50m in ARR and a user base of 100,000, the difference in annual revenue from an embedded lending product could be material. Assuming an average loan balance of £2,000 per user and a net interest margin of 5%, the total addressable interest income is £10m per year. Under a BaaS model retaining 60%, the SaaS firm earns £6m. Under a licensed partnership retaining 85%, the figure rises to £8.5m. The £2.5m difference more than offsets the higher upfront legal and compliance costs within the first year.
However, these figures are illustrative. Actual margins depend on product type, user behaviour, regulatory jurisdiction and the specific terms negotiated. The key point is that the licensed partnership route offers superior unit economics for products with high transaction volumes or large loan books, while the BaaS route is more attractive for lower-volume or experimental products.
Why It Matters
The choice between BaaS APIs and licensed partnerships is not merely a procurement decision. It shapes the SaaS firm's product roadmap, risk profile and valuation. Investors in SaaS companies increasingly scrutinise the depth of financial services integration. A platform that owns the full financial relationship with its users, rather than relying on a thin API layer, commands higher revenue multiples.
Public market comparables support this view. Shopify, which has built deep financial services capabilities through partnerships with Affirm and Stripe, trades at a higher revenue multiple than pure subscription platforms. While Shopify is an enterprise-scale example, the principle applies to mid-market firms seeking to increase their enterprise value.
Regulatory trends also favour the licensed partnership model. Regulators in the UK, EU and US are tightening oversight of BaaS providers, particularly around consumer protection and anti-money laundering. The Financial Conduct Authority in the UK has signalled increased scrutiny of firms that outsource compliance to third parties without adequate oversight. SaaS firms that choose the BaaS route must ensure their provider's compliance posture meets regulatory standards, or risk being held jointly liable.
Risks and Unknowns
Both models carry risks that are often underestimated. The BaaS model exposes the SaaS firm to concentration risk. If the provider's banking partner changes terms or exits the relationship, the SaaS firm may need to migrate its entire financial product to a new provider, a process that can take months and disrupt customer trust.
The licensed partnership model, while more stable, introduces operational complexity. The SaaS firm must build internal compliance capabilities, including a dedicated team for financial crime monitoring, regulatory reporting and audit management. For a firm with no prior financial services experience, this can be a significant distraction from its core software business.
There is also the risk of adverse selection in lending products. SaaS firms that embed lending without sophisticated credit underwriting may attract higher-risk borrowers, leading to loan losses that erode margins. Both BaaS providers and bank partners typically require the SaaS firm to retain some credit risk, either through a first-loss tranche or a reserve fund.
Regulatory uncertainty remains a factor. The UK's Future Regulatory Framework review and the EU's Payment Services Directive (PSD3) could introduce new requirements for embedded finance providers. In the US, the Consumer Financial Protection Bureau has signalled interest in regulating digital wallets and payment apps more strictly. SaaS firms must build flexibility into their chosen model to adapt to changing rules.
FY Outlook
The mid-market embedded finance market is likely to consolidate around a hybrid model. SaaS firms will use BaaS APIs for low-risk, high-volume products such as virtual cards or instant payments, while reserving licensed partnerships for higher-margin products such as lending and deposit accounts.
We expect to see more SaaS firms acquiring or building in-house compliance capabilities, even if they continue to rely on external partners for balance sheet capacity. The cost of compliance is falling as regulatory technology improves, making it feasible for mid-market firms to internalise functions that were previously outsourced.
Over the next 18 to 24 months, the most successful mid-market SaaS firms will be those that treat embedded finance as a core product capability, not a feature. That means investing in dedicated financial services teams, negotiating partnership terms that align with long-term margin targets, and building the operational infrastructure to manage regulatory risk.
Conclusion
The embedded finance decision point is a defining strategic choice for mid-market SaaS firms. BaaS APIs offer speed and low upfront cost but carry dependency and margin risk. Licensed partnerships offer better economics and control but require greater investment and patience.
There is no universal right answer. The optimal path depends on the SaaS firm's product complexity, user base size, regulatory appetite and long-term valuation goals. What is clear is that the window for making this choice is narrowing. As regulators tighten oversight and customers raise their expectations, the cost of getting it wrong will only increase.
SaaS firms that approach embedded finance with the same rigour they apply to their core product, weighing trade-offs, testing assumptions and building for the long term, will be best positioned to capture the revenue opportunity without taking on unacceptable risk.
