All projects

Developer · Mallow Technologies

Corporate Bank Website

Dynamic loans portal with RBAC

A secure corporate banking site offering real-time loan information, application tracking, and employee-managed content control — so staff update rates, eligibility, and terms without ever touching a developer.

Corporate Bank Website — Dynamic loans portal with RBAC

Domain

Banking / finance

Platform

PHP on Windows IIS

Database

MSSQL Server

Access control

RBAC (3 roles)

Integrations

SFTP · SMTP relay

Overview

A corporate bank needed a customer-facing site where loan information — rates, eligibility, terms — could be kept accurate by their own staff, without a developer in the loop for every change. In a regulated environment, that content control has to be safe, auditable, and role-scoped.

It runs on an enterprise PHP-on-Windows/IIS and MSSQL stack, with a dynamic loan engine, an RBAC employee portal for content management, and secure SFTP/SMTP infrastructure for documents and notifications.

Key features

  • Real-time, editable loan information per loan type — managed by bank staff
  • Step-by-step application and eligibility guidance with 'Apply Now' CTAs
  • RBAC employee portal with Editor, Admin, and Analyst roles
  • Daily loan-application summary with live status tracking
  • Dynamic content blocks rendered per loan category
  • SFTP document upload/download and SMTP relay for notifications

Architecture

~/projects/corporate-bank-website/architecture.md

PHP running on Windows Server (IIS) with MSSQL as the relational database; RESTful APIs; SMTP relay for email; SFTP for secure document handling; strict input validation and role-based access throughout.

What I did

  • Built the dynamic loan-information engine that lets staff edit rates, eligibility, and terms
  • Implemented the RBAC employee portal with Editor, Admin, and Analyst roles
  • Developed application tracking with daily summary reporting
  • Integrated SFTP document handling and SMTP relay on the Windows/IIS + MSSQL stack

Outcomes

Outcome 01

Content control handed to non-technical staff, removing developers from routine updates

Outcome 02

Strict validation, sanitization, and access control across a regulated banking surface

Outcome 03

Reliable document handling and email over enterprise SFTP/SMTP infrastructure

Stack

06 tools

PHPMSSQLWindows IISRESTSMTPSFTP