How to Pick Embedded Banking for SaaS Platforms

Who this is for

The founder, COO, or head of fintech at a vertical software company that already moves merchant money, or is about to, and now wants balances inside the product: accounts, wallets, payouts, or a ledger the merchants already live in. You are picking how to hold and move funds without becoming a bank.

This page is not the payments pick. If the job is taking a card rate, read How to pick payments first. It is not issuing spend cards as the primary job (cards) and not working capital (lending). It is also not a ranked table. The banking list is editorial. Order is not a score you can buy.

The decision tree (middleware BaaS vs bank APIs vs treasury/money-movement-only)

Three jobs get sold as “embedded banking.” They are not the same business. Name the job before you name a vendor.

Middleware BaaS. A software vendor sits in front of one or more chartered partner banks. You embed deposit accounts or wallets, a ledger, and rails (ACH, wires, book transfers, sometimes cards) through that vendor’s API. The vendor is not the bank. The partner bank holds the deposits (or FBO structures), sets KYC and KYB policy, and is named on disclosures. Production is a sales conversation plus bank diligence. On this directory that shape is Unit (accounts and wallets inside the product; not a bank and not a PayFac), Treasury Prime (multi-bank API; you still sign a direct partner-bank agreement; Treasury Prime does not hold the charter), Stripe Treasury (partner-bank financial accounts for business users on Stripe; not consumer wallets, not self-serve live), Synctera (accounts or wallets, optional card programs, and rails through one console), and Increase (partner-bank accounts including FBO constructs, rails, and optional issuing on the same stack; published fee schedule; Increase is not the bank). What you get: one integration and a path to accounts without a charter. What you do not get: the charter, a self-serve live start, or a guarantee that balances port if you leave.

Bank APIs. You contract with the chartered bank that owns the accounts. The bank sells its own APIs (and often a partner platform). There is no middleware layer claiming to be the bank. Diligence is a bank program conversation. The bank can still pause rails and is still named on deposit insurance, where it applies. On this directory that shape is Column (national bank; Column holds the charter), Lead Bank (Missouri-chartered FDIC bank; Partner Platform for fintechs; not the consumer retail brand page), and Cross River (NJ FDIC bank; accounts and rails through COS APIs; optional card programs). What you get: a named bank on the account and a direct program. What you do not get: a charter of your own, a published platform rate card on most of these pages, or production keys with no bank kickoff.

Treasury / money-movement-only. The job is operating payments: a unified ledger, ACH, wires, realtime rails, reconciliation, and (sometimes) connecting bank accounts you already have. The vendor is a technology company. A bank or other regulated payments partner still holds and moves funds. This is not the same as embedding FDIC accounts as a product your users open. On this directory that shape is Modern Treasury (payment accounts and ledger on a managed PSP, or bring-your-own-bank through the same API; not a consumer retail bank brand). Adjacent money-movement listings on the payments table (Dwolla, Astra, TabaPay) are rail jobs, not a deposit program. If you only need to move and reconcile money, do not buy a full BaaS program because the deck said banking.

Not this tree. Card acquiring and PayFac-as-a-service live on payments. Spend-card issuing as the primary job lives on cards. A deposit sponsor bank and a BIN sponsor can be the same bank. They are not automatically the same role. If the job is only cards, do not start here.

There is no public volume number on this directory that tells you when to go direct to a bank, and no public month count that makes a charter optional. Vendors will quote program minimums in a sales room. Those are commercial. This page will not invent a threshold.

Sponsor bank is the first honest question. Which chartered bank is on the account? Who is named on customer disclosures? Who holds the FBO or the demand deposit? Middleware that talks to several banks is still not the charter. Bank-API listings are the bank. Treasury listings name a payments partner or your own connected bank. If you cannot get the bank named in one sentence, you do not have a pick yet. Read sponsor bank.

Diligence is the bank’s, even when a middleware vendor runs the API. KYB on the businesses you board, KYC on control persons, and program approval sit with the bank’s policy. You can buy onboarding software and still not be the underwriter. Live money on every listing on this table waits on a sales or bank path. Increase and Modern Treasury publish usage-style pricing. That is a fee schedule, not a skip-diligence card.

Time-to-live is not a feature comparison. Nothing on the banking table is a self-serve charter. Sandbox may be public (Column). Sandbox credentials may wait on a technical kickoff (Lead Bank). Production keys wait on contracting and bank due diligence on all of them. This page does not print a month count. If a vendor will not say whether production waits on the bank, believe the listing that already said sales-led.

What you actually own is usually the product UX, the integration, and a fee, spread, or bounty on balances and rails. You do not own the charter. You do not own deposit insurance. You often do not own the account relationship if you leave. Ask whether end-user accounts are assigned to you, whether they port if you change middleware or banks, who the customer-facing disclosure names, and what happens to balances if the vendor or the bank exits the program. A multi-bank middleware pitch is not a portable book unless the contract says the accounts move. A direct bank API is not a charter you take with you.

Start here / Skip if

Start with middleware BaaS if you want accounts or wallets inside the product, you do not want the first conversation to be “we are applying to be a bank partner of record,” and you will still accept bank diligence through the vendor. Read Unit and Treasury Prime as two shapes of that job (operated program vs software plus a direct bank agreement). Read Stripe Treasury if the rest of the stack is already there and the users are businesses, not consumers. That is a fit check, not a rank.

Start with bank APIs if you want the named bank on the account, you will take a bank program conversation, and you do not want a middleware layer between you and the charter. Read Column, Lead Bank, and Cross River as the bank-of-record cluster. Confirm cards or lending as adjacent programs, not as proof you bought a full stack.

Start with treasury / money-movement-only if the job is a ledger and rails, including connecting bank accounts you already have, and you are not opening end-user deposit accounts as a product. Read Modern Treasury. If the job is a single rail, read the payments-table money-movement listings instead.

Skip becoming a bank. This directory does not sell a charter. Skip a consumer retail bank brand page. Skip any pitch that says production keys ship with no KYB and no bank. Skip this page if the job is only card checkout, only spend cards, or only working capital.

Live banking peers. Editorial fit only. Not a rank, not a buy order.

Unit: Middleware BaaS. Accounts and wallets without a charter. Not a bank and not a PayFac.
Treasury Prime: Multi-bank API plus a direct partner-bank agreement. Treasury Prime does not hold the charter.
Stripe Treasury: Partner-bank financial accounts for business users on Stripe. Sales-led. Not consumer wallets.
Column: National bank that owns the charter and sells its own APIs. Bank, not middleware.
Lead Bank: Missouri-chartered FDIC sponsor bank. Partner Platform for fintechs, not the retail brand page.
Cross River: NJ FDIC bank. Accounts and rails through the bank’s APIs. Optional card programs.
Modern Treasury: Payment operations and ledger. Managed PSP or bring-your-own-bank. Not a deposit charter.
Increase: Partner-bank accounts and rails, optional issuing, published fees. Increase is not the bank.

Banking-as-a-service: The embedded-accounts model. The platform is not the bank.
Sponsor bank: Who holds the charter. Every program on this page still needs one.
Know Your Business: Entity verification the bank or program will require before you board businesses.
BIN sponsor: Who holds the card-network range if you also issue cards. Not a synonym for sponsor bank.

FAQ

Does banking-as-a-service 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. Confirm the named bank on the contract and on customer-facing account documents.

Should I go through middleware or contract the bank directly?

Depends on the job, not on a volume number this page will not invent. Middleware is one integration and a vendor that already has bank programs. You still go through bank diligence, and you should ask what happens to accounts if you leave. Direct bank APIs put the named bank on the account and remove a middleware layer. You still do not own the charter. Treasury Prime is the middle shape: software plus a direct bank agreement.

Is a treasury or payments-operations API the same as embedding accounts?

No. Treasury and payment operations move and reconcile money, often on accounts you already have or on a managed PSP. Embedded banking in the BaaS sense opens end-user or merchant accounts at a sponsor bank inside your product. You can need both. They are not the same pick.

If I change vendors, do the deposit accounts come with me?

Often no, unless the agreement assigns the accounts and says they port. Balances sit at the sponsor bank under that bank’s program. Middleware that talks to several banks is not a portable book by default. Ask who the customer disclosure names and what a migration actually moves.

If I embed accounts, can I issue cards on the same program?

Sometimes, as an adjacent module (several banking listings mention optional cards). A deposit sponsor bank is not automatically a BIN sponsor. If spend cards are the job, read the cards table and BIN sponsor. Do not assume one bank contract covers both roles.

How to pick embedded banking for SaaS platforms