- product-portfolio
- ecosystem-catalog
- deep-dives
- core
Billing, Subscriptions, Payments & Revenue - Analysis¶
Planning-layer analysis for category 4. 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: Billing & Subscriptions
- Group: core
- Default wave / cycle: Phase 1 · Core Platform Wave
- 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 |
|---|---|
| Connector | 5 |
| Microservice | 2 |
| Module-in-service | 41 |
| Portal/UI Module | 2 |
Anti-fragmentation stance
Per ADR-0011, the 41 module candidates below are delivered inside the Billing & Subscriptions bounded-context service, not as separate microservices. Only the 2 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-0173 | Payment Gateway Abstraction | 1 | Planned |
| CS-SVC-0187 | Billing Ledger Service | 1 | Planned |
Connector Candidates¶
- Stripe Adapter (
CS-SVC-0174) - plugin in the Connector Runtime. - Adyen Adapter (
CS-SVC-0175) - plugin in the Connector Runtime. - PayPal Adapter (
CS-SVC-0176) - plugin in the Connector Runtime. - Payoneer Adapter (
CS-SVC-0177) - plugin in the Connector Runtime. - Bank Transfer Adapter (
CS-SVC-0178) - plugin in the Connector Runtime.
Portal / UI Modules¶
- Customer Billing Portal (
CS-SVC-0199) - Revenue Operations Dashboard (
CS-SVC-0200)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Billing & Subscriptions 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: standard audit logging.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): Billing Service, Pricing Model Service, Price Book Service, Plan Pricing Service, Add-On Pricing Service, Usage-Based Pricing Service, Tiered Pricing Service, Volume Pricing 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?