Sales and Service
Product Matching
sd-product-matching · bian-sales-service
A BIAN service domain in Sales and Service. It applies the Process functional pattern to the Product Match, with the Product Match Procedure as its control record — one independent Spring Boot microservice on the platform's Cilium eBPF mesh.
View repository ↗The 162-domain platform ↗
Business DomainSales
Functional PatternProcess
Asset TypeProduct Match
Control RecordProduct Match Procedure
USEWhat it is used for
Representative use cases for the Product Matching service domain within a BIAN-aligned core-banking landscape.
- Run Product Matching workflows from lead capture through fulfilled product agreement
- Match customers to eligible products using bureau + behavioral data
- Track conversion funnels and hand off won opportunities to fulfillment domains
APIBIAN semantic API
The control record (Product Match Procedure) 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/product-match-procedure/initiate | Initiate |
| GET | /v1/product-match-procedure/{crId}/retrieve | Retrieve |
| PUT | /v1/product-match-procedure/{crId}/update | Update |
| PUT | /v1/product-match-procedure/{crId}/control | Control (suspend / resume / terminate) |
INTBackend integrations
The systems and standards a real deployment of Product Matching would transact with.
- CRM & lead engines: Salesforce, HubSpot
- Pricing/offer engines: Earnix, Nomis
- Origination platforms: nCino, FinnOne
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-product-matching
mvn -f sd-product-matching spring-boot:run
curl localhost:8080/v1/service-domain
# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-product-matching ./helm -n bian-sales-service
FAQQuestions
What is the BIAN “Process” functional pattern?
A Process service domain executes and tracks a defined operational procedure, step by step, to completion. Product Matching applies it to the Product Match.
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. Product Matching is the service domain for Sales; it manages the Product Match Procedure and exposes it through standard BIAN action terms.
What business area does Product Matching belong to?
Product Matching 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 Product Matching 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
Product Matching is one of 162 BIAN service domains on the platform. Explore the rest: