How ankushp965/payment-platform works
Payment-Platform is a small payment-processing system. A client submits a payment to the Payment API, which assigns an ID and independently requests ledger recording and notification dispatch before returning their statuses. The ledger persists transactions in PostgreSQL; notification delivery is currently mocked. Each service also exposes health and Prometheus metrics endpoints. The README provides no further product detail, and deployment configuration is not mapped as runtime behavior. Edges reflect the shown HTTP calls and database operations; no metrics scraper or external messaging integration is evidenced.
Main entry points: payment-api/main.py Payment API · ledger/main.py Ledger service · notification/main.py Notification service · postgres.yaml PostgreSQL
Components 8
Payment processing
- Payment API
services/payment-api/main.py
Ledger
- Ledger service
services/ledger/main.py - PostgreSQL
charts/payment-platform/templates/postgres.yaml
Notifications
- Notification service
services/notification/main.py
Service operations
- Payment metrics
services/payment-api/main.py - Ledger metrics
services/ledger/main.py - Notification metrics
services/notification/main.py
Other components
- Payment client
Connections 7
- Payment client → Payment API: submits payment
services/payment-api/main.py - Payment API → Ledger service: posts entry
services/payment-api/main.py - Payment API → Notification service: posts notification
services/payment-api/main.py - Ledger service → PostgreSQL: writes transaction
services/ledger/main.py - Payment API → Payment metrics: records metrics
services/payment-api/main.py - Ledger service → Ledger metrics: records metrics
services/ledger/main.py - Notification service → Notification metrics: records metrics
services/notification/main.py