Wasif Iqbal

Senior Solution Architect, Payments & Fintech

15 years designing secure, scalable, cloud-native platforms for banks and fintechs, and staying in the build long enough to see the architecture survive contact with production.

Fig. 0: the network mark, at scale. Hover a node for detail.
15+
Years of Software Experience
12+
Years Leading Engineering Teams
10+
Enterprise Systems Delivered
7+
Years Designing Enterprise Architectures
10+
Legacy Systems Transformed
5+
Years Building Cloud-Native Solutions
About
nameWasif Iqbal
roleSr. Solution Architect
domainfintech / banking
experience15+ years
basedN. Virginia
statusavailable

Who I am

I'm a Senior Solution Architect with over 15 years delivering enterprise-grade solutions across fintech and banking. I specialize in architecting scalable platforms, leading distributed engineering teams, and solving complex technology challenges from discovery through execution.

My approach is rooted in full ownership. I design architectures, stay engaged in implementation, guide technical direction, mentor engineers, and help teams deliver reliable solutions to production, not a document handed off and forgotten.

Beyond technology, I'm a builder: woodworking, 3D printing, home automation. Same instinct, different material: turning ideas into things that actually work.

What does a fractional solution architect do for a fintech startup?

Designs the target system architecture, makes the build-versus-buy and sequencing calls, and stays engaged through implementation rather than handing off a document and leaving. For a fintech startup, that means architecting payment and core platform systems that are PCI compliant from the start, setting a modernization roadmap the team can actually execute against, and mentoring the engineers who'll own the system after the engagement ends, all without the cost of a full-time architecture hire.

What's the difference between a solution architect and a software architect?

A software architect owns the design of one system: its modules, its internal structure. A solution architect owns the space between systems: how a new platform fits the existing stack, which parts to buy versus build, and how migration happens without stopping the business. On a fintech engagement, that usually means the payment rails, the core ledger, and everything already in production, not a single codebase in isolation.

How long does a legacy payment system modernization actually take?

Longer than the first estimate, and that's fine if it's accounted for. A gateway or issuing platform with a decade of production history rarely modernizes in one push. It moves adapter-first: wrap the legacy system, migrate merchants or accounts in waves, and retire the old platform only once the new one has proven itself under real volume. Expect 12–24 months for a meaningful cutover on a system that size, not a quarter.

What does PCI DSS actually change about how you design a system?

Mostly where you draw boundaries. Cardholder data gets its own tightly scoped network segment, tokenization replaces raw PAN storage everywhere it can, and every service that touches that segment inherits the compliance burden, so the real architecture work is minimizing how much of the system is actually in scope. Get that boundary right early and the rest of PCI DSS is mostly process, not redesign.

Experience

Track record

Twelve engagements across four employers, most recent first. Jump to one, or scroll. The nav on the left tracks where you are.

Blankfactor / Globant

2023 – Present
Lead Architect

Payment Gateway Consolidation & Modernization

Leading a comparative assessment of distributed payment gateway ecosystems for two PayFac clients (one running 8 gateways, another 10+). Each client's gateways are evaluated on industry fit, product features, functional and non-functional requirements, and technology and operations, then one strategic gateway is recommended per client while the rest are sunset. The consolidation itself follows an adapter-based architecture for backward compatibility, migrating merchants in waves with risks flagged and mitigated.

Assessment complete; consolidation strategy and migration roadmap in place across both platforms.
MicroservicesCloud InfrastructureObservability Tooling
Lead Architect

Banking Product Suite: Liquidity, Marketplace & Settlement

Designed the end-to-end prototype and high-level target-state architecture and data model for a bank's Liquidity Management product, then led the effort to build an MVP on the client's preferred stack (Java Spring, PostgreSQL, AWS, Angular). Also leading, from an architecture role, the design and prototyping of a Vendor Marketplace and Settlement Engine as the next MVP portals.

Liquidity Management System MVP delivered and in client demo; Vendor Marketplace and Settlement Engine portals in design and prototyping.
FigmaJava SpringPostgreSQLAWSAngular
Senior Solution Architect

Payfac Platform Modernization

Modernized a payment facilitator's business processes and infrastructure with cloud-native modules, evolving legacy components into scalable, resilient services under strict PCI DSS compliance. Integrated Datadog logging, metrics, and SIEM to strengthen observability and security monitoring.

AWS costs down 10% · System latency down 25%.
AWSMicroservicesDatadog APM/SIEMPCI DSS

Croem Inc

2012 – 2023
Lead Solution Architect

Gateway Platform

Modernized a legacy SOAP/WebForms (.NET 3.5) payment gateway into a modular-monolith platform on .NET Framework 4.5+ (MVC, Entity Framework) with a new UX and upgraded infrastructure, PCI DSS compliant and integrated with AMEX, CLAVE, Mastercard, Tecnicard, and other payment processors. Owned it end-to-end for over a decade in production, powering payment acceptance across eCommerce platforms and a merchant portal.

Merchants processed transactions without touching processor or network complexity.
C# / .NET Framework 4.5+ (MVC, EF)SQL ServerPayment APIsPCI DSS
Lead Solution Architect

Legacy Issuing System Modernization

Modernized and migrated a private card issuing platform to a new .NET Core system, replacing a tightly coupled legacy codebase that had become difficult to maintain and scale. Added web and mobile interfaces for digital wallet access, integrated with the banking core to service its products, and eased onboarding through dynamic forms.

Platform stability and performance improved; ready for evolving issuing requirements.
C# / .NET CoreAngularMobilePCI DSS
Sr. Software Engineer & Team Lead

Customer & Subscription Management Platform

Designed a multi-tenant customer and subscription platform used across telecom, insurance, and utility: customer lifecycle, subscription orchestration, billing rules, and financial reporting.

Streamlined billing across industries with improved reporting accuracy.
C# / .NETAngularREST APIs
Lead Principal Developer & Architect

AMS: Maritime Management System

Architected and built a comprehensive document and workflow management system for the Panama Canal Authority, replacing a legacy static, manual process. Led a team of developers and QA, managing the project end-to-end across the full SDLC.

Modernized a manual, paper-based workflow into a digital system for a national infrastructure authority.
C# / .NET CoreSQL ServerAngular
Lead Principal Developer & Architect

CedulaD: National Digital Wallet (COVID Response)

Architected and built CedulaD, a digital wallet issuing monthly government allowances to citizens of Panama in response to COVID-19, delivered in a 2–3 month build cycle. Integrated with stores and supermarkets for grocery and medicine purchases, later expanded to education and medical sectors. Led a team of developers and QA, managing the full SDLC from requirements through release.

Scaled nationwide to all citizens of Panama.
C# / .NET CoreSQL ServerAngular
Principal Developer & Architect

POS, Link to Pay, Click to Pay & Social Pay

Built and maintained a suite of independent payment channels (POS, Link to Pay, Click to Pay, and Social Pay) integrated with the core payment gateway, letting merchants pick the channel that fit their needs. Owned development, support, and ongoing improvement across the full SDLC.

Gave merchants channel flexibility without touching gateway integration complexity.
C# / .NET 4.6SQL ServerAngular / Vanilla JS
Senior Software Engineer

eCommerce Billing Portal: Telco, Insurance & Utility

Built a white-label eCommerce billing portal enabling prepaid and postpaid bill payment across telecom, insurance, and utility industries.

Single white-label platform scaled to 30+ clients across three industries.
C# / .NET 4.6SQL ServerJavaScript

BroadPeak Technologies

Jan 2012 – Mar 2012
Software Developer

Edible Arrangements: Franchise Order Email Receipt

Maintained Edible Arrangements' enterprise franchise software and partnered with the US Franchise team to design, build, and launch an automated order email receipt feature.

Streamlined order confirmation workflows for franchise operations.
Franchise Systems

Deltasoft Technologies

Jul 2011 – Jan 2012
Software Developer

Web-Based Mapping Plugin

Built a modular, web-based mapping plugin using the Great Map algorithm and local storage for data persistence, then integrated it into the company's customer management portal.

Gave the customer management portal a reusable, self-contained mapping module.
JavaScriptWeb Mapping
Services

Where I help

Six ways engagements usually start, most turn into more than one.

Solution Architecture

Design and evolve scalable, maintainable systems from the ground up, or stabilize a complex legacy platform. Target architectures and modernization roadmaps, written to be implemented, not admired.

Payment Systems & Fintech

Deep expertise across gateways, payment facilitators, acquiring and issuing. Building and scaling PCI-compliant systems that process high-volume transactions securely and reliably.

Learn more about Payment Systems & Fintech

Engineering Leadership & Mentorship

Hands-on leadership for technical teams: execution, backlog prioritization, architecture reviews, and code quality, building engineering cultures that consistently deliver.

Cloud Migration & Modernization

Modernize legacy platforms into cloud-native architectures on AWS and Azure. System decomposition, microservices adoption, and DevOps enablement for long-term stability.

DevSecOps & Observability

Embed security and operational excellence into every layer of delivery. CI/CD pipelines, automated quality gates, and observability that enables secure, fast releases.

AI Engineering & Agent Systems

Design and operate agentic AI systems: multi-agent orchestration and GenAI applications, backed by evaluation pipelines. Same reliability bar as payment infrastructure, no looser standard for AI.

How do you approach legacy system modernization without downtime?

The system gets decomposed and migrated in stages, not replaced in one cutover. That means identifying the components with the least coupling first, standing up the new architecture alongside the old one, and routing traffic incrementally while both versions run in parallel long enough to verify behavior under real load. Cloud migration and modernization work follows the same pattern whether the target is AWS or Azure: infrastructure optimization and micro-services adoption happen in sequence, verified at each step, so the system stays operational for users the entire time.

What does engineering leadership look like in a consulting engagement?

It's hands-on, not advisory-only: driving backlog prioritization, running architecture reviews, and setting the code quality bar the team holds itself to. Those are the same responsibilities a full-time engineering leader carries, scoped to the engagement. The goal is an engineering culture that keeps delivering after the engagement ends, not a set of recommendations that depend on the consultant staying in the room.

Architecture

How I actually work

Diagrams aren't decoration here: they're the first artifact I hand an engineering team, and often the most honest description of the problem. Four patterns from recent work.

Architect · Backend ·Frontend · QA · SecurityDiscoverSpecShapePlanFeaturescoped agent +playbookShipbuild · lint ·spec + craft verdictRetro & Learnings

Agentic AI development. A foggy effort gets charted into decisions first (discover), then specified into a backlog with testable acceptance criteria (spec), and every open design question gets answered before a line of code is written (shape). The backlog is sequenced into demoable, one-context-window slices (plan). Each slice is then claimed and built by dispatching to whichever specialized agent owns its stack, architect, backend, frontend, QA, security, DevOps, each scoped to only the tools its role needs and a stack-specific playbook (feature). Before it ships, it clears a quality gate: build, lint, and a two-axis verdict on spec fidelity and craft (ship). Retros feed what's learned back into the agents and skills themselves, so the system improves with every cycle.

StakeholderWorkshopVision &GoalsFigmaPrototypeValidated WorkflowData ModelArchitecture& Deliveryiterate

Product design in mind. Before a system diagram exists, there's a product one. A stakeholder workshop turns into a whiteboarded vision and goals, then an interactive Figma prototype validates the workflow with stakeholders, so the technical design serves the product vision instead of the other way around.

// illustrative, redrawn for public use, not a client's actual system diagram

AWSClient /API TrafficCloudflareCDN + WAFApp Layer(EC2)Microservices ·Monolith · ServerlessAmazon ElastiCache(Redis), hot cacheAmazon RDS (Aurora)indexed + read replicasAmazon MQasync event queueBackgroundConsumers(multiple · EC2)Datadog: APM · Logs · MetricsOptimized,Scalable PayFaccache hit ↑ · DB load ↓queue smooths spikes

PayFac modernization and scalability. A PayFac platform re-tuned for scale on AWS, fronted by Cloudflare: a mix of microservices, a modular monolith, and serverless functions on EC2. Amazon ElastiCache (Redis) absorbs read-heavy traffic ahead of an optimized Amazon RDS/Aurora layer, while Amazon MQ decouples write-heavy events to multiple background service consumers. Datadog instruments every hop, cutting database load and smoothing traffic spikes.

// illustrative, redrawn for public use, not a client's actual system diagram

GatewayInventoryData, Docs &MetricsFeature Mapping &CompatibilityGateway SelectionFinancials · FeaturesRoadmap · Ops · InfraConsolidationStrategymigration plan +future-state architectureMigrationStrategyAdapterApproachLift andShiftRisk &MitigationArchitecturalDecisionGaps toCloseModernization

Gateway assessment and evaluation. Every gateway in the estate gets inventoried, then evaluated against the same yardstick: docs, metrics, product-feature mapping, and compatibility. The winner is chosen on financials, features, product roadmap, operational maturity, and infrastructure, then locked into a consolidation strategy spanning migration approach (adapter vs. lift-and-shift), risk and mitigation, architectural decisions, gaps to close, and modernization sequencing.

// illustrative, redrawn for public use, not a client's actual system diagram

Stack

What I build with

Architecture & System Design
Cloud-NativeDDDDistributed SystemsEvent-DrivenAPI StrategySOLIDDesign PatternsAgentic AI
Cloud & Infrastructure
AWSAzureTerraformCloudFormationCI/CD
Security & Compliance
IAMOAuth2 / OIDCSecrets MgmtPCI DSSDevSecOps
Backend & Data
C# / .NETJava / SpringPythonPostgreSQLKafka
Leadership & Delivery
Team LeadershipSDLC PracticesAgile DeliveryStakeholder Alignment
Observability
Distributed TracingAPMMetricsIncident Mgmt
Also: GitHub · Azure DevOps · Jira · Confluence · Docker · Jenkins · Datadog APM · ELK Stack · SonarQube · Postman · Swagger/OpenAPI · Lucidchart · Draw.io · Miro
Contact

Have an architecture problem worth solving properly?

Open to Principal Architect roles, leadership positions, and consulting engagements. If it's worth building, I want to hear about it.

Book a call

Based in Virginia. Available for remote and hybrid engagements. Response time is typically 24–48 hours.