Questions to Ask a Partner Bank or BaaS Provider First
Before you sign, get a straight answer in five areas: their compliance program's real strength, the financial stability of the bank and any middleware layer between you and it, a realistic integration timeline, a complete pricing schedule, and the termination and reserve terms that govern how you exit. A provider that goes vague on any one of these is telling you something, no matter how reassuring the pitch sounds.
Quick Answer: Push for specifics on compliance program strength, program stability, integration timeline, pricing, and termination/reserve terms before you sign anything. Sales decks answer none of these honestly — only direct questions, asked in writing, do.
Your partner bank or banking-as-a-service (BaaS) provider isn't a vendor you can swap out after a bad quarter. It's the regulatory backbone your product operates under, and a weak one can freeze your customers' funds, force an emergency re-platform, or end your company outright — regardless of how good your product is. This checklist assumes you've already narrowed the field using criteria like the ones in our BaaS provider shortlist for fintech founders; it's what you ask each finalist before you sign, not how you build the list. If you're still deciding whether a partner-bank model is the right starting point at all versus pursuing your own license, read bank partnership vs. your own license: which path first before you go further down this path.
Treat this the same way you'd treat any high-stakes vendor comparison: put every finalist's actual answers side by side in one document, not your impression of the sales call. The discipline is the same one behind our complete competitor analysis playbook — structured, criteria-first comparison beats gut feel every time, and it beats it hardest when the stakes are this high. For the regulatory landscape this checklist sits inside, see our guide to fintech regulations for first-time founders.
The Checklist: Questions Grouped by Area
Work through each group with every finalist on your shortlist, and write the answers down verbatim rather than paraphrasing them from memory afterward. A provider that answers well in a live call but won't put the same answer in writing has just given you a different answer.
Compliance program
- 1. Who owns BSA/AML compliance for your specific program, and how many dedicated staff support it — not the bank's entire portfolio of fintech partners?
- 2. When was their most recent regulatory exam, and did it result in a consent order, a matter requiring attention, or any other formal finding? If so, is it resolved, and can they show you the resolution?
- 3. How do they monitor your program's transactions for suspicious activity specifically — is monitoring automated, who reviews the alerts, and what's the escalation path when something looks wrong?
- 4. If a regulator later finds fault with your program specifically, what happens to your ability to keep operating while it's remediated?
Program stability and financial health
- 5. How many other fintech programs do they currently support, and is a program your size meaningful to them or a rounding error they could drop without noticing?
- 6. Have they disclosed any recent capital concerns, and are they willing to discuss their financial position, not just their growth story?
- 7. If a BaaS middleware layer sits between you and the chartered bank, who holds the ledger of record — you, the middleware provider, or the bank — and how is reconciliation between those systems actually verified?
- 8. What happens to your program and your customers' funds if the middleware provider or the bank itself runs into financial distress?
Integration and technical fit
- 9. What's a realistic integration timeline based on programs of comparable complexity to yours, not the best-case number in the sales deck?
- 10. What does a production-equivalent sandbox actually include, and in what specific ways will the real production environment differ from it?
- 11. Who owns incident response when the API goes down outside business hours, and what's the actual resolution-time commitment, in writing?
- 12. How do they version their API and give notice before a breaking change ships?
Pricing and fee structure
- 13. Can they provide a complete, line-itemized fee schedule covering every activity your product will generate — not a summary, the actual schedule?
- 14. Does pricing change as you scale, and what are the actual tiers — not "we'll work something out when you get there"?
- 15. Who absorbs the cost of chargebacks, failed transactions, and confirmed fraud losses — you, them, or a split, and under what conditions?
- 16. Are there minimum monthly fees or minimum volume commitments, and what happens if you fall short of them?
Termination, reserves, and exit
- 17. Can you see the actual termination clause in the contract, not a verbal summary of it, including the notice period each side is required to give?
- 18. What reserve requirements apply to your program, and under exactly what conditions can the bank or provider increase the reserve?
- 19. What happens to customer funds and data during an offboarding, and how long does that process typically take from notice to completion?
- 20. Will they connect you with a reference from a fintech that has already offboarded from their platform — not only a reference from one still on it?
Item-by-Item Rationale: What a Bad Answer Looks Like
Every question above exists to surface a specific failure mode before it becomes your failure mode. The table below pairs each group with what a bad — or evasive — answer actually sounds like, and what a good answer should tell you instead.
| Question(s) | What a bad answer sounds like | What a good answer should tell you |
|---|---|---|
| 1–4 (compliance) | "Our compliance program is best-in-class" with no specifics on staffing, exam history, or monitoring process | The name of who owns your program's compliance, a documented exam history, and a specific monitoring and escalation process |
| 5–8 (stability) | Refusing to discuss portfolio size, capital position, or how the ledger reconciles across the middleware and the bank | A candid sense of how significant your program is to them, and a clear, verifiable answer on who holds the ledger of record |
| 9–12 (integration) | A flat "4 to 6 weeks" with no detail on what changes between sandbox and production | A timeline grounded in a comparable program's actual experience, plus a specific list of sandbox-to-production differences |
| 13–16 (pricing) | "Let's finalize pricing after you sign" or a fee schedule with unexplained catch-all line items | A complete, line-itemized schedule you can model against your own unit economics before you commit to anything |
| 17–20 (termination) | "Standard terms" offered instead of the actual clause, or reluctance to provide an offboarded reference | The literal contract language, a specific reserve-increase trigger, and a reference willing to describe their own exit |
Read across the table and the pattern is consistent: a good answer is specific, verifiable, and put in writing without you having to push twice. A bad answer is reassuring in tone but empty of anything you could act on — and tone is exactly what a sales process is optimized to get right.
Failure Modes Each Question Prevents
These questions aren't hypothetical caution. Each one maps to a failure pattern that has played out publicly across the banking-as-a-service industry, not just to a theoretical worst case.
- Skipping the compliance questions (1–4): Several sponsor banks have been the subject of public regulatory consent orders in recent years after examiners found their BSA/AML programs hadn't kept pace with the number of fintech partners they'd taken on. When that happens, banks under a consent order commonly pause onboarding new partners and, in some cases, freeze growth or terminate existing programs while they remediate — and you inherit that disruption regardless of how well-run your own company is.
- Skipping the stability questions (5–8): A widely reported 2024 collapse of a banking-as-a-service ledger provider left end users at multiple fintech apps unable to access their own money for months, because no single system of record could reconcile what the middleware layer said against what the underlying banks actually held. The lesson isn't "avoid middleware" — it's that question 7, on who holds the ledger of record and how reconciliation is verified, is not optional diligence.
- Skipping the integration questions (9–12): Founders routinely sign based on a sandbox demo and a best-case timeline, then discover that real KYC vendors, real card-network rules, and real risk controls stretch the actual integration to several times the length they budgeted for — burning runway and pushing back a launch date that was already promised to investors.
- Skipping the pricing questions (13–16): A fee schedule that looked simple in the sales deck reveals unexplained per-account or per-transaction line items once volume actually scales, turning a unit-economics model that worked on paper into one that doesn't survive contact with real usage.
- Skipping the termination questions (17–20): Reserve requirements that seemed reasonable at signing can be raised unilaterally mid-dispute, freezing working capital at the exact moment you need it most. And an offboarding with no defined process can leave customer funds in limbo for weeks or months — the same pattern that made the 2024 middleware collapse a crisis for end users rather than an inconvenience.
Key Takeaways
- Five areas cover the real risk: compliance program strength, program stability, integration timeline, pricing, and termination/reserve terms. A weak answer in any one is disqualifying on its own.
- Get answers in writing, not on a call. A verbal answer that sounds confident and a written answer that says the same thing are not the same commitment.
- The ledger-of-record question matters more than it sounds. When a BaaS middleware layer sits between you and the chartered bank, knowing who reconciles what — and how — is the single question most likely to matter in a crisis.
- Sandbox timelines are not production timelines. Ask what specifically changes between the two, not just how long the sandbox took to stand up.
- Reserve and termination terms deserve as much scrutiny as pricing. They rarely get equal attention during a sales process, and they're the terms that bind you hardest when a relationship goes wrong.
- A reference from someone who left is worth more than one from someone who stayed. Ask for it directly, and treat hesitation as an answer.
Frequently Asked Questions
How long should partner bank due diligence actually take?
Long enough to get every answer in this checklist in writing, which for most founders means several weeks of parallel conversations with multiple finalists rather than a single call with one candidate. Compressing it to save time is the most common way founders end up locked into terms they didn't fully understand until a dispute forced them to reread the contract.
Is a BaaS provider the same thing as a sponsor bank?
No — a BaaS provider is typically a middleware layer that sits between your product and one or more chartered banks, handling technical integration and sometimes program management, while the sponsor bank is the regulated institution actually holding the charter your program operates under. Some programs work directly with a bank; others work through a BaaS provider that has its own bank relationships. Question 7 above exists specifically because that distinction matters for who holds the ledger of record.
What's a reasonable reserve requirement for an early-stage fintech program?
There's no single reasonable figure — it depends on your transaction volume, risk profile, and the specific bank's own risk appetite, which is exactly why question 18 asks for the actual conditions under which the reserve can be increased rather than accepting a number at face value. Treat any reserve figure quoted without those conditions attached as an incomplete answer.
Should I get my own money transmitter license instead of using a partner bank?
That's a separate decision from this checklist, and it depends on your product's control needs, margin, and timeline — not on how well or poorly any single partner bank answers these questions. If you haven't worked through that tradeoff yet, our comparison of a bank-partnership path against pursuing your own license is the place to start before you finalize a partner-bank decision either way.