How Neobank Works
A neobank delivers banking services entirely through software — no branch network, no teller windows, no COBOL-based mainframes. The technology stack is cloud-native by design, which allows neobanks to ship new features, adjust fee structures, and scale across geographies far faster than incumbents. Understanding the mechanics helps merchants and developers assess whether a neobank belongs in their payment and treasury stack.
License or Partnership
The neobank either applies for its own banking license — a full charter or e-money license — or partners with an established regulated institution. Those that use banking-as-a-service providers essentially rent regulated infrastructure: accounts, IBANs, card issuing, and payment rails. The licensing path determines deposit protection, product eligibility, and regulatory obligations.
Cloud-Native Core Banking
Instead of legacy mainframes, neobanks run modern core banking engines such as Thought Machine, Mambu, or proprietary in-house builds. This enables real-time ledgers, programmable accounts, and millisecond-level transaction processing. The architecture also reduces the cost of compliance changes — a regulatory update that takes a traditional bank 18 months to implement can take a neobank weeks.
API-First Product Layer
Every product — cards, accounts, FX conversions, payment initiation — is exposed via REST or GraphQL APIs. This is what makes digital banking integrations accessible to developers building embedded financial products or connecting neobank accounts to automated treasury workflows. Webhooks deliver real-time transaction events without polling.
Mobile-First Onboarding
Account opening uses eKYC (electronic know your customer), biometric identity verification, and document scanning. A business account that takes two to three weeks at a traditional bank can open in under ten minutes on most neobank platforms. This speed advantage is particularly significant for fast-growing ecommerce merchants who need a business account before their first payout cycle.
Revenue Model
Neobanks monetize through interchange fees on card spend, subscription tiers for premium accounts, FX spreads, interest income on deposits, and — increasingly — lending and savings products. B2B neobanks also charge for API access, virtual card programs, and white-label infrastructure. The path to profitability varies significantly: Revolut posted its first annual profit in 2021; most others are still in heavy growth investment.
Why Neobank Matters
The rise of neobanks is not a niche fintech story — it is a structural shift in how financial services are designed, distributed, and accessed. For merchants and payment professionals, the implications reach into settlement accounts, supplier payments, expense management, and multi-currency treasury.
Global market scale: The global neobank market was valued at approximately $66.8 billion in 2023 and is projected to grow at a compound annual growth rate of around 54% through 2030 (Grand View Research, 2024). This growth is driven by smartphone penetration, declining consumer trust in traditional banks following the 2008 financial crisis, and the dramatically lower cost of cloud infrastructure versus physical branch networks.
Customer adoption at scale: By 2024, more than 400 neobanks were operating globally, collectively serving over one billion accounts (Statista, 2024). Revolut surpassed 45 million retail customers; Nubank in Latin America crossed 100 million users, making it one of the largest financial institutions in the region by account count. These are not marginal players — they are mainstream financial infrastructure for hundreds of millions of people.
Business banking momentum: According to Juniper Research, the number of SMEs using neobank business accounts is forecast to exceed 20 million globally by 2026. For payment teams, this matters because neobank business accounts typically offer faster settlement visibility, webhook-based transaction notifications, and direct API access to balance and ledger data — capabilities that legacy bank portals and file-based SFTP exports rarely provide.
Why This Matters for Payment Teams
Neobank accounts are increasingly used as receiving accounts for marketplace payouts, B2B supplier disbursements, and multi-currency treasury operations — especially where API access and settlement speed outweigh the product depth of a traditional bank.
The adoption of open banking standards — PSD2 in Europe, the Consumer Data Right in Australia, Open Banking in the UK — has further accelerated neobank relevance. Neobanks were purpose-built for open banking connectivity. Incumbent banks had to retrofit it onto decades-old systems, with predictably mixed results.
Neobank vs. Challenger Bank
Neobank and challenger bank are terms used almost interchangeably in fintech media, but they describe meaningfully different business models. The clearest distinction is regulatory: whether the institution holds its own full banking license, or operates through a licensed partner.
| Dimension | Neobank | Challenger Bank |
|---|---|---|
| Banking license | Often uses a BaaS partner; may hold e-money license | Typically holds own full banking authorization |
| Physical presence | None | None (rare limited exceptions) |
| Technology stack | Cloud-native, API-first from inception | Modern core; occasionally some legacy debt |
| Product breadth | Focused (accounts, cards, FX, basic payments) | Broader (mortgages, business lending, overdrafts) |
| Deposit protection | Via partner bank or own license; verify the entity | Directly insured as licensed credit institution |
| Typical examples | Chime (US), Wise, N26 | Monzo (UK), Starling Bank, Revolut (post-license) |
| Primary target | Consumer-first, expanding to SMB | Consumer and business, full regulatory depth |
In practice the categories converge over time. Many neobanks pursue their own license as they scale, gradually crossing into challenger bank territory. The distinction matters most when evaluating deposit protection, product eligibility (such as lending), and regulatory obligations for AML and KYC.
See also: challenger bank for a detailed treatment of the licensing and regulatory differences between these categories.
Types of Neobank
Neobank is not a monolithic category — the label covers several meaningfully different business models, target markets, and technology approaches. Identifying the right variant is the first step in evaluating whether a specific neobank fits a merchant's or developer's needs.
Consumer neobanks target retail customers with fee-free current accounts, spending analytics, budgeting tools, and competitive FX rates. Examples include Chime in the US, Monzo in the UK, and N26 across Europe. These products are excellent for individuals but rarely offer the API depth, multi-user access controls, or bulk payment tooling that payment developers require.
B2B and SMB neobanks are purpose-built for businesses. Mercury, Brex, Tide, and Qonto focus on multi-user business accounts, virtual card issuance, automated expense categorization, and integrations with accounting platforms like QuickBooks and Xero. These are the most directly relevant to ecommerce merchants and payment teams.
Vertical neobanks serve a specific industry or demographic — neobanks built for freelancers, for creator economy participants, for agricultural businesses, or for specific geographic markets. They offer deep integrations with sector-specific tooling at the cost of narrower general functionality.
Embedded neobanks are the newest category: companies that are not financial institutions — retailers, HR platforms, logistics providers — that launch banking-like products powered by embedded finance infrastructure. The regulated entity is a licensed BaaS provider operating beneath a branded surface.
Crypto-native neobanks blend traditional account features with cryptocurrency custody, on/off ramp services, and DeFi integrations. Regulatory treatment varies significantly by jurisdiction, and several high-profile examples in this category have faced enforcement actions.
Best Practices
Integrating a neobank effectively — whether as a merchant using one for treasury management or a developer building on top of its APIs — requires deliberate choices rather than simply picking the most-marketed brand. The following guidance applies across the most common use cases.
For Merchants
- Verify deposit protection before committing operational funds. Confirm whether the neobank holds a banking license with deposit insurance (FDIC, FSCS, or equivalent) or routes funds through a partner bank. Know the coverage limit — typically $250,000 in the US or £85,000 in the UK per institution — and distribute balances accordingly.
- Evaluate multi-currency support before selecting a neobank for cross-border payments. Neobanks like Wise Business and Airwallex offer local account numbers in 10–30 currencies with interbank-rate FX; others are effectively single-currency and add significant friction for international operations.
- Map payment rail support to your settlement requirements. Does the neobank support SEPA Instant, SWIFT, Faster Payments, ACH, or BACS? Real-time rails matter for time-sensitive supplier payments or weekly payroll runs. Batch-only rails may introduce one to two business day delays.
- Use neobank virtual cards for SaaS subscriptions and ad spend. B2B neobanks typically offer unlimited virtual card issuance with per-card spend limits. This is a straightforward operational control that prevents vendor overspend without exposing the primary company account.
- Plan for API availability and build alerting. Neobanks are generally more reliable than legacy bank portals, but uptime SLAs vary. Build retry logic and balance-change webhooks into any automated treasury or reconciliation workflow.
For Developers
- Authenticate with OAuth 2.0 and implement token refresh proactively. Most neobank APIs issue short-lived access tokens. Failing to refresh before expiry causes silent failures in production payment flows.
- Use webhooks for real-time transaction events rather than polling balance endpoints. Webhook delivery is faster, more reliable, and cheaper on API rate quotas than repeated GET requests on account balances.
- Test in sandbox before connecting production accounts. Most B2B neobanks — Mercury, Monzo, Starling — provide sandbox environments with synthetic transaction data. Use them fully before any live integration.
- Abstract the neobank behind a service layer in your codebase. Hard-coding to a single neobank's API schema makes provider migration painful. A thin abstraction layer allows you to swap banking providers without rewriting core reconciliation or payout logic.
- Respect PSD2 and open banking consent flows when building on top of regulated account access. Strong customer authentication applies to account information requests and payment initiation — failing to handle SCA redirects correctly is the most common integration failure in European neobank API integrations.
Common Mistakes
Neobanks are operationally simpler than traditional banks in most respects, but certain errors are common even among experienced payment teams. Recognizing these patterns early prevents expensive corrections after a neobank is embedded in a live payment stack.
1. Treating a neobank as a payment processor. Neobanks hold and move money; they do not authorize card-not-present transactions on behalf of merchants. You still need an acquirer or payment gateway to accept payments from your customers. Neobanks sit in the receiving and disbursement layer of the stack, not the acceptance layer.
2. Assuming global payment rail coverage. Many neobanks are licensed in one jurisdiction and rely on correspondent banking relationships for other regions. A European IBAN issued by a neobank may not cleanly receive USD wires, and vice versa. Always test the exact currency, rail, and geographic combination your use case requires before committing to a provider.
3. Ignoring the underlying regulated entity. When a neobank fails, pivots, or exits a market — as several have — the underlying BaaS partner typically ensures fund continuity, but not always seamlessly. Know the legal name of the regulated institution holding your funds, not just the neobank's brand name.
4. Over-concentrating treasury in a single neobank. Deposit insurance limits are per institution. Large operational cash balances above the insured threshold carry unprotected risk in a bank failure scenario. Distribute treasury across multiple institutions and review concentration risk quarterly.
5. Skipping reconciliation automation at launch. Neobank transaction data is clean, structured, and API-accessible — but merchants frequently fail to connect it to their accounting system from day one. Manual month-end reconciliation against high-volume neobank accounts is time-consuming and error-prone. Build or configure automated reconciliation into the initial setup, not as a post-launch cleanup project.
Neobank and Tagada
Neobanks and payment orchestration platforms serve adjacent but distinct layers of the payment stack. Understanding where they intersect helps merchants get maximum value from both.
Tagada operates as a payment orchestration platform, routing transactions across acquirers, PSPs, and payment methods to optimize authorization rates and reduce processing costs. Neobanks, by contrast, manage accounts, hold funds, and move money via banking rails. The two systems complement each other rather than competing.
Where Tagada and Neobanks Intersect
Merchants using Tagada for payment orchestration often connect neobank business accounts as the destination for settlement funds. B2B neobanks with webhook support and structured API transaction data make reconciliation against Tagada's transaction ledger significantly faster than traditional bank statement reconciliation — reducing manual accounting overhead by hours per week at scale.
If your business uses a neobank for multi-currency treasury or B2B supplier disbursements, Tagada's orchestration layer sits upstream — handling routing logic, retry strategies, and acquirer selection — while the neobank manages the downstream banking leg. Settlement flows from Tagada into the neobank's account structure, where API-accessible transaction data enables near-real-time reconciliation without manual file downloads or screen scraping.