▚ BIAN PLATFORM
CatalogRunFAQRepo ↗

Operations and Execution

Transaction Engine

sd-transaction-engine · bian-operations

A BIAN service domain in Operations and Execution. It applies the Operate functional pattern to the Transaction Ledger, with the Transaction Ledger Operating Session as its control record — one independent Spring Boot microservice on the platform's Cilium eBPF mesh.

View repository ↗The 162-domain platform ↗

Business DomainOperations
Functional PatternOperate
Asset TypeTransaction Ledger
Control RecordTransaction Ledger Operating Session

USEWhat it is used for

Representative use cases for the Transaction Engine service domain within a BIAN-aligned core-banking landscape.

APIBIAN semantic API

The control record (Transaction Ledger Operating Session) is exposed through uniform BIAN action terms. Java 21 · Spring Boot 3, OpenAPI at /swagger-ui.html, health at /actuator/health.

MethodPathBIAN action
GET/v1/service-domainService metadata
POST/v1/transaction-ledger-operating-session/initiateInitiate
GET/v1/transaction-ledger-operating-session/{crId}/retrieveRetrieve
PUT/v1/transaction-ledger-operating-session/{crId}/updateUpdate
PUT/v1/transaction-ledger-operating-session/{crId}/controlControl (suspend / resume / terminate)

INTBackend integrations

The systems and standards a real deployment of Transaction Engine would transact with.

RUNRun it yourself

Each service domain is its own standalone Spring Boot repository — clone and run in seconds, or deploy onto Kubernetes with the bundled Helm chart behind the Cilium mesh.

# run this service domain standalone
git clone https://github.com/Sreenivas-Sadhu-Prabhakara/sd-transaction-engine
mvn -f sd-transaction-engine spring-boot:run
curl localhost:8080/v1/service-domain

# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-transaction-engine ./helm -n bian-operations

FAQQuestions

What is the BIAN “Operate” functional pattern?
An Operate service domain keeps a piece of operational or technical capability running day to day. Transaction Engine applies it to the Transaction Ledger.
What is a BIAN service domain?
BIAN (the Banking Industry Architecture Network) decomposes a bank into independent service domains, each owning exactly one business capability. Transaction Engine is the service domain for Operations; it manages the Transaction Ledger Operating Session and exposes it through standard BIAN action terms.
What business area does Transaction Engine belong to?
Transaction Engine sits in the Operations and Execution business area — the operational core that executes payments, positions, settlements and transactions. It runs in the bian-operations namespace as one independent Spring Boot microservice.
Is Transaction Engine production-ready?
It is an educational reference implementation: a real BIAN REST API over an in-memory store, ready to be filled with domain logic. It is not a live bank and is not affiliated with BIAN.

SEEIn the landscape

Transaction Engine is one of 162 BIAN service domains on the platform. Explore the rest:

▚ Platform overview The Master Catalog (162 domains) This repository ↗