Reference Data

Customer Reference Data Management

sd-customer-reference-data-management · bian-reference-data

A BIAN service domain in Reference Data. It applies the Maintain functional pattern to the Customer Reference Data, with the Customer Reference Data Maintenance Agreement as its control record — one independent Spring Boot microservice on the platform's Cilium eBPF mesh.

View repository ↗The 162-domain platform ↗

Business DomainReference Data

Functional PatternMaintain

Asset TypeCustomer Reference Data

Control RecordCustomer Reference Data Maintenance Agreement

USEWhat it is used for

Representative use cases for the Customer Reference Data Management service domain within a BIAN-aligned core-banking landscape.

Serve golden-source Customer Reference Data data to every other service domain with full audit history
Synchronize Customer Reference Data Management records bi-directionally with the core banking system of record
Provide point-in-time lookups for regulatory reporting and reconciliation

APIBIAN semantic API

The control record (Customer Reference Data Maintenance Agreement) 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/customer-reference-data-maintenance-agreement/initiate`	Initiate
GET	`/v1/customer-reference-data-maintenance-agreement/{crId}/retrieve`	Retrieve
PUT	`/v1/customer-reference-data-maintenance-agreement/{crId}/update`	Update
PUT	`/v1/customer-reference-data-maintenance-agreement/{crId}/control`	Control (suspend / resume / terminate)

INTBackend integrations

The systems and standards a real deployment of Customer Reference Data Management would transact with.

Core banking: Temenos Transact, Infosys Finacle, Mambu, Thought Machine Vault
Market data: Refinitiv/LSEG, Bloomberg, SIX Financial
Registries & identity: GLEIF (LEI), SWIFTRef, national ID/address validators (DigiLocker, Loqate)

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-customer-reference-data-management
mvn -f sd-customer-reference-data-management spring-boot:run
curl localhost:8080/v1/service-domain

# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-customer-reference-data-management ./helm -n bian-reference-data

FAQQuestions

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. Customer Reference Data Management is the service domain for Reference Data; it manages the Customer Reference Data Maintenance Agreement and exposes it through standard BIAN action terms.

What business area does Customer Reference Data Management belong to?

Customer Reference Data Management sits in the Reference Data business area — the golden-source reference-data backbone that every other service domain reads from. It runs in the bian-reference-data namespace as one independent Spring Boot microservice.

Is Customer Reference Data 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.