How narutchai01/solpay-core-service works
Solpay Core Service exposes account, identity, balance, quote, swap, and transaction APIs, with RabbitMQ-driven processing for deposits and withdrawals. The principal transaction workflow accepts an API request, records it, then advances asynchronous blockchain, balance, and payment stages before finalizing status; off-chain withdrawals also generate and store a slip. The README documents those event relationships. Several domain modules are unsampled, so their internal calls are not inferred here.
Main entry points: transaction_service.go Transaction orchestration · consumer.go Event consumers · server.go HTTP server · routes.go API routes
Components 24
HTTP API
- HTTP server
internal/server/server.go - API routes
internal/routes/routes.go - Transaction handlers
internal/handler/transaction_handler.go - User handlers
internal/handler/user_handler.go - Account handlers
internal/handler/account_handler.go
Domain Services
- Domain services
internal/core/services - KYC & user service
internal/core/services/user_service.go - Quote & swap
internal/core/services/quote_service.go - On-chain service
internal/core/services/onchain_service.go - Balance service
internal/core/services/balance_service.go
Transaction Processing
- Transaction orchestration
internal/core/services/transaction_service.go - RabbitMQ queues
internal/infra/rabbitmq - Event consumers
internal/infra/rabbitmq/consumer.go
Persistence & Integrations
- PostgreSQL
internal/db/db.go - Transaction repository
internal/infra/repositories/transaction_repository.go - Domain repositories
internal/infra/repositories - Solana transaction client
internal/infra/solana/transaction_repository.go - Payment gateway
internal/infra/payment/omise_gateway.go - Slip generation
internal/utils/slip.go - Supabase storage
internal/infra/supabase/upload.go
Realtime
- WebSocket hub
internal/websocket/hub.go - WebSocket routes
internal/routes/websocket_route.go
Other components
- User
- Supabase
Connections 30
- User → HTTP server: sends requests
- HTTP server → API routes: configures routes
internal/server/server.go - API routes → Transaction handlers: routes transactions
- API routes → User handlers: routes users
- API routes → Account handlers: routes accounts
- Transaction handlers → Transaction orchestration: invokes
internal/handler/transaction_handler.go - User handlers → KYC & user service: invokes
internal/handler/user_handler.go - Account handlers → Domain services: invokes
internal/handler/account_handler.go - HTTP server → RabbitMQ queues: sets up queues
internal/server/server.go - HTTP server → WebSocket hub: starts
internal/server/server.go - HTTP server → WebSocket routes: configures
internal/server/server.go - Transaction orchestration → Transaction repository: records transaction
- Transaction repository → PostgreSQL: reads and writes
internal/infra/repositories/transaction_repository.go - Transaction orchestration → RabbitMQ queues: publishes events
- RabbitMQ queues → Event consumers: dispatches messages
- Event consumers → Transaction orchestration: reports status
- Event consumers → Solana transaction client: dispatches on-chain work
- Event consumers → Balance service: dispatches balance work
- Event consumers → Payment gateway: dispatches payment work
- Event consumers → PostgreSQL: updates transaction
- KYC & user service → Supabase storage: uploads KYC images
internal/core/services/user_service.go - Supabase storage → Supabase: stores files
- Transaction orchestration → Slip generation: generates slip
- Transaction orchestration → Supabase storage: uploads slip
- Transaction orchestration → WebSocket hub: notifies clients
- API routes → Quote & swap: exposes quotes and swaps
internal/routes/routes.go - Quote & swap → Domain repositories: uses repositories
- On-chain service → Solana transaction client: uses client
- Balance service → Domain repositories: uses repositories
- KYC & user service → Domain repositories: uses repositories