Takaful and Shared Operations

Customer Reference Data

isb-customer-reference-data · isb-operations

A Shariah-native BIAN service domain in Takaful and Shared Operations. It applies the Maintain functional pattern to the Customer Reference Data, with the Customer Reference Data Maintenance Agreement as its control record — one isolated Spring Boot microservice.

View repository ↗The 48-domain landscape ↗

Business DomainShared Operations

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 service domain within a Shariah-compliant core-banking landscape.

Maintain Customer Reference Data records consistently across the Islamic estate
Combine conventional KYC/AML with Shariah-specific screening at onboarding
Produce AAOIFI-basis financials and IFSB regulatory returns
Operate branch/digital channels with products labeled by underlying contract

APIBIAN semantic API

Each service domain exposes its control record (Customer Reference Data Maintenance Agreement) through uniform BIAN action terms. Java 21 · Spring Boot 3, with OpenAPI at /swagger-ui.html.

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 would transact with.

AML/screening: NICE Actimize, World-Check (plus Shariah screening data)
Accounting: AAOIFI FAS-aligned GL mappings on SAP/Oracle
Regulators: IFSB-aligned returns; national central banks

RUNRun it yourself

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

# run this domain standalone
git clone https://github.com/Sreenivas-Sadhu-Prabhakara/isb-customer-reference-data
mvn -f isb-customer-reference-data spring-boot:run
curl localhost:8080/v1/service-domain

# or deploy onto Kubernetes (Cilium mesh)
helm upgrade --install isb-customer-reference-data ./helm -n isb-operations

FAQQuestions

What business area does Customer Reference Data belong to?

Customer Reference Data sits in the Takaful and Shared Operations business area — Takaful (cooperative insurance) and the shared operational domains that support the Islamic banking landscape. It follows the BIAN Maintain functional pattern over the Customer Reference Data asset, with the Customer Reference Data Maintenance Agreement as its control record.

How is this isolated from conventional banking?

Completely. The Islamic landscape shares no code, repositories, namespaces or events with the conventional platform. This domain lives in the isb-operations namespace with an isb-* repository and com.bank.islamic package, so the two can never mix by accident.

Is this a certified Shariah-compliant product?

No. It is an educational reference implementation in the BIAN service-domain style. Actual Shariah compliance of any real deployment requires certification by a qualified Shariah Supervisory Board. Standards referenced: AAOIFI, IFSB, IIFM.