Sales and Service

Customer Event History

sd-customer-event-history · bian-sales-service

A BIAN service domain in Sales and Service. It applies the Maintain functional pattern to the Customer Event Log, with the Customer Event Log 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 DomainCustomer Management

Functional PatternMaintain

Asset TypeCustomer Event Log

Control RecordCustomer Event Log Maintenance Agreement

USEWhat it is used for

Representative use cases for the Customer Event History service domain within a BIAN-aligned core-banking landscape.

Maintain a single view of the customer across products, channels, and entities
Drive onboarding, servicing, and offboarding journeys for Customer Event Log records
Feed customer analytics, consent, and entitlement decisions to channel applications

APIBIAN semantic API

The control record (Customer Event Log 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-event-log-maintenance-agreement/initiate`	Initiate
GET	`/v1/customer-event-log-maintenance-agreement/{crId}/retrieve`	Retrieve
PUT	`/v1/customer-event-log-maintenance-agreement/{crId}/update`	Update
PUT	`/v1/customer-event-log-maintenance-agreement/{crId}/control`	Control (suspend / resume / terminate)

INTBackend integrations

The systems and standards a real deployment of Customer Event History would transact with.

CRM: Salesforce Financial Services Cloud, Microsoft Dynamics 365
CIAM: Keycloak, Okta, ForgeRock
Credit bureaus: CIBIL, Experian, Equifax
KYC utilities & registries

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

# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-customer-event-history ./helm -n bian-sales-service

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

What business area does Customer Event History belong to?

Customer Event History sits in the Sales and Service business area — the customer-facing sales, servicing and channel domains that run the customer lifecycle. It runs in the bian-sales-service namespace as one independent Spring Boot microservice.

Is Customer Event History 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.