- BaaS pricing has four core components: a platform fee, a per-account or per-user fee, transaction fees, and an interchange split. Every quote you receive maps to at least two of these.
- Monthly platform minimums range from roughly $1,000 to $25,000 depending on the provider and your volume tier. If your projected revenue does not clear that floor, the unit economics break before you launch.
- Interchange revenue is the most misunderstood piece. Some platforms pass through 100% and charge on fees; others take a cut of interchange on top of everything else. The difference compounds significantly at scale.
- Most BaaS providers do not publish full pricing. This article lays out the fee structures that are publicly documented and benchmarks what negotiated ranges look like based on disclosed industry data.
- Real contracts vary significantly from any benchmark scenario. The figures in this article are reference points for evaluating quotes, not actual pricing you should expect to receive without a sales conversation.
- This page covers what BaaS providers charge buyers. Provider-side margin economics are covered separately in our hidden economics of Banking-as-a-Service piece, and how to price your own fintech product is covered in our fintech SaaS pricing models guide.
BaaS pricing follows four knowable structures: a recurring platform fee, a per-account charge, transaction-level fees, and an interchange revenue split. Most platforms combine two to three of these into a contract. Monthly minimums typically run between $1,000 and $25,000. Interchange splits vary from full pass-through to a 20-30% platform cut. A fintech processing $2M per month in card spend will pay materially different effective rates depending on which structure it signed, and that difference is predictable if you know what to look for before the sales call. Actual contract terms differ from any published benchmark, sometimes substantially, based on your product type, volume commitment, and sponsor bank relationship.
What Does BaaS Pricing Actually Include?
Most founders go into BaaS vendor conversations thinking about one number. The platform comes back with five. Understanding what each line item does is prerequisite to benchmarking any quote.
BaaS pricing assembles from a menu of components. A provider might charge all of them or only a subset, but the menu itself is consistent across the market. Here is how each one works in practice.
Platform Fee (Monthly or Annual Baseline)
This is the fixed cost of access to the BaaS stack: the bank connectivity, compliance infrastructure, API access, and support tier. It exists regardless of how many accounts you open or how much transaction volume you run. Providers use it to cover their own sponsor bank relationship costs and compliance overhead. For early-stage buyers, it is the number that kills unit economics first, because it does not scale down with slow months.
Per-Account Fee
Charged monthly per active account (or per end user account, depending on how the contract defines “active”). Some platforms waive this below a certain account threshold and then switch it on. Others tier it, so the per-account rate drops as your book grows. This is the fee that matters most for consumer-facing fintechs building wallet or deposit products, because it scales linearly with your user base.
Transaction Fees
ACH transfers, wire transfers, card transactions, and RTP payments typically each carry their own per-transaction fee. ACH fees in BaaS contracts generally run between $0.15 and $0.50 per transfer, depending on direction (credit vs. debit) and speed (same-day vs. standard). Wire fees are higher, often $5 to $25 per outbound wire. These numbers are consistent with what providers like Unit and Column have disclosed in documentation reviewed by developers on public forums.
Interchange Revenue Split
For platforms issuing debit or prepaid cards, interchange is the most financially significant line item, and the one most often buried in the term sheet. When a cardholder swipes, the merchant’s bank pays interchange to the card network, which flows to the issuing bank and then to the BaaS stack. The question is what percentage reaches you. Some providers pass through the full interchange and recoup their margin elsewhere. Others keep 20-40% of interchange as their primary revenue mechanism. At $2M monthly card spend with a 1.5% average interchange rate, a 30% platform cut translates to $9,000 per month that does not appear as a line item fee but quietly disappears from your revenue.
KYC and Compliance Fees
Many BaaS platforms charge per-verification for KYC at onboarding, and some add ongoing monitoring fees per account per month. These are sometimes bundled, sometimes passed through from third-party identity providers at cost-plus. The per-verification cost of KYC varies from under $1 to over $5 depending on check depth, and it is worth isolating this from the platform fee in any negotiation.
What Do BaaS Platforms Actually Charge? A Fee-Band Table
Most major BaaS platforms do not publish complete pricing. What follows reflects publicly available information from developer documentation, disclosed pricing tiers, and information that has appeared in industry reporting. Where a specific number is not publicly documented, the cell says so plainly. For Synctera and Treasury Prime specifically, almost no public pricing numbers exist, treat those rows as structural reference only, not price anchors.
| Platform | Monthly Platform Fee | Per-Account Fee | ACH Fee (per transfer) | Interchange Split | KYC Fee |
|---|---|---|---|---|---|
| Unit | Not publicly disclosed; reported minimum commitments in the $2,000 to $5,000/mo range based on developer forum discussions and fintech founder accounts | Not publicly disclosed; negotiated per contract | Not publicly disclosed; negotiated per contract | Disclosed as pass-through model in developer docs; platform margin via fees | Bundled; specifics not public |
| Column | No platform fee on public starter tier; pricing scales with usage | Not publicly disclosed | Publicly disclosed at $0.25 per ACH transfer on standard pricing page (as of public documentation) | Pass-through model disclosed | Not bundled; separate KYC vendor required |
| Synctera | Not publicly disclosed; enterprise negotiated. No public floor figures available, contact sales for any estimate. | Not publicly disclosed | Not publicly disclosed | Not publicly disclosed | Bundled with onboarding flow; specifics not public |
| Treasury Prime | Not publicly disclosed. Treasury Prime does not publish pricing. A floor in the $3,000 to $10,000/mo range has appeared in fintech founder accounts on X (formerly Twitter) and in recorded startup conference Q&As, but Treasury Prime has not confirmed any figure publicly, treat as directional only. | Not publicly disclosed | Not publicly disclosed | Not publicly disclosed | Not publicly disclosed |
| Marqeta (card issuing) | No traditional platform fee; revenue via interchange and per-transaction fees | Not applicable (card-focused) | Not applicable | Interchange-based revenue model described in Marqeta’s public investor filings; specific split terms are negotiated per program and not publicly disclosed | Not bundled |
| Stripe Issuing | No separate platform fee; integrated with Stripe account | Not applicable | $1.00 per ACH debit per public Stripe pricing page (US) | Interchange passed through to platform per Stripe docs | Not bundled; Stripe Identity sold separately |
| Lithic | Starter tier available; enterprise pricing negotiated | Not publicly disclosed at enterprise tier | Not applicable (card-focused) | Not publicly disclosed | Not bundled |
The opacity in this table is intentional on the vendors’ part, not a gap in research. BaaS providers price through sales conversations because their actual cost to serve varies significantly based on the sponsor bank relationship, the product type (deposit vs. card vs. lending), and the volume commitment you bring to the table. The absence of public pricing is itself a negotiating signal: it means every number is movable.
How Much Does BaaS Actually Cost? A Worked Scenario
Abstract fee components are hard to reason about. A concrete example makes the math tangible. The figures below are illustrative, real contracts vary significantly based on provider, product type, and negotiated terms. Use this as a modeling framework, not a pricing quote.
Say a Series A vertical SaaS company wants to embed deposit accounts for its 5,000 small business customers. It expects modest transaction activity per customer: two ACH transfers per month and light card spend averaging $500 per account per month.
At a platform charging $3,000 per month as a base fee, $2 per active account per month, $0.30 per ACH transfer, and retaining 25% of interchange on a 1.2% average interchange rate, here is the hypothetical monthly cost structure:
- Platform fee: $3,000
- Per-account fees (5,000 accounts at $2): $10,000
- ACH fees (5,000 accounts, 2 transfers each, at $0.30): $3,000
- Interchange retained by platform (5,000 accounts at $500 card spend, 1.2% interchange, 25% platform cut): $7,500
- Total monthly BaaS cost (hypothetical): $23,500
Against 5,000 accounts, that works out to $4.70 per account per month in loaded BaaS cost. If you are charging your SMB customers $15 per month for the banking product, you have $10.30 per account to cover your own infrastructure, support, and margin. If you are offering banking for free as a retention mechanic, those same costs come directly off your SaaS margin. This is the scenario where the hidden costs that kill fintech SaaS margins show up in your board deck. Your actual contract will almost certainly differ from these inputs, some providers charge more per account, some retain a larger interchange cut, and most have minimum commitments that change the floor calculation entirely.
What Are the Main BaaS Pricing Models?
Not every BaaS provider structures their pricing the same way. The market has settled into roughly four pricing architectures, and knowing which one you are looking at determines which levers are negotiable.
Fee-Forward Model
The platform charges explicit fees at every layer (platform, per-account, per-transaction) and passes interchange through to you largely intact. Your cost is visible and predictable. The primary negotiating points are the per-transaction rates and the platform minimum. This model favors buyers who can project volume accurately and who want to retain interchange revenue as a meaningful revenue line.
Interchange-Forward Model
The platform charges low or no explicit fees and makes its margin primarily by retaining a percentage of interchange. Early costs look lower, but the true cost scales with card volume in a way that is difficult to audit without transaction-level reporting. Marqeta’s business model, as described in its public investor filings, is the clearest example of this structure at scale. It is best for programs with low card volume and high non-card activity, where the platform’s interchange cut stays small in absolute terms.
SaaS Subscription Model
A flat monthly fee for API access and a defined feature set, with transaction fees capped or tiered. Less common in BaaS than in pure developer tooling, but some providers offer a startup tier structured this way to reduce friction at onboarding. The risk is that the cap or tier resets in ways that create surprise charges at growth inflection points.
Revenue-Share Model
The platform takes a percentage of the revenue your embedded banking product generates, which may include deposit interest spreads, late fees, or loan origination fees depending on the product. Common in embedded lending and BNPL-adjacent structures. This aligns incentives well early on but becomes expensive when your product matures, because the platform continues earning a cut of margin it no longer had to work to build.
The FintechSpecs BaaS Quote Stress Test
When a BaaS provider sends a term sheet, most teams look at the headline platform fee and move on. That is the wrong place to look first. The following four-step framework, which we call the BaaS Quote Stress Test, is designed to surface the fees that matter at scale before you sign.
Step 1: Calculate Your Fully Loaded Cost Per Account
Take the total projected monthly bill at your expected account count and divide by that account count. If the number is above $5 per account for a free banking product or above $8 per account for a premium banking product, you have a margin problem unless you are confident your revenue-per-account clears those thresholds with room.
Step 2: Isolate the Interchange Math
Ask the vendor for the exact interchange split percentage. Then run the math at three card spend volumes: your expected volume, 2x expected, and 5x expected. If the platform retains 25% of interchange and you are projecting $10M monthly card spend at 1.5% average interchange, the platform takes $37,500 per month in interchange alone. At 5x volume, that is $187,500 per month. That number should appear explicitly in your financial model before you sign.
Step 3: Map the Minimum Commitment
Most BaaS contracts carry a monthly minimum, meaning you pay the platform fee floor even if your volume does not generate fees that reach it. Identify the floor and calculate how many active accounts or how much transaction volume you need to organically hit it. If your go-live projection falls short of the minimum, you are paying a tax on slow growth. This is particularly relevant for teams still in the 500-2,000 account range.
Step 4: Audit the Pass-Through Costs
KYC fees, network fees, wire fees, and dispute-handling fees are often described as “pass-throughs” but sometimes arrive with a processing markup. Ask whether each pass-through has a markup percentage and cap it contractually. These costs are addressable at negotiation and are often overlooked because they appear small per event. At 10,000 KYC checks per month with a $0.50 markup per check, the markup line alone runs $5,000 per month.
What Factors Drive BaaS Pricing Up or Down?
BaaS pricing is not arbitrary. Providers charge more for programs that create more compliance burden or credit risk, and less for programs they consider clean and low-risk.
Product type is the largest driver. A deposit account program is simpler to underwrite than an embedded lending product. A prepaid card program with limited spend categories carries less fraud exposure than an unrestricted debit card. Platforms price risk into their fee structure whether they say so explicitly or not.
Volume commitment matters almost as much as product type. A company that can commit to $5M per month in card spend on day one of a contract negotiates from a different position than one projecting $200K. This is why comparing BaaS platforms purely on published rates misses the point. The published rate is rarely the rate you pay if you have credible volume projections.
Sponsor bank relationships also affect what you pay. Platforms that own their sponsor bank relationship outright (as Column does, operating as a chartered bank itself) have different cost structures than platforms that are middleware between you and a third-party bank. The middleware model adds a margin layer. For a detailed breakdown of how these economics flow, see our analysis of the hidden economics of BaaS.
Compliance complexity is the final major driver. Programs serving high-risk customer segments, cannabis-adjacent businesses, money service businesses, or internationally operating customers will pay more for the bank’s compliance review and ongoing monitoring. If your target market includes any of these, budget for a compliance premium of 20-40% on top of a standard program’s rates. The cost of compliance in regulated fintech is real and stage-dependent, as covered in the real cost of compliance in fintech SaaS.
How Does Managed Fintech Engine Pricing Differ from Standard BaaS?
A managed fintech engine sits above a raw BaaS API in the stack. Rather than giving you database access to account and transaction primitives, a managed engine bundles program management, compliance operations, dispute handling, and sometimes customer support into the contract. You pay more per account, but you also build less and hire fewer compliance and operations staff.
Providers offering managed fintech engine structures include Synctera, which explicitly markets a managed compliance layer, and several bank-owned BaaS arms that handle program oversight internally. The pricing premium for managed services over raw API access is material. Where a raw API BaaS might charge $1-2 per account per month, a managed engine can run $5-15 per account per month depending on the service scope.
The managed model makes financial sense for teams that lack an in-house BSA officer or compliance function. Building those capabilities yourself costs more than the premium in most cases until you clear roughly 50,000 active accounts. Below that threshold, outsourcing the compliance operations layer through a managed engine is usually cheaper on a fully loaded basis.
Frequently Asked Questions About BaaS Pricing
How much does Banking-as-a-Service cost per month?
Monthly BaaS costs depend on account volume, transaction activity, and interchange split terms. At a small scale (under 2,000 active accounts), you might pay $1,500 to $5,000 per month in platform and per-account fees. At mid-scale (10,000 to 50,000 accounts), total monthly BaaS costs commonly run between $20,000 and $80,000 before interchange adjustments. Most providers require a minimum monthly commitment regardless of actual volume generated. Real contracts vary significantly from these ranges based on product type and negotiated terms.
What is the difference between a platform fee and a per-account fee in BaaS?
A platform fee is a fixed monthly charge for API access, compliance infrastructure, and support. It does not change with the number of accounts you open. A per-account fee is variable and scales with your active user base. The platform fee is your floor cost; the per-account fee is what makes BaaS progressively more expensive as you grow. Negotiating both independently matters, because a low platform fee with a high per-account rate can be worse than the reverse at scale.
Do BaaS platforms take a cut of interchange?
Many do, but not all. Whether a platform retains interchange, and at what percentage, is one of the most financially significant terms in a BaaS contract. Some providers, including Stripe Issuing, pass interchange through to the platform operator per their published documentation. Others retain 20-40% of interchange as their primary revenue line. Always ask for the interchange split in writing as a specific percentage before signing, not just a description of the model.
What is a BaaS monthly minimum and how does it affect early-stage companies?
A BaaS monthly minimum is a floor payment regardless of the revenue your program generates. If your fees (platform plus per-account plus transactions) total $800 in a slow month but your contract minimum is $2,500, you pay $2,500. For pre-launch or slow-ramp programs, minimums can represent three to five times the revenue-justified cost. Negotiate minimum ramp periods or a lower minimum for the first 6-12 months whenever possible.
Does Treasury Prime publish its pricing?
Treasury Prime does not publish a public pricing page. Pricing is disclosed through a sales engagement. Treasury Prime has not confirmed any specific floor figures publicly. A minimum monthly commitment range in the thousands of dollars has appeared in fintech founder accounts on X (formerly Twitter) and in startup conference Q&As, but these are unverified third-party accounts, not official disclosures. Any figure requires direct confirmation from Treasury Prime during a vendor conversation.
What is the cheapest BaaS option for an early-stage startup?
Column’s approach as a chartered bank offering direct API access tends to have a lower barrier for early-stage programs because it removes one margin layer from the stack. Stripe Issuing is also accessible without a separate platform fee if you are already on Stripe and need card issuing specifically. The cheapest option depends on your product type. For deposit accounts, Column is worth evaluating first. For card programs with lower volume, Stripe Issuing or Lithic’s starter tier are the most documented low-entry-cost options.
How do I benchmark a BaaS quote I received?
Run the BaaS Quote Stress Test outlined in this article: calculate your fully loaded cost per account, isolate the interchange math at 1x, 2x, and 5x expected card volume, identify the minimum commitment and how long it takes your program to organically clear it, and audit every pass-through fee for markup. Then compare the resulting economics against the fee bands above and against the terms of at least two other platform quotes. Never evaluate a BaaS quote in isolation.
What This Means Before Your Next Vendor Call
The standard BaaS sales motion runs like this: the vendor leads with the platform’s feature set and compliance story, pricing comes late in the process, and the quote arrives as a combined minimum commitment figure that obscures the fee-by-fee breakdown. By then, you have spent three weeks in demos and your team has psychological momentum toward a decision. Understanding the four-component structure (platform fee, per-account, transaction fees, interchange split) before that conversation shifts who controls the frame.
The interchange question is where the most money hides. A platform charging $0 in platform fees and passing through only 70% of interchange on a program with $3M monthly card spend costs more than a platform charging $5,000 per month in platform fees and passing through 95% of interchange. At $3M monthly spend and 1.4% average interchange, the math shakes out to $12,600 per month in retained interchange for the first provider versus $5,000 plus $2,100 ($7,100 total) for the second. The “no platform fee” option costs $5,500 more per month. This is not an edge case. It is the normal arithmetic of a badly-read BaaS quote.
For teams still selecting a platform, the BaaS platform comparison on FintechSpecs covers the feature and compliance dimensions alongside pricing posture. The pricing framework on this page gives you the cost side of that evaluation. Run both in parallel, and go into every vendor call having already modeled the minimum commitment scenario at your realistic go-live account count. The vendor will know you have done the work, and the conversation will move faster.
