Adviser Hub CloudEnterprise Wealth Tech
Implementation Guide

Eight Banking-as-a-Service Red Flags Partner Banks and Fintechs Miss

Most BaaS failures trace back to gaps that were visible at signing. Here are eight red flags, each paired with the control or contract clause to demand before go-live.

By the Adviser Hub Cloud editorial team · November 2026 · 7 min read

Why the Contract Matters More Than the Demo

If you're about to sign a sponsor bank agreement or a middleware contract, the demo tells you little about a banking as a service platform. What matters is whether you could prove, on any given morning, who owns every unit of currency in the pooled account, and who answers to the regulator when something breaks.

The 2024 collapse of US middleware provider Synapse showed how badly this can go. End users of several fintech apps had funds frozen for months while banks, the middleware and the fintechs disputed whose records were right. Since then, US supervisors have issued a run of enforcement actions against sponsor banks over weak oversight of fintech partners. The UK has moved to tighten safeguarding rules for payment and e-money firms, and the EU's Digital Operational Resilience Act (DORA) has made third-party technology risk a management-body responsibility.

Advertisement

The eight red flags below recur in BaaS due diligence. They apply whether you're the bank or the fintech, and each comes with the control or clause to ask for instead.

Ledger Gaps That Hide Shortfalls Until It's Too Late

Red flag 1: the middleware holds the only ledger of end-user balances. The bank sees one pooled for-benefit-of (FBO) or client money account. The fintech sees app balances. Only the middleware knows how the two connect. If that provider fails, nobody can quickly work out who is owed what.

Demand instead: a contractual right for the bank to receive a daily, account-level copy of the sub-ledger in a defined format, and the ability to rebuild balances without the middleware's help. Some banks now run their own sub-ledger and treat the middleware purely as orchestration. Above a few thousand accounts, that's the design to insist on, because manual reconstruction stops being realistic at that scale.

Red flag 2: reconciliation is monthly, or breaks get waved off as "timing differences." A break left open for 30 days is a shortfall you haven't measured yet.

Demand instead: daily three-way reconciliation between the bank's core balance, the middleware ledger and the fintech ledger. Put aging thresholds in writing, for example escalation to named owners after two business days and to senior management after five. The contract should also name who funds any shortfall, and by when.

Compliance Ownership That Only Exists in a Slide Deck

Red flag 3: nobody can show you a signed responsibility matrix. Fintechs often assume the bank "handles compliance." Banks often assume the fintech's onboarding vendor screens customers properly. Regulators accept neither assumption. The US interagency third-party risk guidance, the EBA's outsourcing guidelines in Europe, the Reserve Bank of India's digital lending rules and the Monetary Authority of Singapore's outsourcing expectations share one principle: the licensed institution stays accountable for what its partners do.

Demand instead: a responsibility schedule attached to the contract, built at control level rather than function level. It should cover:

  • Customer identification and beneficial ownership checks
  • Sanctions screening and rescreening frequency
  • Transaction monitoring rules, alert review SLAs and who decides on suspicious activity reports
  • Complaints, disputes and chargeback timelines
  • Pre-approval of marketing, disclosures and fee changes

Any change to the schedule should need written sign-off from both parties. Sound embedded finance compliance means every control has one named owner and one named checker.

Concentration Risk and Exit Plans Nobody Has Tested

Red flag 4: one side depends heavily on the other. Sponsor bank risk climbs when a handful of fintech programs supply a large share of a bank's deposits or fee income. That money can leave fast, and one partner's compliance failure can draw scrutiny onto the whole bank. The fintech is just as exposed if it relies on a single bank and a single middleware provider with no fallback.

Demand instead: banks should set concentration limits per program and per middleware provider, and report against them to the board. Fintechs operating in more than one market should line up a second sponsor or licensed partner within 12 to 24 months of launch.

Red flag 5: the exit clause stops at "reasonable transition assistance." That wording doesn't move a single account.

Demand instead: a notice period of 90 to 180 days; a defined export format covering balances, transaction history, KYC records and consent records; and a migration runbook tested annually. The provider must keep services running through wind-down, even while fees are in dispute.

Audit Rights and the Open Banking API Layer

Red flag 6: you can audit the provider but not its subcontractors. A typical BaaS stack includes card processors, KYC vendors, cloud hosting and often an open banking API platform for account aggregation or payment initiation. Each is a fourth party. DORA expects EU financial entities to map these dependencies, and supervisors elsewhere are heading the same way.

Demand instead: audit and information rights that flow down to critical subcontractors, plus advance notice before any of them is replaced. For the API layer, also ask for:

  • Exportable consent logs showing when each consent was granted, renewed and revoked
  • An API versioning policy with at least six months' deprecation notice
  • Uptime SLAs backed by service credits, and incident notification within hours, not days

Open banking rules differ by market. The UK's Open Banking standard, Brazil's Open Finance, India's Account Aggregator framework and the EU's payment services rules (now being overhauled) each set their own permissions and consent requirements. Confirm the platform holds the right authorizations in every country where you'll use it.

Growth That Outruns Controls, and Fuzzy Protection Claims

Red flag 7: no limits on onboarding volume. Published enforcement actions against sponsor banks often describe the same pattern: account growth outpaced monitoring capacity, and alert backlogs built up for months.

Demand instead: volume caps in the program agreement covering accounts opened per month, total balances and transaction value. Each increase should depend on measured control health: alert backlog, reconciliation break aging and complaint volumes.

Red flag 8: marketing blurs what protection end users actually have. Protection rules vary widely. In the US, pass-through deposit insurance depends on accurate records of who owns what. In the UK and EU, e-money is safeguarded but generally isn't covered by deposit guarantee schemes. Other markets set their own coverage limits and eligibility rules.

Demand instead: bank pre-approval of any wording about protection, insurance or safeguarding, and plain-language disclosures naming the licensed entity that holds the funds.

A 30-Day Due Diligence Sequence Before You Sign

Red flagControl to demandContract clause
Single middleware ledgerDaily sub-ledger copy held by the bankData delivery and reconstruction rights
Slow reconciliationDaily three-way reconciliationBreak aging, escalation, shortfall funding
Unclear compliance ownershipControl-level responsibility matrixResponsibility schedule with change control
ConcentrationPer-program and per-provider limitsReporting and limit triggers
Weak exitTested migration runbookNotice period, export format, continuity
No fourth-party visibilitySubcontractor mapFlow-down audit rights, change notice
Uncapped growthControl-health metricsVolume caps tied to metrics
Misleading protection claimsMarketing reviewPre-approval and disclosure requirements

Work through it in order. Week one: obtain the subcontractor map and responsibility matrix. Week two: run a test reconciliation on a sample day of real data. Week three: review the exit runbook. Week four: negotiate the clauses, using what the first three weeks exposed as leverage.

An independent review of reconciliation and compliance controls typically runs USD 30,000 to 150,000 depending on scope and region. That's an indicative 2026 market range that varies by contract and provider, so get quotes. Have qualified legal counsel in your jurisdiction review the agreement itself.

The decision rule: if a banking as a service platform won't commit in writing to daily reconciliation and bank-held ledger data, walk away, however good the pricing looks.

Frequently asked questions

Who is ultimately responsible for compliance in a BaaS partnership?

In most markets, the licensed bank or regulated entity. It can delegate tasks to fintechs or middleware providers, but not accountability. That's why supervisors in the US, Europe, India, Singapore and elsewhere expect the bank to oversee partners' controls directly. A signed, control-level responsibility matrix is the clearest evidence of who does what.

How often should a BaaS program reconcile end-user balances?

Ask for daily, as a three-way match between the bank's core account balance, the middleware ledger and the fintech's ledger, with written aging thresholds and escalation paths for breaks. Programs with heavy real-time payment volumes may also need intraday reconciliation.

What should a BaaS exit clause include?

A notice period, typically 90 to 180 days; a defined export format for balances, transaction history, KYC files and consent records; and a commitment to keep services running during wind-down. Require a migration runbook tested annually, so you know the exit works before you need it.

Does using an open banking API platform add regulatory risk?

It can, because the provider becomes a critical fourth party in your stack. Confirm it holds the right permissions in each market you operate in, that consent records are exportable, and that its uptime and incident notification terms match your own obligations. Requirements differ between the UK, EU, Brazil, India and other regimes.

How much does independent BaaS platform due diligence cost?

A focused independent review of reconciliation, compliance controls and contracts typically costs USD 30,000 to 150,000, driven by scope, program size and region. This is an indicative 2026 market range that varies by provider and contract, so get several quotes and confirm scope in writing.

Written by the Adviser Hub Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.