Why Business, Product, and Service Differ in Banking Digital Architecture

Business (Business): Core Value Proposition

Business is the sum of core activities a commercial bank performs to create value for customers, answering “what market we compete in and what fundamental need we solve”. It is strategic, not directly delivered to customers, and guides product and service design.

Example: supply‑chain finance links upstream and downstream enterprises, solves SMEs’ financing difficulties and large corporates’ receivables pressure, covering procurement, production and sales processes. The bank markets the solution, offers products, and delivers services through operations, risk control, etc.

Michael Porter’s value‑chain analysis can be used to understand this flow.

Product (Product): Standardized Packaging of Business

Product answers “how to satisfy the customer need”. It is a standardized, priced, reusable financial instrument or contract derived from business capabilities.

Examples: cross‑border FX spot product, or a restaurant’s “business set menu”. In IT systems, a product corresponds to a template in a product factory containing configurable parameters such as rates, limits, and terms.

Products are tactical, bridging business and service, and enable repeatable delivery through a product factory.

Service (Service): Delivery Interface and Process

Service is the concrete process, channel, or API through which the bank delivers product value to customers. Examples include mobile banking apps, corporate‑banking APIs, or financing application portals.

In development terms, “service” often equals an API that can be composed and invoked, forming the core of a service‑oriented architecture.

Relationship Between Business, Product, and Service

The three form a top‑down chain: Business need → Product encapsulation → Service delivery.

Step‑by‑Step Realization

Define business vision (why) : Identify pain points such as low efficiency of corporate cash management and set the goal of cash‑management business.

Productize (what) : Design standardized products (e.g., cash‑pool, multi‑level ledger) with clear pricing and regulatory attributes, then configure them in a product factory for reuse.

Service‑orient delivery (how) : Expose the product through channels like online banking, APIs, or branch counters, complemented by support services to ensure a smooth customer experience.

Deep Dive: Corporate Account Opening – Product or Service?

Corporate account opening is a basic banking scenario often confused. The process includes application, KYC, on‑site due diligence, approval, and contract signing, with regulatory checks for AML, fraud, and compliance.

From the customer side, the experience focuses on speed, convenience, and service attitude, reflecting service attributes. From the bank side, the process is standardized, priced, and delivers a tangible output (account number, U‑Key), reflecting product attributes.

In modern architecture it should be treated as a “product‑centric standardized service process”.

Product layer (backend) : Define the “basic deposit account” product with interest rates, fee templates, accounting rules, and regulatory reporting attributes.

Service layer (mid‑office) : Decompose the opening flow into atomic services such as customer info validation, AML check, account creation, seal registration, and e‑signing, orchestrated as an “account opening service”.

Experience layer (front‑office) : Whether the client uses a counter, a relationship‑manager tablet, or an online appointment, the same set of middle‑office services is invoked, with workflow variations handling differences like on‑site presence.

Conclusion

Business answers “why”, product answers “what”, and service answers “how”. Confusing these concepts in a bank’s digital architecture is like an architect mixing blueprints, floor plans, and interior design, leading to an uninhabitable building. Clear distinction enables elegant, responsive banking architecture.