Financial workflows without contract code.
Bantu has two categories of programmable functionality. The native protocol layer is the mature and institutionally valuable one: it expresses most regulated financial workflows directly, without requiring the deployment of high-risk custom code.
Most of what a bank needs is already an operation.#
The Bantu operation set publicly documents payments, path payments, offers, trustline operations, authorization, multisignature configuration, claimable balances, sponsorship and account controls. That makes it possible to build a wide range of financial workflows without deploying general-purpose code at all.
Mature, deterministic, and covered by protocol-level testing rather than per-deployment contract audit.
- Asset issuance
- Trustline creation and limits
- Asset-holder authorization
- Trustline freeze and revocation
- Limited authorization
- Optional clawback
- Multisignature thresholds
- Atomic multi-operation transactions
- Path payments and FX routing
- Order-book trading
- Claimable balances
- Sponsored reserves
- Signer management
- Sequence-number controls
- Ledger-linked data entries
- Transaction memos and references
Bantu provides programmable settlement and compliance controls at protocol level, allowing many regulated financial workflows to execute without relying on high-risk custom smart contracts.
- Escrow payments
- Corporate approval chains
- Controlled FX settlement
- Liquidity-routing rules
- Conditional payouts
- Merchant settlement
- Treasury controls
- Whitelisted stablecoin distribution
- Trade-finance disbursement
- Government cash-transfer programmes
- Controlled bond and coupon workflows
Languages and integration stack.#
Bantu integrates through its ledger APIs, transaction envelopes, XDR-compatible transaction model and SDK ecosystem. The public GitHub organisation includes Flutter/Dart, Go and Java SDK repositories, and the developer documentation links JavaScript, Java and Go transaction examples.
Web wallets, Node.js backends, transaction construction, payment applications, dashboards and operational tooling.
Enterprise banking middleware, Android applications, financial-system integration and back-office applications.
High-performance backend services, payment orchestration, API services and infrastructure tooling.
Cross-platform mobile wallets and payment applications.
The Expansion API can be called from Python, PHP, C#, Ruby, Kotlin, Rust or any environment with a standard HTTP client.
The practical stack for a banking system.
For production banking systems the most practical combination is typically the following.
- Java or Kotlin for core-banking and enterprise integration
- Go or Node.js for high-throughput payment and settlement services
- Python for data engineering, reconciliation, risk analytics, reporting and compliance automation
- Flutter for consumer and agent wallets
- REST, event streaming and internal message queues for integration with AML, sanctions, treasury, KYC and core-banking systems
Bring us your control requirements.
Bantu is appropriate for traditional financial institutions because it combines a regulated asset-issuance model with native compliance controls, institutional multisignature governance, real-time settlement, programmable payment flows, FX routing, auditability and federated validator consensus. Put your own requirements against it and tell us where the gaps are.