How djambred/manjo-2026 works
This Laravel application is a QRIS payment command center: merchants or payment clients create and query transactions, payments update their status, and merchant notifications are dispatched through an outbox. Operators can inspect activity and perform investigation actions; administrators manage merchant and transaction records. The tree and excerpts support the main processing and operational branches, but not every route or integration detail, so uncertain wiring is omitted.
Main entry points: QrisTransactionActionService.php Transaction Actions · Resources Admin Resources · QrisMobilePaymentController.php Mobile Payment · QrisTransaction.php QRIS Transactions
Components 20
Payment API
- Create and Query
src/app/Http/Controllers/Api/QrisApiController.php - Callback and Ops
src/app/Http/Controllers/Api/QrisOpsController.php
Payment Lifecycle
- Mobile Payment
src/app/Http/Controllers/QrisMobilePaymentController.php - Transaction Actions
src/app/Services/QrisTransactionActionService.php - QRIS Transactions
src/app/Models/QrisTransaction.php - Status History
src/app/Models/TransactionStatusHistory.php - Query Logs
src/app/Models/TransactionQueryLog.php - Settlements
src/app/Models/Settlement.php - Refunds
src/app/Models/Refund.php - Callback Logs
src/app/Models/CallbackLog.php - Notification Outbox
src/app/Models/MerchantNotificationOutbox.php - Outbox Dispatch
src/app/Jobs/DispatchMerchantNotificationOutboxJob.php
Operations
- Command Center
src/app/Http/Controllers/CommandCenterController.php - Operations Views
src/resources/views
Administration
- Admin Resources
src/app/Filament/Admin/Resources - Merchant Records
src/app/Models/Merchant.php - User Records
src/app/Models/User.php
Other components
- Merchant Client
- QRIS Provider
- Merchant Callback
Connections 36
- Merchant Client → Create and Query: submits requests
- Create and Query → QRIS Transactions: creates or reads
- Create and Query → Query Logs: records queries
- Create and Query → Merchant Records: looks up merchant
- Create and Query → Merchant Client: returns QR and status
- QRIS Provider → Callback and Ops: sends callbacks
- Callback and Ops → QRIS Transactions: updates status
- Callback and Ops → Callback Logs: records callback
- Callback and Ops → Merchant Records: looks up merchant
- Mobile Payment → QRIS Transactions: updates payment
- Mobile Payment → Status History: records transition
- Mobile Payment → Settlements: upserts settlement
- Mobile Payment → Notification Outbox: creates notification
- Mobile Payment → Outbox Dispatch: dispatches outbox
- Transaction Actions → QRIS Transactions: changes status
- Transaction Actions → Query Logs: records query
- Transaction Actions → Status History: records transition
- Transaction Actions → Settlements: updates settlement
- Transaction Actions → Refunds: records refund
- Transaction Actions → Callback Logs: records simulation
- Transaction Actions → Notification Outbox: creates notification
- Transaction Actions → Outbox Dispatch: dispatches outbox
- Outbox Dispatch → Notification Outbox: reads delivery
- Outbox Dispatch → Merchant Callback: sends notification
- Command Center → QRIS Transactions: reads transactions
- Command Center → Notification Outbox: reads deliveries
- Command Center → Callback Logs: reads callbacks
- Command Center → Query Logs: reads query history
- Command Center → Operations Views: renders pages
- Admin Resources → Merchant Records: manages merchants
- Admin Resources → QRIS Transactions: manages transactions
- Admin Resources → Settlements: manages settlements
- Admin Resources → Refunds: manages refunds
- Admin Resources → Notification Outbox: manages deliveries
- Admin Resources → Callback Logs: reviews callbacks
- Admin Resources → User Records: manages users