Banking

Unit

Embedded banking infrastructure for software platforms that issue partner-bank deposit accounts and wallets, move money on US rails, and run the program through Unit's API.

  • Best ForUS software that needs accounts and wallets inside the product without a charter.
  • Not Fora bank, and not a PayFac.
  • Updated 26 Aug 2026

Banking-as-a-service on partner banks, not a bank and not a PayFac. Custom build if you want the bank relationship and the ledger. Managed Solutions if you want Unit to operate banking for a revenue share.

What it is

Unit is Unit Finance Inc.’s financial infrastructure platform for software companies that want to store, move, spend, and lend money inside their products. The homepage and docs call it enterprise-grade financial infrastructure. Footer and legal copy state that Unit is a financial technology company and not a bank. Banking services are provided by Unit’s bank partners, Members FDIC.

Two implementation paths sit on the same ledger. Building on the Platform is the custom path: API, dashboard, and optional UI components, with a direct relationship to one or more partner banks. Managed Solutions (announced as Ready-to-Launch) embed Banking, Bill Pay, or Capital as modules Unit builds and operates. The Banking module is accounts, payouts, and branded cards under the platform’s brand.

This page is the banking product: deposit accounts and wallet (FBO) accounts, plus the money-movement rails attached to those accounts. Cards, capital, and bill pay are Unit products. They are not this page.

Who it’s for

Two shapes, from Unit’s own pages:

  • Software platforms building on the Platform, where the company wants deposit accounts or wallets inside the product and holds a direct relationship with a partner bank through Unit’s API. The enterprise-grade infrastructure guide says you choose the bank partner, negotiate terms directly, and Unit provides the infrastructure.
  • Software platforms embedding Managed Solutions, where Unit runs the Banking module (and optionally Bill Pay or Capital) under the platform’s brand. The vertical SaaS page sells this path as a way to go live quickly and keep an existing payment processor.

Use-case pages also name businesses, consumers, and independent workers as end-customer types. Accounts-and-wallets copy covers businesses, sole proprietors, and individuals.

It is a fit for a US vertical software company that wants partner-bank accounts, wallets, and ACH, wire, RTP, and check movement inside the product, and does not hold a bank charter.

Standout details

  • Deposit accounts are DDAs held at partner banks, with routing and account numbers, and are described as FDIC-insurance eligible under the bank’s charter. Wallet accounts (FBO) sit on Unit’s native ledger as balances that are not traditional deposit accounts. Wallets docs say they can originate and receive ACH, originate wires, do book payments and checks, and support prepaid or benefits cards, subject to bank-partner approval. Production wallet terms are configured by contacting Unit.
  • The money-movement page lists ACH and same-day ACH, wires and reverse wires, check deposit and lockbox, check printing and mailing, international payments, push-to-card, RTP, and book payments. The platform page states Unit is a registered Fed service provider with direct submission to Fedwire, FedACH, and check infrastructure, plus direct Visa and Mastercard connectivity. Visa debit cards are issued by Unit’s bank partners under a Visa license. Card issuing is Unit’s product. It is not this page.
  • Applications docs describe a non-documentary KYC and KYB flow: most applications approved in under five seconds, documents when Unit flags an exception, and manual review under a two-business-hour SLA. Bank partners can vary requirements. Thread Bank has separate application docs. The KYC guide and platform copy let platforms use Unit’s KYC and KYB or bring their own vendor, in coordination with the bank.
  • Production is not self-serve. Docs’ onboarding checklist requires due diligence, insurance, end-user terms, a reserve account, and a bank-partner introduction before production API keys. The onboarding guide states a typical custom launch of 2 to 3 months. Managed Solutions pages state three weeks or less and one line of code. Sandbox signup is public at unit.co/sandbox (it redirects to app.s.unit.sh/signup). Terms limit sandbox to dummy data and internal evaluation. Live sales start at Contact sales.
  • Unit does not publish a public pricing page. Managed Solutions copy describes a revenue share on transaction and deposit revenue, with Unit absorbing fraud losses on that path. The configuring-your-build guide says the Platform path has more favorable variable economics and that the platform bears risk per its agreement. This listing does not repeat a rate card.
  • Partner banks named on current Unit legal product-terms pages: Thread Bank, i3 Bank, Lincoln Savings Bank, Five Star Bank, Pacific West Bank, and TransPecos Bank. A July 2025 Ready-to-Launch announcement states banking services for that path are provided by i3 Bank, Member FDIC. The platform page sells holding direct relationships with one or multiple partner banks through Unit’s API.
  • Geography is the United States. Terms of service say Unit is designed to be used within the United States. Privacy policy says personal data is collected and stored in the United States. Security page states SOC 2 Type II and PCI DSS Level 1, with applications on AWS. Homepage states $100B+ annual transaction volume, 5M+ accounts, and 11M+ API calls per day. Those figures are Unit’s.
  • Homepage names Highbeam, Benepass, Relay, and RentSpree with quotes. Relay’s quote says the company scaled on Unit past $1B in deposits. Managed Solutions and homepage also name Wix (banking for merchants) and Heard. Adjacent Unit products include card issuing (debit, credit, prepaid), capital and lending, and bill pay. Those are Unit’s. They are not this page. Vertical SaaS and Managed Solutions pages say the banking module works with an existing processor, naming Stripe Connect, Adyen, and others.

Sources: unit.co, Platform, Accounts and wallets, Money movement, Managed Solutions, Managed Solutions Banking, Vertical SaaS, About, Security, Privacy Policy, Terms, Contact sales, Sandbox, Docs overview, Applications, Customers, Wallets, Onboarding, Payments API, Cards API, Enterprise-grade infrastructure, Configuring your build, Bank partner onboarding, KYC guide, Embedded banking guide, Ready-to-Launch announcement, Thread Bank terms, i3 Bank terms, Lincoln Savings Bank terms, Five Star Bank terms, Pacific West Bank terms, TransPecos Bank terms, Card issuing, Lending.

Honest verdict

Unit is the listing to read when the job is embedded banking for a US software platform: partner-bank deposit accounts or FBO wallets, ACH, wires, RTP, and checks on those accounts, and a ledger you can run custom or hand to Unit. Unit is not a bank. The charter sits with the partner banks. On the custom path you hold the bank relationship. On Managed Solutions, Unit operates the Banking module and the Ready-to-Launch footnote names i3 Bank.

What it is not: a payments PayFac, a published buy rate, or a self-serve live start. Stripe Connect, Finix, and Rainforest are acquiring products. Unit’s own vertical SaaS page treats those processors as something you keep while adding banking. If the job is merchant card acceptance, read those listings. If the job is accounts at a partner bank inside the product, start here.