FinFactory Blueprint
Master architecture and system design context for FinFactory’s composable fintech platform.
Platform Composition Map
Reference composition map provided for the overview page.
Overview
FinFactory Blueprint is the master architecture and system design repository for FinFactory’s composable fintech platform.
FinFactory is building financial infrastructure primitives that can be assembled into production fintech products such as stored-value wallets, merchant acquiring platforms, QRPh payment systems, card programs, POS deployments, and AI-assisted financial operations.
This repository is documentation-only. It contains architecture decisions, domain models, platform principles, technical standards, and product reference architectures. Implementation code lives in separate service repositories.
Core idea
FinFactory is not a single fintech application. It is a platform made of reusable financial primitives.
Each primitive is a bounded service with its own domain, API, database, events, operational rules, and compliance responsibilities. Products are composed by combining primitives through a unified product API and an orchestration layer.
Platform goals
FinFactory’s platform architecture should support:
- Reusable fintech primitives
- Product-specific composition
- Regulated financial workflows
- Tenant-specific configuration
- Clear service boundaries
- Strong auditability
- Deterministic ledger behavior
- Event-driven integration
- API-first product delivery
- AI-assisted operations with strict controls
Primary primitives
The initial FinFactory primitives are:
- Credit card payments
- Card issuing
- QRPh payments
- EMI wallet issuing
- 3D Secure
- Ledger
- Fraud detection
- Tokenization
- Identity and KYC
- POS and SoftPOS
- AI financial agent
Product composition example
A stored-value e-wallet can be composed from:
- Identity and KYC
- EMI wallet issuing
- Ledger
- QRPh payments
- Fraud detection
- Settlement and reconciliation
- Unified product API
- Product orchestration layer
The client product should not integrate with each primitive separately. Instead, FinFactory should expose one unified API for the composed product while the platform orchestrates the underlying primitives internally.
Repository purpose
This repository should be used for:
- Platform architecture
- Ecosystem diagrams
- Service boundaries
- Domain models
- Product reference architectures
- API standards
- Event standards
- ADRs
- RFCs
- Engineering conventions
- AI coding-agent instructions
This repository should not contain:
- Application source code
- Service implementations
- Database migrations
- Production secrets
- Environment files
- Customer data
- Regulated personal data