How tejasmedade/e-wallet-payment-system works
Project type and purpose
• This is a monolithic, REST-based backend service (no dedicated frontend code) for a digital wallet/payment system (“E-Wallet Payment System”).
• Purpose: expose HTTP endpoints (via Spring Boot controllers) to manage customers, admins, wallets, bank accounts, beneficiaries, bills, and transactions, with MySQL as persistent storage.
File structure
• Top-level pom.xml & Maven wrapper: standard Spring Boot project build.
• src/main/java/com/masai:
• controllers/ → REST endpoints (CustomerController, WalletController, etc.)
• services & servicesImplementation/ → business logic interfaces + implementations
• repository/ → Spring Data JPA repositories mapping to DB tables
• model/ → JPA entity classes (Customer, Wallet, Transaction, Beneficiary, Bill, Address, CurrentSession, etc.)
• dto/ → data transfer objects for request/response payloads
• exceptions/ → custom exceptions + GlobalExceptionHandler
• src/main/resources/application.properties: DB config, server port, messages.properties
README for additional insights
• Confirms layered architecture: REST API built on Spring Boot + Hibernate + MySQL.
• Swagger UI for interactive API docs.
Detailed elements to capture
• Controllers for each resource set (Customer, Wallet, BankAccount, Beneficiary, Bill, Transaction, Login/Logout for Admin & Customer).
• Services + Implementations (interface → concrete class)
• Repositories mapped to each Entity
• Entities: Customer, Admin, Wallet, BankAccount, Beneficiary, Bill, Transaction, Address, CurrentCustomerSession, CurrentAdminSession
• Exception handler (GlobalExceptionHandler) as an interceptor of errors between Controller and Client
• ApplicationProperties (as config) feeding into DataSource configuration