Secure Account Management Banking Software

I’m building a new banking platform focused on rock-solid account management and bulletproof secure transactions. The application must scale smoothly from pilot phase to full production, handle thousands of concurrent users without a hitch, and pass the kind of security scrutiny a regulated financial institution expects. Scope of work The core modules include account opening, balance and statement views, real-time transaction history, pay-in/pay-out processing, and role-based admin dashboards. Seamless secure transaction flows are non-negotiable; every transfer, balance update, or statement request has to be atomic, auditable, and tamper-proof. While secure transactions top the list, I’m happy to integrate any additional layers you recommend—be it two-factor prompts, data-at-rest encryption, or token-based session hardening—so long as they don’t compromise usability. Technology environment Choose the stack you know you can harden and scale—Java/Spring Boot, .NET Core, Node.js with TypeScript, or a comparable enterprise-grade framework. Containerisation (Docker, Kubernetes), automated CI/CD, RESTful or gRPC APIs, and a relational database with ACID guarantees (PostgreSQL, Oracle, or similar) are expected. Cloud deployment on AWS or Azure is preferred, but an on-prem option can be discussed if it better supports compliance. Deliverables • MVP with fully functional account management and secure transaction workflows • Source code in a private Git repo, structured for microservice expansion • Infrastructure-as-code scripts (Terraform or CloudFormation) for repeatable environments • Unit, integration, and security test suites with ≥90 % coverage • Deployment guide and developer documentation that let any competent engineer spin the system up in under 30 minutes • Final handover demo proving transaction integrity under load Acceptance criteria 1. All transactions roll back cleanly on failure and leave no partial writes. 2. OWASP Top-10 penetration tests return zero critical findings. 3. Load test: 2,000 simultaneous users, <250 ms average response on balance queries. 4. Codebase passes static analysis with no high-priority issues. 5. Documentation is complete, clear, and version-controlled alongside the code. Once these boxes are checked, the project is done—though I expect the architecture to be robust enough for future add-ons like loan processing or a mobile front-end. If this challenge fits your wheelhouse, let’s get started.

Project ID: 40191067