> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mesh.larkwave.org/llms.txt
> Use this file to discover all available pages before exploring further.

# How Mesh works

> Larkwave's design: where Mesh runs, and how your call reaches the bank's ledger.

Mesh is one part of the Larkwave platform, which gives a bank virtual accounts, wallets and payments without replacing its core banking. Your bank runs Mesh in its own network; Larkwave runs the engines that keep the ledger.

```mermaid theme={null}
flowchart LR
  you["Your servers"] -->|"HTTPS, X-Api-Key"| mesh
  subgraph bank["Your bank's network"]
    mesh["Mesh"] --> plug["Plug"]
    plug --> core["Core banking and NIP"]
    plug -.->|"the bank's copy of the ledger"| ledgerdb[("Ledger")]
  end
  subgraph larkwave["Larkwave"]
    edge["Larkwave Edge"] --> atlas["Atlas: virtual accounts"]
    edge --> purse["Purse: wallets"]
    edge --> trustcore["TrustCore: identity and KYC"]
  end
  plug <-->|"signed and sealed"| edge
  mesh -->|"signed webhooks"| you
```

## The parts

| Part | Runs at | What it does |
| - | - | - |
| **Mesh** | Your bank | The API you call. Works out your business from the key, checks your permissions and your business's features, and sends webhooks. |
| **Plug** | Your bank | The bank's only link to Larkwave. It signs and seals every call, connects to the bank's core banking and NIP, and keeps the bank's own copy of the ledger. |
| **Larkwave Edge** | Larkwave | Checks each Plug's identity and sends each call to the engine that holds what it is about. |
| **Atlas** | Larkwave | The virtual-account engine: account numbers, payments in, charges, and settlement to your account at the bank. |
| **Purse** | Larkwave | The wallet engine: balances, customers' wallets and their KYC tier limits, transfers. |
| **TrustCore** | Larkwave | Businesses, customers and identity checks (BVN, NIN, CAC and more). |

## What this means for you

* **The business comes from the key.** You never send a business id. Another business's customer, account or payment is a `404`, never a `403`, so nobody can probe what exists.
* **Money in.** A payer pays your account number; the bank's rails reach the Plug, Atlas posts the payment with its charges, and Mesh sends you the event. In test mode the sandbox bank plays the payer.
* **Money out.** A transfer leaves through the bank's own rails. Interbank transfers and settlements answer `queued`, and you follow them with their `GET` or the webhook.
* **One ledger, provable.** Every posting is hash-chained to the one before it, and the bank holds its own copy of every transaction and its breakdown.
* **Test and live never mix.** Each bank runs a sandbox Plug next to its live one, with its own sandbox tenant. A test key can never reach real rails.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.