Insurance financial flows¶
Development area: Insurance financial flows
Premiums, commissions, refunds, and indemnity payments executed through payment services. OpenPlatform reuses the payments module and adapter libraries rather than inventing a parallel money-movement stack.
Public description: https://fireflysoftware.io/openplatform/#insurance-development
Why this area exists¶
Insurance money movement (premium, commission, refund, indemnity) still needs durable payment records and rail/PSP boundaries. Duplicating that beside banking payments would fork the hardest integration surface. This area points implementers at the payments module and states what is still missing for insurance-specific ledgers.
When to use it¶
Use this area when designing premium collection, commission payout, refund, or indemnity settlement on OpenPlatform. Implement against payments, library-rails, and library-psps.
Foundations already in OpenPlatform¶
| Module / guide | Why it matters |
|---|---|
| Payments | Orders, cards, engine, PSDX, rail/PSP libraries |
| Accounts | Account relationships and ledger/GL posting when required |
| Distribution | Commission context for agents and brokers |
| Agreements | Contractual basis for premium and indemnity |
| Adapters | Provider and institution-core boundaries |
Layer map¶
No dedicated insurance-finance repositories are published under firefly-oss yet. Use the payments layer map:
| Layer | Repositories to start from |
|---|---|
| Experience | exp-cards (and product BFFs as published) |
| Domain | domain-banking-cards (payment domain gaps called out on the payments page) |
| Core | core-banking-payments, core-payments-engine, core-banking-psdx |
| Libraries | library-rails, library-psps |
How to start¶
- Read Payments end to end.
- Implement rail/PSP calls through the adapter libraries, not inside domain services.
- Keep institution cores that remain books of record behind adapters (accounts).
- Parent pin: 26.10.19 / Boot 4.1.1 / Java 25.
OpenAPI and events¶
OpenAPI — payments. Events: stub.
Maturity notes¶
In development as an insurance tile; payment foundations are already present. Prefer category language for external networks unless an approved integration guide names them.