9fac160258
Add independent payment-service (port 8012, payment_db) with foundation licensing, BYO-PSP, merchant accounts, idempotent requests, callbacks, and immutable ledger. Co-authored-by: Cursor <cursoragent@cursor.com>
2.0 KiB
2.0 KiB
Phase Pay-Reg — Payment Platform Registration
| Field | Value |
|---|---|
| Phase ID | payment-reg |
| Title | Payment Platform Registration |
| Status | Complete (documentation-only) |
| Service | payment (registered; not yet implemented) |
| Commercial Product | Torbat Pay |
| ADR | ADR-020 |
Purpose
Register the independent Enterprise Payment Platform (Torbat Pay) — service identity, database, phases 14.0–14.10, module inventory, boundaries, and manifests — without modifying any existing service code.
Business Scope
- Document dual tenant payment modes: BYO-PSP and Torbat Pay Merchant (facilitator).
- Define platform-wide payment consumption pattern for Accounting, CRM, Hospitality, Sports Center, Marketplace, Delivery, Experience, Healthcare, Beauty Business, Automation, and future verticals.
- Reserve API port 8012 and database
payment_db.
Technical Scope
- ADR-020 accepted.
- Phases
payment-reg,payment-14.0…payment-14.10registered in phase-manifest. - Service entry in service-manifest and project-index.
- Module registry, roadmap, phase area README, service snapshot (registration state).
- Handover for next phase
payment-14.0.
Out of Scope
- Any code under
backend/services/payment - Alembic migrations, compose wiring, frontend checkout UI
- Real PSP SDK integrations (deferred to
payment-14.1+)
Definition of Done
- ADR-020 published
- payment-roadmap.md with complete phase 14.0–14.10 specifications
- Phase documents under phases/Payment/
- Manifests, project index, module registry updated
- Service snapshot generated (registration baseline)
- Handover phase-pay-reg.md complete
- No existing business services modified