> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-console/product-configurations.md).

# Product Configurations

The **Product Configuration** module is the powerhouse of the XYB Console, a central toolkit for designing, deploying, and managing financial products with both **precision** and **flexibility**. It empowers you to define every aspect of your product’s structure and behavior, giving your team full control from initial setup to production deployment.

***

## Core Components

**1. Products**

This is where you build modular financial products tailored to your use case. You can define how a product behaves, its constraints, and lifecycle parameters such as when it becomes active or archived. With built-in version control, teams can iterate safely while maintaining visibility into historical changes.\
Use cases include launching **wallets** for niche segments, rolling out **BNPL offerings**, or safely testing logic in staging environments before production deployment.

**2. Services**

Each product draws on backend logic powered by modular services like `cac-account-svc`, `cda-entity-svc`, or `cac-ledger-svc`. These services are intentionally decoupled, allowing for easier debugging, clearer ownership, and scalable deployments. Deprecated services are clearly labeled, ensuring teams use only current and supported modules.

**3. Schema Builder**

The Schema Builder is your tool for defining and managing configuration templates using editable JSON blueprints. You can create versioned schema definitions with labeled components and timestamps, perfect for experimenting, onboarding new teams, or aligning front-end behavior with service logic. This makes the platform flexible yet governed, with changes easily tracked and safely deployed.

***

## How it all Comes Together

The Product Configuration module integrates deeply with the rest of the XYB ecosystem:

* **Entities & Accounts** to tie products to real users
* **Ledger & Payments** to enforce business logic for money movement
* **Workflows** to automate events (e.g., disburse a loan after approval)

Together, these integrations turn the module into a **digital product factory**, where your business logic, operational workflows, and technical architecture align.

***

## Why It Matters

* **Full lifecycle control**: Manage everything from drafts to live deployments
* **No-code configurability**: Built for product and operations teams
* **Safe governance**: Versioned, timestamped, and transparent by design

***

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xyb.co/xyb-console/product-configurations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
