BaaS Providers Compared (2026)
Updated: September 16, 2026
Key Takeaways
- The April 2024 collapse of Synapse Financial froze $160-200M in customer funds, triggering a complete regulatory recalibration of the BaaS industry.
- BaaS 2.0 is defined by direct bank-fintech partnerships, daily reconciliation, and bank-owned accountability - the middleware-heavy model is largely abandoned.
- The BaaS market has diverged into distinct provider categories: single-function APIs, bank-led platforms, and multi-product infrastructure.
- March 2025 joint guidance from the FDIC, OCC, and Federal Reserve holds banks fully accountable for all third-party partner actions.
- Provider evaluation after Synapse requires scrutiny of regulatory structure, reconciliation capabilities, product breadth, and sponsor bank stability.
Choosing a Banking as a Service provider in 2026 is a fundamentally different exercise than it was two years ago. The April 2024 Synapse Financial collapse exposed structural failures in the middleware-heavy BaaS model, triggered regulatory action across the U.S. banking system, and forced fintechs to reassess how they evaluate infrastructure partners. For a foundational overview of the BaaS model - how it works, the value chain, use cases, and regulatory compliance - see our complete guide to Banking as a Service.
This article compares the major BaaS providers by model type, jurisdictional coverage, and capabilities, and examines what the post-Synapse regulatory environment means for platform evaluation.
Contents
- The Synapse Collapse: A Watershed Moment
- BaaS 1.0 vs BaaS 2.0
- BaaS Platform Landscape: Providers Compared
- How to Evaluate a BaaS Provider After Synapse
- What Drives BaaS Demand in 2026?
- Where Aerapass Fits in the Provider Landscape
- Frequently Asked Questions
The Synapse Collapse: A Watershed Moment
The April 2024 bankruptcy of Synapse Financial Technologies marked a watershed moment for Banking as a Service. Synapse, a technology middleware provider connecting fintech apps to FDIC-insured banks through omnibus (“For Benefit Of”) accounts, collapsed after failing to reconcile customer balances across multiple partner banks.
Over 100,000 customers found their accounts frozen, with between $160 million and $200 million in deposits locked away. The trustee overseeing the bankruptcy estimated a permanent shortfall of $65 million to $95 million in missing customer funds. The collapse exposed a critical structural flaw in what is now called BaaS 1.0: regulatory ambiguity around accountability.
The fallout was swift. The Federal Reserve Board issued a cease-and-desist order to Evolve Bank & Trust for failing to maintain effective risk management of its fintech partnerships. The FDIC proposed a recordkeeping rule mandating daily reconciliation of customer deposits. And a March 2025 joint statement from the FDIC, OCC, and Federal Reserve explicitly declared that banks cannot outsource compliance and must maintain independent verification of all customer funds.
For fintechs evaluating BaaS providers today, Synapse is the reference case. Every evaluation question - about reconciliation, regulatory structure, fund custody, and accountability - traces back to what went wrong here.
BaaS 1.0 vs BaaS 2.0
The Synapse collapse did not just disrupt one company. It forced a structural shift in how the entire BaaS model operates.
| Dimension | BaaS 1.0 (Pre-2024) | BaaS 2.0 (2025+) | Source |
|---|---|---|---|
| Model Structure | Middleware-heavy tri-party: Bank to Middleware to Fintech | Direct bank-fintech partnerships; middleware optional | American Banker |
| Regulatory Accountability | Ambiguous; compliance diffused across layers | Bank is fully accountable; cannot outsource compliance | FDIC/OCC/Fed Joint Statement (Mar 2025) |
| Ledger Reconciliation | Daily reconciliation optional; middleware held records | Daily reconciliation mandatory; bank verifies independently | FDIC Recordkeeping Proposal (2024) |
| Fund Custody | Omnibus (FBO) accounts with middleware abstraction | Transparent account structure; bank maintains individual customer records | Federal Reserve (Evolve order) |
| Risk Management | Minimal third-party vendor oversight | Robust risk framework; independent testing, BSA/AML monitoring | OCC/FDIC Enforcement Actions (2024-2025) |
| Technology Approach | Plug-and-play API abstraction | End-to-end cash visibility; compliance-first infrastructure | JP Morgan Insights, SDK.finance |
Sources: American Banker, FDIC, OCC, Federal Reserve, JP Morgan Payments Insights.
The shift from BaaS 1.0 to 2.0 is not cosmetic. It changes which providers are viable, which partnership structures are acceptable to regulators, and what due diligence fintechs must conduct before selecting a platform.
BaaS Platform Landscape: Providers Compared
The BaaS market has diverged into distinct platform categories since the Synapse collapse. Choosing the right infrastructure partner depends on whether a business needs single-function APIs, bank-sponsored programme management, or a multi-product platform that combines payments, trading, and wealth management under one integration.
| Provider | Model | Core Capabilities | Jurisdictions | Multi-Asset | White-Label | Post-Synapse Compliance |
|---|---|---|---|---|---|---|
| Galileo (SoFi) | Card + payments API | Card issuing, payment processing, account management | US-centric | No | Limited | Bank-dependent |
| Marqeta | Card issuing platform | Modern card issuing, tokenisation, just-in-time funding | US, EU | No | Yes (cards) | Bank-dependent |
| Solarisbank | Bank-led BaaS | Full banking licence, accounts, cards, lending | EU (German licence) | No | Yes | Direct (licence holder) |
| Unit | Embedded finance API | Accounts, cards, payments, lending (via partner banks) | US | No | Yes | Bank-partnership model |
| Railsr | Modular BaaS | Cards, accounts, FX, compliance modules | UK, EU | Limited | Yes | Bank-partnership model |
| Aerapass | Multi-product infrastructure | Payments, multi-asset exchange, wealth management, card issuance, customer management | HK, SG, AU, CA | Yes (FX, crypto, commodities, precious metals) | Yes (full platform) | Direct (regulated in 4 jurisdictions) |
Comparison based on publicly available information as of September 2026. Capabilities vary by client arrangement and jurisdiction.
Provider Model Types
Single-function API providers focus on one capability (typically card issuance or payments) with high reliability and deep feature sets within that domain. Galileo and Marqeta are the leading examples. They work best for fintechs with a narrow product scope that can manage multiple vendor integrations for additional capabilities. The trade-off is depth within one domain versus the operational overhead of stitching together multiple providers for a full product suite.
Bank-led BaaS involves a licensed bank offering its own infrastructure directly through APIs. Solarisbank in the EU is the primary example. The regulatory structure is unambiguous - the bank holds the licence and controls everything - which addresses the core accountability gap that Synapse exposed. However, coverage is limited to the bank’s own jurisdiction and product set.
Multi-product infrastructure platforms combine multiple financial capabilities under one API layer, typically operating across several jurisdictions. This model reduces vendor management complexity and enables cross-product workflows - a customer onboarded for payments can immediately access trading or card products without a separate integration. The trade-off is a larger integration surface and dependency on a single platform for multiple product lines.
How to Evaluate a BaaS Provider After Synapse
The Synapse collapse introduced five evaluation criteria that did not exist - or were not enforced - before 2024.
1. Regulatory structure transparency. Ask: is the bank directly accountable for all products issued under its licence, or is there a middleware layer abstracting regulatory responsibility? The FDIC/OCC/Fed joint statement makes clear that banks cannot outsource compliance - but some legacy BaaS arrangements still operate with ambiguous accountability. Request a written regulatory responsibility matrix before proceeding.
2. Reconciliation capabilities. Verify that the platform supports daily reconciliation of customer deposits with the sponsor bank independently verifying balances. Synapse failed because reconciliation was optional and middleware-controlled. Post-Synapse, daily reconciliation is not a feature - it is a regulatory expectation.
3. Fund custody model. Understand how customer funds are held. Omnibus (FBO) accounts with middleware-managed records were the structural failure point at Synapse. Transparent account structures where the bank maintains individual customer records reduce the risk of shortfalls during a disruption.
4. Sponsor bank stability. Research the sponsor bank’s regulatory standing, financial health, and BaaS partnership history. A bank under a consent order or regulatory scrutiny may restrict or terminate its BaaS programme, leaving fintechs without infrastructure. Check recent enforcement actions through the FDIC, OCC, and relevant regional regulators.
5. Product breadth vs single-vendor risk. Multi-product platforms reduce integration complexity but increase concentration risk. Single-function providers spread risk across vendors but create operational overhead. The right balance depends on the fintech’s engineering capacity, product roadmap, and risk tolerance. For a deeper analysis of this trade-off, see the build vs buy decision framework for fintechs.
Comparing BaaS providers for your product roadmap? See how Aerapass combines payments, trading, cards, and compliance under one API layer - with direct regulatory coverage across four jurisdictions. Explore the platform
What Drives BaaS Demand in 2026?
Despite the regulatory turbulence, demand for BaaS infrastructure is accelerating. The drivers are structural, not cyclical.
Digital-native consumer expectations. Among Gen Z, 89% bank via mobile, 72% prefer app-based account opening over visiting a branch, and 82% say they would switch banks for better digital services (Deloitte, Bankrate, Mastercard). Millennials show similar patterns. These cohorts expect financial services embedded in the apps they already use - not accessed through separate banking interfaces.
Enterprise embedded finance. Non-financial companies are embedding financial products into their core offerings: ride-sharing apps offering driver payouts, e-commerce platforms providing checkout financing, SaaS tools embedding invoice payments. Each of these use cases runs on BaaS infrastructure. For how BaaS and embedded finance relate, see What Is Banking as a Service?.
Regulatory modernization in Asia-Pacific. Singapore’s MAS FinTech Regulatory Sandbox, Hong Kong’s virtual banking licenses, and Australia’s Consumer Data Right framework create favorable conditions for BaaS adoption. The region’s approach to fintech regulation is accelerating bank-fintech partnerships rather than constraining them.
Where Aerapass Fits in the Provider Landscape
Aerapass operates in the multi-product infrastructure category. The platform consolidates payments, multi-asset exchange (FX, crypto, commodities, precious metals), card issuance, customer management (KYC/AML/compliance), and wealth management infrastructure through a single API layer across four regulated jurisdictions.
Three characteristics position Aerapass relative to the other provider types in the comparison above:
- Multi-jurisdiction coverage. Regulated across Hong Kong, Singapore, Australia, and Canada under the supervision of MAS, SFC/HKMA, ASIC, and FINTRAC. A single integration provides access to regulated infrastructure across four markets without requiring separate banking partners in each region
- Compliance-first architecture. KYC verification, AML screening, transaction monitoring, and regulatory reporting are built into the platform rather than sourced from third-party integrations. This addresses the post-Synapse requirement for end-to-end compliance visibility
- Multi-asset capability. Fintechs building multi-product offerings - combining payments with trading, cards with wealth management - avoid the complexity of integrating separate providers for each capability
The platform manages over 100,000 users across 120+ countries. For a full overview of how the BaaS model works - value chain, use cases, and regulatory compliance - see What Is Banking as a Service? The Definitive Guide. For the technical approach to third-party integration, see how Aerapass enables API-first financial infrastructure.
Frequently Asked Questions
What changed about BaaS provider evaluation after the Synapse collapse?
Five evaluation criteria became non-negotiable: regulatory structure transparency (is the bank directly accountable?), daily reconciliation capabilities (does the bank independently verify balances?), fund custody model (are customer funds held in transparent account structures?), sponsor bank stability (is the bank under regulatory pressure?), and product breadth versus single-vendor risk. Before Synapse, many of these were optional. After the FDIC/OCC/Federal Reserve joint statement in March 2025, they are regulatory expectations.
Which BaaS providers are regulated in multiple jurisdictions?
Most BaaS providers operate under a single jurisdiction’s licence or rely on a sponsor bank’s regulatory coverage. Solarisbank holds a German banking licence covering the EU. Unit and Galileo operate through US partner banks. Aerapass is directly regulated across four jurisdictions - Hong Kong, Singapore, Australia, and Canada - enabling multi-market deployment without requiring separate banking partners in each region.
What is the difference between single-function and multi-product BaaS?
Single-function providers like Galileo and Marqeta focus on one capability (card issuance, payments) with deep feature sets in that domain. Multi-product platforms combine payments, trading, cards, compliance, and wealth management under one API layer. Single-function providers require the fintech to integrate and manage multiple vendors for a full product suite. Multi-product platforms reduce vendor complexity but increase concentration risk on a single provider. The right choice depends on the fintech’s product roadmap and engineering capacity.
How long does it take to launch on a BaaS platform?
Simple card programmes on single-function APIs can go live in weeks. Full white-label banking products involving multi-jurisdictional compliance, custom onboarding flows, and integrated wealth or trading features typically require 8-16 weeks of integration and testing. Post-Synapse, banks require more rigorous due diligence before approving new fintech partnerships, and daily reconciliation testing is mandatory before launch.
Is it safer to use a bank-led BaaS provider than a middleware provider?
Bank-led providers like Solarisbank offer clearer regulatory accountability because the bank controls the entire stack. Middleware providers introduce an additional layer where accountability can become ambiguous - the core issue in the Synapse failure. However, bank-led providers are typically limited to a single jurisdiction and a narrower product set. The safety advantage must be weighed against coverage and capability requirements.
Ready to shortlist your BaaS partner? See how Aerapass handles sponsor bank governance, daily reconciliation, and multi-product delivery across four regulated jurisdictions. Explore Aerapass for fintechs
Regulatory Disclosure: Aerapass financial services are provided through Aerapass, a Major Payment Institution licensed by the Monetary Authority of Singapore and regulated across four jurisdictions (Hong Kong, Singapore, Australia, and Canada). This article is for educational purposes only and does not constitute financial, legal, or regulatory advice. Provider capabilities described are based on publicly available information as of September 2026. Companies evaluating BaaS providers should conduct independent due diligence and consult qualified advisors.
Sources cited: American Banker, FDIC/OCC/Federal Reserve Joint Statements (2024-2025), JP Morgan Payments Insights, SDK.finance, Deloitte Digital Banking Report, Bankrate, Mastercard Gen Z Banking Report.
The content on this page is produced by Aerapass for general informational purposes only and does not constitute financial advice, investment advice, or any other form of professional advice. Aerapass is a technology platform provider serving financial institutions, wealth managers, and fintech companies. Before making any financial decision, you should consult with a qualified, licensed financial advisor who can take your individual objectives and circumstances into account.
