Sales and Service

Channel Activity History

sd-channel-activity-history · bian-sales-service

A BIAN service domain in Sales and Service. It applies the Maintain functional pattern to the Channel Activity Log, with the Channel Activity 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 DomainChannels

Functional PatternMaintain

Asset TypeChannel Activity Log

Control RecordChannel Activity Log Maintenance Agreement

USEWhat it is used for

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

Operate the Channel Activity Log touchpoint and expose its sessions/events to the bank
Route customer contacts and service orders to the right fulfillment domain
Capture channel telemetry for fraud signals and experience analytics

APIBIAN semantic API

The control record (Channel Activity 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/channel-activity-log-maintenance-agreement/initiate`	Initiate
GET	`/v1/channel-activity-log-maintenance-agreement/{crId}/retrieve`	Retrieve
PUT	`/v1/channel-activity-log-maintenance-agreement/{crId}/update`	Update
PUT	`/v1/channel-activity-log-maintenance-agreement/{crId}/control`	Control (suspend / resume / terminate)

INTBackend integrations

The systems and standards a real deployment of Channel Activity History would transact with.

Digital banking: Backbase, Temenos Infinity
ATM/POS: NCR, Diebold Nixdorf, Verifone, Ingenico
Contact center: Genesys, Twilio Flex, Amazon Connect

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

# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-channel-activity-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. Channel Activity History is the service domain for Channels; it manages the Channel Activity Log Maintenance Agreement and exposes it through standard BIAN action terms.

What business area does Channel Activity History belong to?

Channel Activity 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 Channel Activity 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.