> For the complete documentation index, see [llms.txt](https://docs.spendl.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spendl.money/spendl-money-app/spendl-money-overview/b2b-and-b2b2c-architecture.md).

# B2B and B2B2C Architecture

Spendl runs one infrastructure layer for both individual users and the businesses that serve them.

Individuals can use Spendl directly through the Spendl Money App, while businesses can deploy Spendl powered wallets, cards, vouchers, payment flows, and other financial products to their own customers, employees, or user groups.

### One Infrastructure Layer

Spendl does not separate consumer and business use cases into different platforms.

Instead, both operate through different access layers on the same financial infrastructure.

This means the same core system can support individual users, business operations, white label deployments, embedded products, and B2B2C customer experiences.

### How It Can Be Used

<table><thead><tr><th width="293">Use Case</th><th>Description</th></tr></thead><tbody><tr><td>Direct consumer usage</td><td>Individuals use Spendl directly for spending, payments, transfers, vouchers, and supported financial services</td></tr><tr><td>Business powered products</td><td>Businesses offer Spendl powered cards, wallets, vouchers, or payment tools to their own customers</td></tr><tr><td>Embedded services</td><td>Platforms embed Spendl services into their own products and customer journeys</td></tr><tr><td>Enterprise user groups</td><td>Enterprises manage multiple users, teams, customers, or departments under one financial system</td></tr><tr><td>White label deployments</td><td>Businesses launch branded financial experiences powered by Spendl infrastructure</td></tr></tbody></table>

### The App as the Financial OS

The Spendl Money App is more than a dashboard.

It acts as the operating layer for permissions, compliance, money movement, product access, and user interaction.

Every feature created by Spendl flows through this layer. When a new product or service is introduced, it can be made available across both B2B and B2C frameworks in a modular way.

This allows Spendl to expand its product offering without changing how users onboard, access features, or interact with the wider system.

### How the Financial OS Works

<table><thead><tr><th width="243">Layer</th><th>What it controls</th></tr></thead><tbody><tr><td>User access</td><td>Who can access specific products, features, limits, and account types</td></tr><tr><td>Permissions</td><td>What users, businesses, teams, or customer groups are allowed to do</td></tr><tr><td>Compliance</td><td>Verification, monitoring, limits, and approved financial activity</td></tr><tr><td>Money movement</td><td>Transfers, payments, card loading, vouchers, payroll, treasury, and settlements</td></tr><tr><td>Product access</td><td>Which services are available to individuals, businesses, or embedded users</td></tr><tr><td>Reporting</td><td>Visibility over balances, transactions, activity, and operational flows</td></tr></tbody></table>

### Why This Architecture Matters

Spendl’s architecture allows the same infrastructure to serve multiple market needs.

Individuals get direct access to everyday money tools.

Businesses get infrastructure to launch and manage financial products.

Platforms get embedded services without building the regulated backend themselves.

As new services are added, they can be connected into the same system and made available across the relevant access layer.

{% hint style="info" %}
One Platform, Multiple Access Layers

Spendl is designed so individuals, businesses, and B2B2C partners can all operate on the same infrastructure.

* The user experience may change.
* The brand layer may change.
* The underlying system remains connected.
  {% endhint %}