When a fitness studio management platform adds ACH payouts, a basis-point revenue stream starts flowing. Not to the fitness studios, not to their members, but to the platform itself — as a share of the transaction volume passing through its treasury infrastructure. This is the embedded finance revenue model, and it is genuinely misunderstood by most SaaS founders who have not yet built it. The misunderstanding goes in both directions: some teams overestimate how quickly the revenue compounds, others underestimate what the steady-state economics look like at meaningful volume.
What a Basis Point Actually Means in Practice
A basis point is one hundredth of one percent — 0.01%. In payment economics, revenue share is typically expressed in basis points (abbreviated "bps") because the numbers involved require that precision to be meaningful. 15 bps on a $10,000 transaction is $15.00. 15 bps on $1 million in monthly transaction volume is $1,500/month. 15 bps on $10 million in monthly volume is $15,000/month.
These numbers look modest when expressed as a percentage. They look different when expressed as a function of the platform's existing SaaS revenue. Consider a home services SaaS platform with 600 active HVAC and plumbing contractors paying $149/month each: $89,400/month in subscription revenue. If those 600 contractors each receive $8,000/month in ACH payouts through the platform's treasury product, that is $4.8 million in monthly payout volume. At 12 bps revenue share on payout volume, the platform earns $5,760/month — adding 6.4% to its top line without adding a single new subscriber. The treasury product's marginal cost to the platform (after the integration is live) is close to zero. The incremental revenue is nearly all margin.
Where the Basis Points Come From
The revenue share model is not arbitrary. It reflects the economics of the underlying payment infrastructure. In a typical BaaS arrangement, the revenue waterfall flows like this:
The bank partner earns float income on deposits held in the FBO account — the spread between what they pay on deposits (typically near zero for demand deposits) and what they earn deploying those funds. The bank also earns interchange on any card products in the stack. From this pool, the bank shares a portion with the BaaS infrastructure provider, who has negotiated a revenue share agreement as part of the bank partnership terms. The BaaS provider then shares a portion of their take with the platform partner — and this is the basis-point rev-share the platform sees.
ACH payouts specifically generate revenue in a slightly different way. The BaaS provider charges a per-transaction fee to the platform (or passes through NACHA network fees with a markup). The platform may absorb this fee, or may pass it through to the business customer as a convenience fee for instant or same-day settlement. The net to the platform is the difference between what it charges the customer and what it pays the BaaS provider — typically expressed as basis points when stated as a percentage of transaction value, or as a per-item spread when expressed absolutely.
Float income on stored balances adds another revenue layer. When businesses on the platform maintain positive balances in their virtual accounts — a gym holding $12,000 to cover next week's instructor payroll — the FBO account at the bank earns interest on those pooled deposits. In a higher-rate environment, this can be a non-trivial contribution to the revenue share pool. The Fed funds rate trajectory in 2022–2024 significantly increased the value of float income for BaaS providers and their platform partners relative to the prior zero-rate decade.
The Attach Rate Problem
The revenue math assumes that a meaningful percentage of the platform's existing customer base actually adopts the treasury product. This is the attach rate, and it is the variable that most financial models get wrong.
Naive models assume 60–80% attach rates because "our customers already trust us with their business, why wouldn't they use our banking product?" The more realistic picture: early attach rates for newly launched embedded finance products are commonly in the 15–35% range for the first six to twelve months, with growth driven by active promotion, in-app nudges, and demonstrable value delivery (the contractor who got paid same-day and told five peers). By month 18, platforms that actively invest in treasury product adoption often reach 40–60% attach rates among their addressable customer base. That is a reasonable planning assumption, not a guarantee.
The addressable base matters too. Not every customer on the platform will have a use case that fits treasury products. A solo practitioner who receives one payout per month and is satisfied with a paper check has lower treasury product value than a contractor who runs payroll for three employees, pays suppliers weekly, and needs same-day settlement to manage cash flow. The platform's customer segmentation should identify which cohorts have the highest financial needs before building adoption projections.
Tiered Pricing: How the Platform Decides What to Charge
The platform is not just a pass-through in this stack. It makes its own pricing decisions about what it charges its business customers for treasury features, and the spread between its costs and its charges is where the economics are controlled.
The most common structures are: flat per-transaction fee (e.g., $0.25 per ACH credit regardless of amount), percentage-based fee (e.g., 0.25% of transaction value, which is 25 bps), or tiered percentage-based fees that step down at volume. The flat fee favors high-volume, small-transaction use cases (a salon tipping $15 at a time to ten stylists) because the absolute fee is the same regardless of amount. The percentage fee favors large, infrequent transactions (a contractor receiving a $4,500 invoice payment) less well, because 25 bps on $4,500 is $11.25 — which may be competitive or may feel expensive depending on what comparable options cost.
The platform also needs to decide what to do with Same-Day ACH or RTP premium. The cost difference between standard ACH (1–2 day) and Same-Day ACH is real — typically $0.25–0.50 more per transaction at the BaaS layer. The platform can absorb this as a feature perk for premium tier customers, pass it through as a surcharge, or build it into tiered pricing where paying customers on higher plans get instant settlement included.
The Interchange Model for Card Products
If the platform extends to issuing business debit cards — a common next step after ACH payouts are established — the revenue model shifts to include interchange. When a business on the platform uses its virtual account's debit card to pay a supplier, the acquiring bank collects interchange from the merchant and a portion flows back through the card network to the issuing bank, and through the BaaS provider to the platform as interchange revenue share.
Typical interchange revenue share to a BaaS platform partner is in the 50–150 bps range on purchase volume, depending on the merchant category code and the card product type. Business debit cards earn higher interchange than consumer debit in some categories. The economics compound: a contractor who uses the platform's debit card to buy $2,000 in supplies per month generates $10–30/month in interchange revenue share to the platform on that spend alone, in addition to the ACH payout revenue.
We are not saying every vertical SaaS platform should rush to issue debit cards — it is a more complex product addition than ACH payouts, with its own KYB requirements, dispute handling obligations under Regulation Z and the EFTA, and card program management overhead. The point is that the embedded finance revenue model is not a single number but a portfolio of revenue streams that each compound with volume.
What the SaaS Multiple Does to This Revenue
One final dimension that is worth stating explicitly: embedded finance revenue carries a higher revenue quality multiple in SaaS company valuation than subscription revenue in most analytical frameworks, because it scales with customer economic activity rather than headcount. A SaaS subscription is a fixed monthly charge — the customer pays $299/month regardless of whether they had a slow month or a strong month. An ACH payout fee or interchange revenue grows when the customer's business grows. It is structurally more correlated with customer success.
This correlation has practical implications for the platform's business model: treasury revenue is a natural hedge against churn. A customer who is growing their volume and paying the platform an increasing percentage of their financial activity is more deeply embedded than a customer paying a flat subscription fee. The rev-share model aligns the platform's incentives with its customers' success in a way that per-seat SaaS pricing does not. That alignment is one of the structural reasons vertical SaaS companies with embedded finance products tend to show higher net revenue retention than comparable pure-software platforms.
The math takes time to compound. The attach rate takes months to build. The compliance program takes quarters to stand up correctly. But the revenue model, when running at scale, has a different quality and durability than software subscriptions alone — and understanding the mechanics precisely is the starting point for building it right.