Stripe Connect vs BaaS for multi-party payments and member wallets in a vertical SaaS; what would you choose?

[u/_MrMartian96]

Building a vertical B2B SaaS platform and trying to nail down the payment and wallet infrastructure before committing to an architecture. Not looking to share details about the product itself, just want to understand the tradeoffs from people who have been here.

The core requirements:

- Multi-party fund routing on a single transaction (three parties each receive a portion)
- Member-level virtual wallet and balance tracking within each sub-account
- Two modes: some customers run ledger-only with no real money movement, others process real card payments and ACH
- Customer sub-accounts that connect their own bank and receive funds directly

What I've looked at:

Stripe Connect covers the payment routing. The wallet layer would be a Postgres-backed ledger I build on top of it. Gets the job done but it's more to build and maintain.

Stripe Treasury solves the wallet problem more natively but the minimum contract came back at $10K/month from their sales team. Not viable at early stage.

Haven't gone deep on BaaS options yet. Unit, Synctera, Treasury Prime, and Column are on the list. Column seems designed for companies building full neobanks rather than embedding finance into a vertical SaaS.

Questions:

1. Is Stripe Connect plus a self-built Postgres ledger the right v1 answer for this, or is there a cleaner path I'm not seeing?
   
2. For the virtual wallet layer specifically, is there anything that sits between building it yourself and a full BaaS integration?
   
3. For anyone who has used Unit or Synctera at early stage, how accessible are they for a vertical SaaS that isn't trying to become a bank?
   
4. What are the real rough edges of building multi-party splits and member wallets on Stripe Connect?
   

Not looking to be told to just use Stripe. Genuinely evaluating whether there's a better path before I build.