Formance is a highly modular developer platform to build and operate complex money flows of any size and shapes. It comes with several components, that can be used as a whole as the Formance Stack or separately as standalone micro-services and libraries:
- Formance Ledger - Programmable double-entry, immutable source of truth to record internal financial transactions and money movements
- Formance Payments - Unified API and data layer for payments processing
- Formance Numscript - DSL and virtual machine monetary computations and transactions modeling
# macOS
brew tap formancehq/tap
brew install fctl# login to formance cloud fctl login # create a sandbox stack deployment # please note: sandbox are made available for testing and not made for production usage # read more in the docs [1] fctl stack create foobar # commit your first ledger transaction fctl ledger send world foo 100 EUR/2 --ledger=demo # checkout the control dashboard fctl ui
[1] https://docs.formance.com/guides/newSandbox
The Formance Stack is distributed as a collection of binaries, with optional packaging as Docker images and configuration support through command line options and environment variables. The recommended, standard way to deploy the collection of services is to a Kubernetes cluster through our Formance official Helm charts, which repository is available at helm.formance.com.
The full documentation for the formance stack can be found at docs.formance.com
Formance is transitioning to a unified public facing monorepo (this one) that imports versioned services submodules and provides a common infrastructure layer. As we are finalizing this transition, this monorepo is structured as below
The Formance Stack is built on open-source, battle tested technologies including:
- PostgreSQL - Main storage backend
- Kafka/NATS - Cross-services async communication
- Traefik - Main HTTP gateway
just build-openapi composes the component contracts and validates the result.
Ledger V1 and V3 both expose GET /api/ledger/_info with different response
models. Both operations remain in the composed document as
/api/ledger/_info#ledger and /api/ledger/_info#ledgerV3. These are Speakeasy
namespace fragments: generated SDK requests use /api/ledger/_info.
This preserves Ledger.V1.GetInfo and Ledger.V3.Info. V2's separate
/api/ledger/_/info operation remains unchanged. Consumers using other OpenAPI
generators must verify support for namespace fragments.