Unit vs Treasury Prime vs Stripe Treasury for vertical software: bank relationship, accounts, and when to pick which

Who this is for

The founder, COO, or head of fintech at a vertical software company that wants balances inside the product: deposit-style accounts, wallets or FBO structures, and money movement on US rails, without holding a bank charter. You are picking how embedded banking is structured, not shopping a consumer neobank app.

Wall-off. This page is not card acquiring or PayFac-as-a-service (see payments and How to pick payments). It is not spend-card issuing as the primary job (cards), not working capital (lending), and not treasury/money-movement-only ops where you are not opening end-user accounts as a product (read How to pick banking for that third branch). It is also not a direct bank-API pick (Column, Lead Bank, Cross River); those are the bank-of-record cluster on the same pick page.

Pair with How to pick banking for the middleware vs bank-API vs treasury decision tree and Banking-as-a-service for the model definition. Full listings: Unit, Treasury Prime, Stripe Treasury. Order on any related list is editorial fit, not a score you can buy.

Side-by-side

Facts below track greened listings and live marketing posture as of this page’s updated date. Cells say not published when marketing does not show a usable platform rate card. This directory does not invent deposit thresholds, go-live month counts, or FDIC language beyond what vendors and listings already state.

Dimension	Unit	Treasury Prime	Stripe Treasury (for platforms)
What it is	Banking-as-a-service middleware for software platforms: partner-bank deposit accounts and FBO wallets, plus money-movement rails on those accounts, through Unit’s API. Unit is not a bank.	Embedded banking software (Bank OS / multi-bank API): open partner-bank deposit accounts (on-core or ledger/FBO shapes), run a ledger, move money on US rails. Treasury Prime is not a bank; it writes the software.	Stripe’s API for platforms to embed financial accounts for connected business users: store funds, move money on partner-bank rails, optional adjacent Stripe products. Stripe is not a bank. Distinct from Stripe’s Dashboard merchant Treasury product.
Who holds the charter / bank posture	Partner banks hold the charter. Unit legal product-terms pages name Thread Bank, i3 Bank, Lincoln Savings Bank, Five Star Bank, Pacific West Bank, and TransPecos Bank. Custom Platform path: you hold a direct relationship with one or more partner banks through Unit’s API. Managed Solutions / Ready-to-Launch Banking: Unit operates the module; Ready-to-Launch footnote names i3 Bank, Member FDIC.	Partner banks in Treasury Prime’s Bank Network hold the charter and FDIC coverage. Platform signs a direct bank agreement. Newsroom and network copy have named KeyBank, People Trust Community FCU, U.S. Bank, i3 Bank, Coastal, and others; network size figures vary by page (treat as vendor copy). Find a Bank matches you into a sponsor.	Stripe is not a bank and not an FDIC-insured depository. Greened listing: US funds eligible for FDIC pass-through insurance are held at Fifth Third Bank, N.A., Member FDIC. Stripe Payments Company is the licensed money transmitter. Stripe’s messaging guide tells platforms not to call these bank accounts, checking accounts, or savings accounts.
Go-live	Sandbox signup is public. Production is not self-serve: diligence, insurance, end-user terms, reserve, and bank-partner introduction before production keys (per Unit onboarding docs cited in the listing). Managed Solutions marketing claims a faster path than custom; still commercial. Contact sales for live.	Sandbox signup is public. Production is not self-serve: Find a Bank or contact sales, direct bank agreement, bank diligence, bank-approved funds flow and KYC, then production credentials.	Sandbox with Treasury-for-platforms access for build. Live access is sales-led (contact embedded-finance sales). Listing: public preview in the UK; private preview in the US and listed EU countries as of the listing’s sources. Not a public self-serve live start.
Pricing posture (live marketing)	Not published. No public platform rate card. Managed Solutions copy describes revenue share on transaction and deposit revenue (Unit absorbing fraud losses on that path per Unit’s copy). Platform / custom path economics are contractual.	Not published. Commercial pages describe usage-based pricing without a rate card.	Not published for Treasury for platforms. Stripe’s public Pricing page Treasury section covers the merchant Dashboard financial account, not this platform product. Eligible US platforms may contract an administrative facilitation fee on connected-account balances (per listing).
What you embed (this evaluation)	Deposit accounts (DDA at partner bank) and wallet (FBO) accounts; ACH (including same-day), wires, RTP, checks, book payments, and related rails Unit lists. Cards, capital, and bill pay are Unit products; they are adjacent, not this guide’s core pick.	On-core or ledger/FBO deposit accounts with routing and account numbers; ACH, wires, book transfers; check deposit/issue; FedNow and network transfers where the bank enables them. Card issuing and other TP modules are adjacent, not this evaluation.	Financial accounts for business connected accounts (storage and related shapes); US financial addresses (routing/account numbers); ACH, wire, RTP (preview), book movement between financial accounts; optional Issuing/Capital adjacency on Stripe. B2B only on current requirements docs. Not a general consumer wallet.
Ops / KYC posture	Unit applications flow: Unit KYC/KYB or bring-your-own vendor in coordination with the bank. Custom path: you own more program and bank relationship work. Managed Solutions: Unit operates banking under your brand.	KYC/KYB in Apply flow, or Incremental KYC. Built-in KYC or bank-approved BYO vendor. Any KYC change needs bank approval. You hold the direct bank relationship and program control Treasury Prime markets.	Stripe handles identity verification for KYC/compliance through Stripe platform onboarding workflows. Platforms collect entity and owner details and acceptance of Stripe and Treasury-for-platforms terms. Capabilities stay restricted until requirements are met.
Best for	US vertical software that wants partner-bank accounts or wallets inside the product and will choose custom (direct bank relationship + Unit infra) or Managed Solutions (Unit operates Banking).	US software/fintech that wants a multi-bank API, will sign a direct partner-bank agreement, and wants on-core or ledger account structures with the bank in the loop on KYC and funds flow.	Platforms already on Stripe that want partner-bank financial accounts and money movement for business users, will accept sales-led / preview access, and will follow Stripe’s allowed messaging (financial account / wallet language, not “bank account”).
Not for	Published buy rate; self-serve production keys; treating Unit as a PayFac or as the bank. If the job is merchant card acceptance only, read payments listings instead.	Production keys without a signed partner-bank agreement and bank diligence; expecting Treasury Prime to hold the charter; pure self-serve live start.	Consumer wallets as the general offering; self-serve live without a Stripe sales conversation; marketing these balances as bank/checking/savings accounts; treating Dashboard merchant Treasury pricing as the platforms product rate card.

Decision notes

Facts vs verdict. The table is facts from greened listings and public marketing posture. The notes below are editorial judgment. They are not a rank and not a #1 crown.

Name the bank before you name the middleware. Every row still needs a sponsor bank. Unit and Treasury Prime are middleware/software in front of partner banks. Stripe Treasury sits on Stripe’s partner-bank program (Fifth Third named for eligible US funds in the listing). If you cannot get the bank named in one sentence, you do not have a pick yet. Read Banking-as-a-service.

Direct bank agreement vs operated program vs Stripe program. Treasury Prime’s default story is software plus a direct bank MSA. Unit’s custom Platform path is similar (direct bank relationship through Unit’s API). Unit Managed Solutions is Unit operating Banking under your brand. Stripe Treasury is Stripe’s platform program: Stripe runs KYC workflows and money-transmitter posture; you do not shop a separate “Find a Bank” marketplace the way Treasury Prime sells it. Pick the relationship shape you actually want to operate.

No invented volume or month gate. This directory does not publish a deposit AUM number or a month count that moves you from middleware to a direct bank API. Vendor onboarding guides may cite typical timelines (Unit’s custom onboarding guide states a typical custom launch of 2 to 3 months; Managed Solutions pages claim three weeks or less). Those are vendor claims, not Vert SLAs. Ask in the sales room. Do not paste a blog statistic into a board deck as if Vert certified it.

Published pricing is absent on all three for this job. Kill a deal that will not state who the bank is, who customer disclosures name, whether accounts port if you leave, and what your economics are (revenue share, per-account fees, facilitation fee, or other). “Usage-based” without a card is still not published.

Financial account ≠ bank account (Stripe). Stripe’s own messaging guide for Treasury for platforms forbids calling these bank accounts, checking accounts, or savings accounts. If your product marketing needs the words “bank account” and “FDIC-insured checking” as the customer-facing story, confirm what your bank program and counsel will allow on Unit or Treasury Prime before you assume Stripe Treasury fits the copy.

When to pick Unit. You want accounts or wallets inside a US vertical product, will accept partner-bank diligence, and want either custom infra with a direct bank relationship or a Managed Solutions path where Unit operates Banking. You are not buying Unit because you confused BaaS with PayFac.

When to pick Treasury Prime. You want multi-bank optionality, will complete Find-a-Bank (or equivalent) diligence, will sign a direct partner-bank agreement, and care about on-core vs ledger account structure. You will not get production keys without the bank.

When to pick Stripe Treasury. The rest of the stack is already Stripe, users are businesses (not consumers on the general offering), you will talk to sales and live with preview/availability constraints Stripe documents, and you will market balances with Stripe-approved language.

None of these three if. You need the bank itself on the contract as API seller (read Column / Lead Bank / Cross River on pick banking). You only need a ledger and rails on accounts you already have (treasury/money-movement-only branch). You only need card acquiring. You need consumer deposit accounts as Stripe’s general Treasury-for-platforms offering (it is B2B on current requirements).

How to pick banking: Middleware BaaS vs bank APIs vs treasury/money-movement-only.
Banking-as-a-service: Embedded accounts model; the platform is not the bank.
Sponsor bank: Who holds the charter.
Unit: Custom or Managed Solutions BaaS middleware; not a bank; not a PayFac.
Treasury Prime: Multi-bank software plus direct bank agreement; not the charter.
Stripe Treasury: Partner-bank financial accounts for business users on Stripe; sales-led / preview.

FAQ

Are Unit, Treasury Prime, and Stripe Treasury all “BaaS”?

Roughly yes in the directory sense: software platforms embed partner-bank balances without holding a charter. The shapes differ. Unit is middleware (custom or managed). Treasury Prime is banking software plus a direct bank agreement. Stripe Treasury is financial accounts on Stripe’s partner-bank and money-transmitter stack for platform business users. Read each listing for who the bank is.

Does picking any of these make my company a bank?

No. The chartered sponsor bank is the bank. You are a software platform or program manager on that bank’s program. Deposit insurance, where it applies, sits with the bank under FDIC rules. Confirm the named bank on contracts and customer-facing disclosures.

Which one has public pricing?

None of the three publish a usable Treasury-for-platforms / BaaS platform rate card on marketing for this job. Unit and Treasury Prime are not published. Stripe’s public Pricing Treasury section is the merchant Dashboard product, not Treasury for platforms. Ask for the commercial stack in writing.

Can I start on Stripe Treasury and later move accounts to Unit or Treasury Prime?

Often balances do not port just because you change middleware. Accounts sit at a sponsor bank under that bank’s program. Ask who disclosures name and what a migration actually moves before you assume portability. This directory does not invent a migration path.

Is Stripe Treasury the same as the Treasury product in the Stripe Dashboard?

No. Dashboard Treasury is a merchant money-management financial account. Treasury for platforms is the embed product for connected business users. This guide and the Stripe Treasury listing evaluate the platforms product.