- product-portfolio
- ecosystem-catalog
- deep-dives
- vertical
Banking, Payments, Lending & FinTech - Analysis¶
Planning-layer analysis for category 15. It groups the 50 candidate services into capabilities, recommends what becomes a standalone service versus a module, and captures domain, interface, and non-functional notes. For the plain item list see the browse page.
Scope & Bounded Context¶
- Primary bounded context: Banking & FinTech
- Group: vertical
- Default wave / cycle: Phase 4 · Cycle 4: AI Interaction & Verticals
- Items: 50 candidates
This category is anchored to the ConnectSoft DDD baseline in the SaaS framework DDD blueprint and the service classification model.
Classification Breakdown¶
| Classification | Count |
|---|---|
| Module-in-service | 42 |
| Platform Product | 8 |
Anti-fragmentation stance
Per ADR-0011, the 42 module candidates below are delivered inside the Banking & FinTech bounded-context service, not as separate microservices. Only the 8 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-0701 | Digital Banking Platform | 3 | Planned |
| CS-SVC-0708 | Sanctions Screening Platform | 3 | Planned |
| CS-SVC-0726 | Card Issuing Platform | 3 | Planned |
| CS-SVC-0733 | Payment Orchestration Platform | 3 | Planned |
| CS-SVC-0743 | BNPL Platform | 3 | Planned |
| CS-SVC-0744 | Consumer Lending Platform | 3 | Planned |
| CS-SVC-0745 | Business Lending Platform | 3 | Planned |
| CS-SVC-0749 | Open Banking API Platform | 3 | Planned |
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Banking & FinTech context; cross-context reads go through published contracts, never shared databases.
- Integration is event-first (outbox + integration events) per the event-driven mindset.
- APIs are contract-first and versioned through the API & Integration context.
Non-Functional Posture¶
- Multi-tenancy & edition-awareness: required for all serious candidates.
- Security: High baseline; secrets via the platform secret store; least privilege.
- Compliance: critical - audit + evidence by default.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): Card Tokenization Service
- Future (Tier 4-5): none
Open Questions¶
- Which module candidates, if any, develop independent scaling or ownership needs that would justify promotion to a standalone service?
- Where do this category's contracts overlap with adjacent contexts, and who owns them?