Skip to main content
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.

The parts

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.