A Runway Worksheet for Fintech Platforms With Restricted Cash

Pull your balance sheet and list every bucket of cash separately: operating cash you can deploy freely, reserves held with a sponsor bank or payment processor, any net worth or bonding requirement tied to state licensing, and funds set aside against pending chargebacks or refunds. Add them up, then subtract everything except the first bucket. That smaller number, not your total cash balance, is your real runway denominator. A lot of founders discover their actual runway is meaningfully shorter than the number on the balance sheet suggested, simply because a large restricted-cash bucket was hiding inside the total the whole time.

Embedded finance and payments platforms often earn per-transaction or per-account fees, which is a different shape of revenue than a SaaS subscription. Usage-based revenue tied to transaction volume can grow or shrink with a client's own business cycle, which makes it look less predictable to a lender than a fixed monthly software fee, even when your relationship with that client is genuinely stable. If you have any piece of revenue on a fixed monthly platform fee or minimum commitment, separate that out, because it's the piece most likely to qualify for a revenue-based advance.

Venture debt is more common here than in a lot of the other categories in this comparison, because fintech companies are more often venture-backed to begin with, and specialty lenders who understand payments and compliance economics do exist. But a lender underwriting a fintech platform will ask about your restricted cash specifically, since it reduces the cushion they're counting on if growth slows. Expect a lender's covenants to reference your usable cash balance, not your total balance sheet cash, and make sure your own tracking matches that definition before you're negotiating the term sheet.

• If the gap is genuinely about extending runway to a milestone, and your restricted cash is a known, stable percentage of your balance, venture debt sized conservatively against usable cash is a reasonable option.
• If your revenue is mostly usage-based and volatile with client transaction volume, a revenue-based advance may undersize what a lender expects, since usage-based revenue is harder to size against confidently.
• If a meaningful and growing share of your restricted cash is tied to licensing requirements as you expand into new states, treat that as a planned cost of expansion, not a surprise eating into runway you thought you had.
• If you're not sure how a lender will treat your restricted cash, ask directly and early. It's a normal question, and getting a clear answer before you're deep into a process saves everyone time.

Beyond the usual financials, expect questions about your sponsor bank relationship and its stability, your compliance program (know-your-customer and anti-money-laundering controls), and your licensing footprint state by state. A lender who's done this before will read your restricted-cash schedule closely, because it tells them more about your real financial flexibility than your headline cash balance does. Coming to that conversation with a clean worksheet, rather than making them extract the numbers from you, is one of the fastest ways to build credibility in the process.

A restricted-cash worksheet isn't a one-time exercise. Adding a new state license, renegotiating terms with your sponsor bank, or launching a new product line that carries its own reserve requirement all change the usable-cash number, sometimes significantly. Say your platform expands into five new states in a single quarter to support a large client's rollout: each of those states may carry its own net worth or bonding requirement, and stacking them can eat into usable cash faster than the revenue from that expansion shows up to offset it.

Build a habit of rerunning the worksheet whenever a material change happens, not just once a year during planning season, so your runway number stays honest as the business grows in directions that carry their own regulatory weight.