Why SaaS companies avoid the bank conversation
The sponsor bank relationship is the most consequential decision in an embedded payments program. It is also the one SaaS companies delay the longest. The reasons are consistent: the bank diligence process is slow and compliance-heavy, the requirements are unfamiliar (BSA/AML program documentation, financial statements, operating history), and the timeline — 6–12 months from first conversation to live program — feels incompatible with SaaS product development velocity.
So SaaS companies launch on Stripe, or BaaS, or a PayFac arrangement — and defer the bank relationship question to "later." Later arrives when the economics gap becomes visible, the product ceiling is hit, or a board conversation about payments monetization forces the question. By then, the program has been running for 12–24 months on infrastructure that wasn't designed for what the company actually needs.
The reframe that changes the calculus: the bank relationship is not a compliance project. It is a revenue decision. Every month it is deferred is a month of recoverable economics that doesn't recover.
The cost of delay in real dollars
A SaaS platform processing $5M monthly in payment volume on a BaaS arrangement is capturing approximately 70–90 basis points in net interchange. A direct bank relationship at the same volume captures approximately 140–160 basis points. The monthly economics gap: $35,000–$45,000. Annually: $420,000–$540,000.
Every month the bank relationship is deferred costs $35,000–$45,000 in economics that are gone. The bank relationship build — diligence, compliance infrastructure, onboarding — typically costs $150,000–$300,000 in total investment and 9–12 months of elapsed time. At the economics gap above, the payback period is 3–6 months post-launch. The deferral decision is not free — it has a measurable monthly cost.
At $10M monthly, the gap doubles. At $20M monthly, the annual gap between BaaS and direct exceeds $2M. The conversation that feels like a compliance overhead is actually a conversation about a seven-figure annual revenue decision.
What the bank relationship actually unlocks
Interchange economics. The most immediate unlock. Moving from BaaS revenue share to full interchange capture at a direct bank adds 50–90 basis points on card volume immediately. For a $5M monthly program, this is $30,000–$54,000 per month in additional economics that the BaaS middleware was capturing.
Float yield. Customer balances held in FBO accounts generate yield — currently 4–5% annualized on Fed Funds equivalent rates. BaaS providers retain this yield by default. A direct bank agreement makes float yield a negotiable term. At $2M average daily FBO balance, 4.5% annualized yield is $90,000 per year — a revenue line that doesn't exist in most BaaS arrangements.
Product flexibility. The bank relationship enables products that BaaS stacks don't support or don't support well: commercial card BIN categories with higher interchange rates, card issuing programs with specific spending controls, lending programs co-originated with the bank, and fee structures the BaaS layer doesn't enable.
Program independence. A direct bank relationship means your program isn't dependent on a BaaS provider's technology decisions, compliance posture, or business continuity. The 2023–2024 BaaS regulatory environment — which resulted in consent orders, program restrictions, and in Synapse's case, complete platform failure — demonstrated that program independence is not just an economics consideration.
What makes bank diligence move faster
The 6–12 month timeline for bank diligence is the median for programs that arrive unprepared. Prepared programs — those that bring a complete BSA/AML program document, a clear KYB/KYC process, financial statements showing runway, and a defined program model to the first conversation — move through diligence in 4–6 months. The preparation investment is 6–10 weeks of work. The timeline reduction is 2–4 months of additional economics at the gap rates above.
The specific preparation that matters: a board-approved BSA/AML program (the single most common reason bank diligence stalls is its absence), documented KYB/KYC processes, 18–24 months of financial runway or committed capital, and a clear program model document that answers the questions the bank's compliance team will ask. None of this requires legal complexity — it requires operational preparation.
When to start the bank conversation
The bank conversation should start when you can see $3M monthly processing volume within 12 months — not when you're already there. The bank relationship takes 6–12 months to establish. Starting when you hit $3M means the direct program launches at $5–6M monthly, capturing full economics from the point of the launch. Starting when you're at $5M means you've already incurred 12–18 months of the economics gap while the relationship is being built.
The correct trigger is forward-looking volume, not current volume. Start the bank conversation a year before you need the bank relationship, not when you feel the constraint of not having it.
Ready to start the bank relationship conversation? Read how ExpandUp approaches bank partner selection, or talk with us — we've been through this process from both sides of the table.