Operations and Execution
Correspondent Bank Management
sd-correspondent-bank-management · bian-operations
A BIAN service domain in Operations and Execution. It applies the Manage functional pattern to the Correspondent Arrangement, with the Correspondent Arrangement Management Plan as its control record — one independent Spring Boot microservice on the platform's Cilium eBPF mesh.
View repository ↗The 162-domain platform ↗
Business DomainPayments
Functional PatternManage
Asset TypeCorrespondent Arrangement
Control RecordCorrespondent Arrangement Management Plan
USEWhat it is used for
Representative use cases for the Correspondent Bank Management service domain within a BIAN-aligned core-banking landscape.
- Accept, validate, and route Correspondent Arrangement instructions to the correct rail
- Execute transfers with debit/credit atomicity and compensation on failure
- Provide payment status tracking to channels and corporate clients (gpi-style)
- Screen instructions against sanctions lists before release
APIBIAN semantic API
The control record (Correspondent Arrangement Management Plan) is exposed through uniform BIAN action terms. Java 21 · Spring Boot 3, OpenAPI at /swagger-ui.html, health at /actuator/health.
| Method | Path | BIAN action |
|---|
| GET | /v1/service-domain | Service metadata |
| POST | /v1/correspondent-arrangement-management-plan/initiate | Initiate |
| GET | /v1/correspondent-arrangement-management-plan/{crId}/retrieve | Retrieve |
| PUT | /v1/correspondent-arrangement-management-plan/{crId}/update | Update |
| PUT | /v1/correspondent-arrangement-management-plan/{crId}/control | Control (suspend / resume / terminate) |
INTBackend integrations
The systems and standards a real deployment of Correspondent Bank Management would transact with.
- Rails: SWIFT, SEPA, ACH/NACHA, UPI (NPCI), NEFT/RTGS/IMPS, FedNow, TARGET2
- Payment hubs: Volante, ACI Worldwide, FIS, Finastra
- Sanctions screening: Fircosoft, LexisNexis Bridger
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-correspondent-bank-management
mvn -f sd-correspondent-bank-management spring-boot:run
curl localhost:8080/v1/service-domain
# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-correspondent-bank-management ./helm -n bian-operations
FAQQuestions
What is the BIAN “Manage” functional pattern?
A Manage service domain plans, coordinates and oversees a resource or activity across its lifecycle. Correspondent Bank Management applies it to the Correspondent Arrangement.
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. Correspondent Bank Management is the service domain for Payments; it manages the Correspondent Arrangement Management Plan and exposes it through standard BIAN action terms.
What business area does Correspondent Bank Management belong to?
Correspondent Bank Management 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 Correspondent Bank Management 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
Correspondent Bank Management is one of 162 BIAN service domains on the platform. Explore the rest: