How to Build a Banking App: Cost, Timeline, and BaaS vs. Custom

A credit union in the Midwest spends six months evaluating neobank vendors. None fit. Their members are small business owners. They need business checking, expense categorization, and a debit card that integrates with the credit union's existing loan data. Every BaaS platform they look at is built for consumer accounts. The ones that do business banking have onboarding timelines of eight months. The credit union ends up deciding to build.

That decision, and the path that follows it, is what this guide is about. Whether you are a fintech startup launching a consumer neobank, a community bank that wants a mobile-first layer, or a vertical SaaS company adding embedded banking to your product, the questions are the same: how much does this cost, how long does it take, and when does custom software make more sense than an off-the-shelf BaaS platform?

How much does it cost to build a banking app?

A BaaS-backed MVP with deposit accounts, a debit card, ACH transfers, and push notifications costs $120K-$200K and ships in 20-28 weeks. A full neobank with lending, savings goals, and multi-currency support runs $350K-$600K over 36-52 weeks. Building regulated infrastructure with your own banking charter starts at $2M and takes 24-36 months.

The $120K-$200K range covers KYC/AML flows, card program setup, core account management screens, and the compliance review cycles that BaaS providers require before you go live. Engineering is not the cost driver. Onboarding and compliance review cycles are. Most operators land closer to $160K-$180K once you account for the compliance configuration work that API documentation understates by a factor of three.

Who actually builds a custom banking app?

Not every operator who asks about building a banking app should build one. Here are the four that consistently have a real case.

Payroll and HR platforms adding earned wage access. When your platform processes payroll, you have the data that makes a deposit account valuable. The problem is leakage: you pay workers, and those funds immediately move to a bank the worker chose years ago. An embedded deposit account and a platform-issued debit card keeps those funds inside your product. The platform becomes the financial home, not just the payroll processor. That is a retention and monetization shift, not just a feature add.

Gig economy platforms with a churn problem. On-demand platforms that pay workers via standard bank transfer compete on rate alone. Platforms offering a spending account, instant payouts, and basic savings tools have a retention advantage that pure-rate competitors cannot easily copy. According to the Aspen Institute, financial wellness tools rank among the highest-valued benefits for gig workers, who often lack access to employer-sponsored financial products. The card and the account are a retention tool dressed as a financial product. According to the FDIC's 2023 National Survey of Unbanked and Underbanked Households, 44 percent of banked U.S. households now use mobile banking as their primary method of account access — nearly ninefold growth over the past decade — which signals how decisively financial behavior has shifted to mobile-first products.

Credit unions and community banks that need a digital-first experience. Core banking replacement costs $10M or more and takes years. A BaaS-backed mobile app lets a credit union compete with consumer neobanks on mobile experience without touching existing compliance and risk infrastructure. The core system stays put. The member-facing layer gets rebuilt.

Vertical SaaS companies where customers are already financially inside the product. A property management platform where landlords collect rent, pay contractors, and track expenses is a natural host for an embedded business account. The account is not a new product. It is the financial layer the existing workflows already need. Adding it increases average revenue per account and makes the SaaS product stickier.

Synapse, Unit, and Treasury Prime vs. custom banking software

Before deciding to build, you need to evaluate what BaaS platforms can and cannot do. The three most common options are Unit, Treasury Prime, and Synapse. Each has a different profile.

Unit targets consumer and business neobanks with modern REST APIs and fast developer onboarding. Their card program tooling is strong, their sandbox is well-documented, and they have pre-built KYC flows. If you are building a consumer-facing neobank or an embedded business account product and your requirements fit standard account structures, Unit is the fastest path to a live product. Compliance review typically takes four to eight weeks.

Treasury Prime focuses on community banks and credit unions that want to offer embedded banking to their commercial clients. Their model is bank-first rather than fintech-first: they connect you to a network of partner banks, which gives you more sponsor bank options than most single-bank BaaS providers. If you are a credit union building an embedded banking product for your small business members, Treasury Prime's banking network is worth evaluating.

Synapse operated as a middleware layer between multiple sponsor banks and fintechs, offering multi-bank redundancy. In 2024, Synapse filed for bankruptcy. Customer funds were frozen for weeks. The episode illustrated the specific risk of BaaS middleware: when the middle layer fails, the sponsor bank relationship and the customer funds are both at risk. Operators who had single-bank BaaS relationships with direct contracts were less exposed. Synapse customers who lacked that redundancy faced a painful forced migration.

Use a BaaS platform when:

• Your product fits standard account, card, and ACH structures without extensive customization

• You are pre-product-market-fit and need to ship in under six months

• Your transaction volume is under $100M annually and BaaS per-account fees are economically viable

• You do not need deep integration with proprietary non-banking data systems

Use custom banking software instead when you hit any of these thresholds:

1. Your card program requires non-standard fee logic, tiered interchange structures, or branded card features that BaaS platforms do not support
2. You need multi-BaaS redundancy at the infrastructure level, not just at the sponsor bank level, because sponsor bank concentration risk is unacceptable for your user base
3. Your product requires deep real-time integration with data systems the BaaS API cannot reach: proprietary ERP data, payroll records, property management ledgers, or loan performance data
4. Your annual transaction volume crosses $500M and the per-account and per-transaction fee structure makes BaaS meaningfully more expensive than owning the underlying infrastructure
5. Your product differentiation depends on capabilities that BaaS API constraints would prevent: custom risk scoring, proprietary fraud models, or account structures that do not map to standard checking/savings models

According to S&P Global Market Intelligence, neobanks that reach profitability do so primarily on debit card interchange and tight cost discipline on fraud and customer acquisition. The product advantage is the account experience, not the feature count. BaaS gets you to the account experience faster. Custom software gives you more control over it.

Banking app features: V1, V2, and V3

The fastest way to ship nothing is to build everything at once. The phasing below reflects what actually matters at each stage.

V1: Prove the account is useful ($120K-$200K, 20-28 weeks)

V2: Add reasons to keep funds in the account ($80K-$150K additional)

V3: Expand the financial product surface ($200K-$400K additional)

How a neobank actually makes money

Getting the revenue model wrong in V1 shapes the wrong features. The four revenue lines work differently depending on whether you are building a consumer neobank or an embedded banking product.

Interchange fees are the primary engine for consumer neobanks. Every time a user swipes your debit card, the merchant pays a processing fee and your card program earns a share, typically 0.5-1.5% of the transaction. According to Forbes, Chime was processing over $8 billion in annual transactions and generating roughly $600-$700 million in revenue from interchange alone. Interchange scales with card usage, not account count.

Subscription tiers work when you can deliver features users will pay for directly. Revolut charges $9.99-$16.99 per month for premium tiers covering travel insurance, higher ATM withdrawal limits, and multi-currency accounts. This model requires higher-engagement users than interchange alone.

Lending margin, meaning interest on overdraft facilities, personal loans, or buy-now-pay-later products, is where larger neobanks find their second growth curve. It carries more credit risk and regulatory complexity. It belongs in V2 or V3, not at launch.

For operators building embedded banking rather than a standalone consumer neobank, the math is different. The primary value of the bank account is retention and data. The account keeps users financially inside your platform, and monetization follows from that stickiness. Interchange is a secondary benefit, not the business model.

Where custom banking app projects fail

Most banking app overruns trace back to two specific failure modes. Both are foreseeable before a line of code is written.

Sponsor bank dependency built in at the architecture level. Single sponsor bank dependency is the most common architectural mistake in BaaS-backed builds, and it can cost $200K-$500K to unwind. After 2023, when regulators increased scrutiny on BaaS partnerships, several sponsor banks exited the market, some with 60 to 90 days' notice. American Banker documented the resulting scramble: neobanks on single-sponsor structures faced forced replatforms or shutdown on compressed timelines. The Synapse bankruptcy in 2024 made the risk concrete for the whole industry.

The fix is architectural: abstract the BaaS provider dependency from day one. Design your account model, card issuance flow, and transaction ledger so the sponsor bank is a pluggable integration, not a hard dependency baked into every API call. That abstraction costs roughly $15K-$25K in additional V1 engineering. A forced replatform costs $200K-$500K and nine months you do not have.

Deferring card fraud controls to V2. New debit card programs attract fraud within days of going live. Fraud rings test new programs with small transactions, then escalate. Programs without velocity limits, real-time transaction monitoring, and instant card freeze capability face chargebacks that can exceed $50K-$100K in the first 90 days. Some BaaS providers include basic fraud tooling. Most require explicit configuration. Building velocity rules, device fingerprinting, and instant card controls into V1 is cheaper than the chargebacks. This is the single most common place operators try to defer cost to V2 and then absorb a painful fraud event instead.

How RaftLabs builds banking apps

Every banking project we take starts with a BaaS provider audit before any engineering work. The provider you choose affects your compliance timeline, card program configuration options, fraud tooling, and fee structure. Choosing the wrong provider is a $50K-$100K mistake that shows up 18 months into the build, not at kickoff.

"The operators who ship fastest treat BaaS onboarding like a project track, not a vendor procurement," says Ashit Vora, co-founder of RaftLabs. "Start the compliance review on week one, run it in parallel with engineering, and you are not waiting 60 days for approval after the app is done. In every banking app build we have scoped, teams who skipped that step lost an average of six to eight weeks at the worst possible moment: right before launch."

Our default architecture for BaaS-backed builds isolates the banking provider dependency behind an internal service layer. That decision adds two to three weeks to V1 and saves months of replatforming if your sponsor bank relationship changes. We include V1 fraud controls, meaning velocity limits, device signals, and instant freeze, in every card program build. These are not optional line items.

If you are a fintech startup evaluating your first BaaS provider, a credit union deciding whether to build or buy, or a vertical SaaS operator scoping an embedded banking feature, we can give you a clear cost range and a provider recommendation in one conversation. Request a 30-minute scoping call and we will tell you which BaaS platform fits your user base, what the compliance timeline looks like, and where the real cost risk lives in your specific build.

RaftLabs is a product development studio. We build fintech products, SaaS platforms, and AI-integrated applications for founders and operators at growth-stage companies.