Banking, OTP and Settlement Integration

Problem and Context

• Legacy .NET workflows had to support regulated financial operations with traceable auth and settlement flows.
• Multiple bank/identity/SMS integrations introduced synchronous and background reliability risks.

Built

• OTP-gated Web API/MVC surfaces for regulated jeweler and back-office flows.
• REST/SOAP bank integrations, identity checks, file uploads, and request/response persistence.
• Windows services for bank token refresh and Exchange email dispatch.

Architecture

• Global JWT validation via DelegatingHandler.
• Reusable HTTP/SOAP helper patterns.
• Segmented apps/services around tablet, backoffice, bank, and ERP workflows.

Integrations

• REST/SOAP banking endpoints, SMS OTP services, and identity-check providers.
• Back-office and ERP-adjacent workflows around uploads and settlement records.

Reliability, Security, and Operations

• Global JWT validation and token-refresh services separated from request paths.
• Audit-ready logging with persisted request/response trails.

Operations

• Audit-ready traffic logging.
• Token refresh isolated from request paths.
• Business email dispatch decoupled through database-backed mail flow.

Technology Stack