Source: [OpenPlatform business capabilities](https://fireflysoftware.io/openplatform/modules/)

Description: OpenPlatform capabilities for customers, agreements, payments, lending, and operational records, as Firefly services use them.

Language: en

[Home](https://fireflysoftware.io/)/OpenPlatform / Modules

# Choose capabilities by the work they support.

Each capability groups open modules, combined in a service with the rules and providers its scope needs.

[Discuss your service architecture](https://fireflysoftware.io/contact/) [Explore our services](https://fireflysoftware.io/services/)

## Shared business capabilities.

01

### Customers and relationships

People, organizations, and their relationships.

02

### Onboarding and verification

Evidence records and provider checks.

03

### Products and agreements

Product configuration, contracts, and documents.

04

### Distribution and identity

Partners, user access, and communications.

## Banking and lending capabilities.

01

### Accounts and financial records

Accounts, transactions, and ledger connections.

02

### Payments and cards

Interfaces to your payment and card providers.

03

### Lending lifecycle

Applications, servicing events, collateral, and collections.

04

### Risk and compliance records

Cases, results, and reporting linked to the operation.

Inside each capability

## Open a capability to see its modules.

01

## Customers and relationships

One consistent view of the people and businesses each journey serves.

### What it covers

- People, legal entities and relationships
- Contact details, identity records and consent
- Customer registration coordinated across services

### How it fits

Reuse customer data across account opening, credit applications, and policyholder service.

### Its modules

[core-common-customer-mgmt](https://github.com/firefly-oss/core-common-customer-mgmt) [domain-customer-people](https://github.com/firefly-oss/domain-customer-people)

02

## Onboarding and verification

Data collection, identity evidence, and verification cases in one journey.

### What it covers

- Individual and business onboarding APIs
- Personal, economic and corporate information
- KYC/KYB evidence, case records and journey status

### How it fits

Prepare a complete customer file, with your providers and approval policy built in.

### Its modules

[exp-onboarding](https://github.com/firefly-oss/exp-onboarding) [domain-customer-kyc-kyb](https://github.com/firefly-oss/domain-customer-kyc-kyb) [core-common-kycb-mgmt](https://github.com/firefly-oss/core-common-kycb-mgmt)

03

## Products and commercial configuration

Consistent product definitions, adapted to each channel.

### What it covers

- Catalogue, categories, versions and product relationships
- Configuration and required documentation
- Lending pricing queries and instalment simulations

### How it fits

Compose a financing offer from catalogue and pricing, or connect to an insurer’s rating systems.

### Its modules

[core-common-product-mgmt](https://github.com/firefly-oss/core-common-product-mgmt) [domain-product-catalog](https://github.com/firefly-oss/domain-product-catalog) [domain-core-pricing-engine](https://github.com/firefly-oss/domain-core-pricing-engine)

04

## Agreements and documents

Each agreement with its parties and evidence, in one context.

### What it covers

- Contract terms, party roles and status history
- Document metadata, versions and permissions
- Content and e-signature through your providers

### How it fits

Assemble account and loan agreements, or manage policy-document references beside your policy system.

### Its modules

[core-common-contract-mgmt](https://github.com/firefly-oss/core-common-contract-mgmt) [domain-common-contracts](https://github.com/firefly-oss/domain-common-contracts) [core-common-document-mgmt](https://github.com/firefly-oss/core-common-document-mgmt)

05

## Distribution and partner channels

Product access, branding, and operating context for distributors and agents.

### What it covers

- Distributors, agencies, agents and assignments
- Product assignments, territories and operating permissions
- Channel branding, configuration and contractual terms

### How it fits

Build partner-led finance, or agent and broker journeys connected to the insurer.

### Its modules

[core-common-distributor-mgmt](https://github.com/firefly-oss/core-common-distributor-mgmt) [domain-distributor-branding](https://github.com/firefly-oss/domain-distributor-branding) [domain-distributor-catalog](https://github.com/firefly-oss/domain-distributor-catalog) [exp-distributor](https://github.com/firefly-oss/exp-distributor)

06

## Accounts and financial records

Account relationships kept apart from financial movements, each with its own owner.

### What it covers

- Accounts, balances, restrictions and account spaces
- Transactions, transaction legs and status history
- General-ledger accounts, journal batches and entries

### How it fits

Coordinate account opening and design posting controls around your accounting model.

### Its modules

[core-banking-accounts](https://github.com/firefly-oss/core-banking-accounts) [domain-banking-accounts](https://github.com/firefly-oss/domain-banking-accounts) [core-banking-ledger](https://github.com/firefly-oss/core-banking-ledger) [core-common-accounting-gl](https://github.com/firefly-oss/core-common-accounting-gl)

07

## Payments and cards

Payment and card operations, without provider details in every application.

### What it covers

- Payment orders, beneficiaries, schedules and fees
- Card records, limits, transactions and disputes
- Separate interfaces per payment rail

### How it fits

Build payment and card journeys, including premium collections, refunds, and insurance payouts.

### Its modules

[core-banking-payments](https://github.com/firefly-oss/core-banking-payments) [core-banking-cards](https://github.com/firefly-oss/core-banking-cards) [domain-banking-cards](https://github.com/firefly-oss/domain-banking-cards) [library-rails](https://github.com/firefly-oss/library-rails) [library-psps](https://github.com/firefly-oss/library-psps)

08

## The lending lifecycle

From application, offer, and decision to the records that service a loan.

### What it covers

- Applications, documents, offers and decision records
- Disbursements, repayment schedules and servicing events
- Collateral, collections, and product data

### How it fits

Compose consumer or business finance; credit policy and decisions stay with your institution.

### Its modules

[core-lending-loan-origination](https://github.com/firefly-oss/core-lending-loan-origination) [domain-lending-loan-origination](https://github.com/firefly-oss/domain-lending-loan-origination) [core-lending-loan-servicing](https://github.com/firefly-oss/core-lending-loan-servicing) [core-lending-collateral-management](https://github.com/firefly-oss/core-lending-collateral-management) [core-lending-delinquency-collections](https://github.com/firefly-oss/core-lending-delinquency-collections)

09

## Risk and compliance operations

A structured record of reviews, risk decisions, and reporting, linked to each case.

### What it covers

- Credit-scoring requests, models and result records
- Provisioning, ECL values, and stage history
- AML cases, reports, and submission records

### How it fits

Connect your approved risk calculations to operational records; actuarial systems stay integrated, not replaced.

### Its modules

[core-lending-credit-scoring](https://github.com/firefly-oss/core-lending-credit-scoring) [core-lending-provisioning-risk](https://github.com/firefly-oss/core-lending-provisioning-risk) [core-lending-regulatory-compliance](https://github.com/firefly-oss/core-lending-regulatory-compliance)

10

## Identity and shared services

Access, communication, and configuration, reused across applications.

### What it covers

- Users, roles, permissions and identity-provider links
- Authentication, sessions and token operations
- Notifications, preferences, and reference data

### How it fits

Common access and notifications for banking and insurance journeys, including connected policy systems.

### Its modules

[core-common-user-mgmt](https://github.com/firefly-oss/core-common-user-mgmt) [domain-core-security-center](https://github.com/firefly-oss/domain-core-security-center) [domain-common-notifications](https://github.com/firefly-oss/domain-common-notifications) [core-common-reference-master-data](https://github.com/firefly-oss/core-common-reference-master-data)

Each repository carries its own license and release information.

Scope and selection

## Read the catalogue as part of a service.

### Insurance services connect shared and dedicated capabilities

Policy, underwriting, claims, and actuarial work connect to the insurer’s own systems.

### A module is one part of the service

We select each component for its license, fit, security, and recovery, and accept it before it goes live.

Your first operation

## Bring us one operation.

Tell us the process, the volume, and what “done” looks like. We will come back with a scope, a deployment plan, and a proposal.

[Discuss your service architecture](https://fireflysoftware.io/contact/) [Request a demo](https://fireflysoftware.io/contact/?request=demo)
