gitwtfhub

wtf is neobank-primitives?

andry-lebedev/neobank-primitives — explained in plain English

Analysis updated 2026-05-18

174TypeScriptAudience · developerComplexity · 3/5Setup · easy

TL;DR

A starter neobank app and framework for building fintech tools that AI agents can safely use, with a policy engine and human approval built into the design.

Mindmap

mindmap
  root((Neobank Primitives))
    What it does
      Interactive demo neobank
      Agent safe financial primitives
      Policy controlled autonomy
    Tech stack
      TypeScript
      React
      Swipelux adapter
    Use cases
      Fintech app starting point
      AI agent payment tools
      Policy gated transactions
    Audience
      Developers
      Fintech builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Explore a working demo of a neobank app with accounts, deposits, payouts, and transfers.

REASON 2

Prototype giving an AI agent narrowly scoped, policy checked financial tools instead of an open payment API.

REASON 3

Use the identity, account, and transaction primitives as a base for a fintech product.

REASON 4

Connect a sandbox Swipelux account to move the demo from mock data to a real adapter.

What's in the stack?

TypeScriptReact

How it stacks up

andry-lebedev/neobank-primitivesbytedoger/awesome-openpricemattpocock/sextant
Stars174173173
LanguageTypeScriptTypeScriptTypeScript
Last pushed2020-11-25
MaintenanceDormant
Setup difficultyeasymoderateeasy
Complexity3/53/5
Audiencedevelopergeneralpm founder

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 30min

Demo mode needs no credentials, connecting the live Swipelux adapter requires your own sandbox API key.

Wtf does this do

Neobank Primitives is a starter project for building fintech applications, with a particular focus on making them safe for AI agents to operate, not just people. It works today as a fully interactive demo neobank you can click through with realistic sample data, covering personal and business accounts, identity onboarding, deposits, payouts, and wallet transfers. The bigger pieces the project is building toward, a policy engine, a standalone SDK, and a full set of business verification tools, are described in the README but are not yet shipped as something you could run in production. The idea behind the project is that handing an AI agent an open ended payment API is risky, so instead it wants to give agents narrow, well defined tools for things like getting a payout quote or checking an account balance, with a policy engine sitting between the agent's request and the money actually moving. Every operation is meant to follow the same steps: validate the request, check it against policy rules, get authorization, execute it, normalize the result, and record it for audit. Depending on the policy, an operation might run automatically or pause and wait for a human to approve it, for example the first time money is sent to a new recipient. The repository is built with TypeScript and React. Financial primitives like accounts, transactions, and identity are kept provider neutral, meaning they are not tied to one specific banking backend, and the project currently ships one working integration with a company called Swipelux as a sandbox example, with more providers planned later. To run it locally you clone the repository, install dependencies with npm, and start the dev server, no environment file or API keys are needed to use the demo mode. If you want to connect the live Swipelux integration, you provide your own sandbox API key inside the running app, which is kept in the browser session. The README does not state a license for the project.

Yoink these prompts

Prompt 1
Help me clone and run the Neobank Primitives demo locally with npm.
Prompt 2
Explain how the policy engine in Neobank Primitives decides when a transaction needs human approval.
Prompt 3
Show me how to connect a Swipelux sandbox API key to move from demo mode to the live adapter.
Prompt 4
Walk me through the primitive surface for identity, accounts, and transactions in this project.

Frequently asked questions

wtf is neobank-primitives?

A starter neobank app and framework for building fintech tools that AI agents can safely use, with a policy engine and human approval built into the design.

What language is neobank-primitives written in?

Mainly TypeScript. The stack also includes TypeScript, React.

How hard is neobank-primitives to set up?

Setup difficulty is rated easy, with roughly 30min to a first successful run.

Who is neobank-primitives for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.