Primary Engineering POC & Backend Engineer
Technical Ownership for HSBC's Payment Integration
Owned technical delivery for HSBC as the primary engineering point of contact, translating requirements into architecture and execution while building a configurable Feedzai risk extension.
Details are intentionally generalized to respect confidentiality.
- Timeline
- 2025–2026
- Domain
- Merchant technical ownership, payment integration, risk lifecycle
- Impact
- Served as HSBC's primary engineering point of contact while delivering a configurable Feedzai risk extension across transaction and refund lifecycles.
Architecture
System boundary map
The diagram preserves the major responsibilities and handoffs while omitting proprietary implementation details.
HSBC Technical Ownership
Provided end-to-end technical ownership for the HSBC integration and implemented pre- and post-refund risk flows plus a backward-compatible notification-policy layer driven by dashboard configuration, runtime rules evaluation, and auditable decisions.
Context
I was entrusted with primary technical ownership for HSBC's integration: turning requirements into technical decisions, following delivery through, and communicating clearly across the merchant and internal teams.
Within that ownership, fraud-risk systems influenced real-time payment decisions and downstream provider feedback. Refund support added a separate lifecycle with different status, policy, and notification requirements.
Problem
The platform needed risk-provider coverage before and after refunds in addition to existing transaction stages.
The existing notification model sent updates too broadly; the merchant needed control over which transaction and refund statuses were eligible for provider notification.
Constraints
Risk-provider failures could not make payment or refund paths fragile.
New rules needed backward-compatible defaults for merchants without configuration.
Runtime decisions required auditable evidence for sent and skipped notifications.
Configuration had to reuse existing persistence boundaries safely.
My Role
Served as HSBC's primary engineering point of contact for requirements, technical decisions, issue follow-through, Jira coordination, and delivery discussions alongside product and program stakeholders.
Designed and implemented refund risk coverage and the generic notification-eligibility layer across dashboard, persistence, runtime evaluation, payload contracts, and auditing as one key part of the broader integration ownership.
Technical Design
Added pre-refund and post-refund provider flows with stage-specific request and response handling.
Designed dashboard configuration that persists structured JSON rules and resolves them at runtime for post-transaction and post-refund notifications.
Kept notification decisions backward compatible, with explicit logs for delivery and policy-based suppression.
Tradeoffs
A generic rules layer required stronger validation than merchant-specific branching, but made the capability reusable and operationally clearer.
Reusing existing storage reduced schema churn while placing more responsibility on contract validation and version compatibility.
Impact
Established a clear primary engineering ownership model for HSBC's technical delivery and communication.
Expanded Feedzai risk coverage across transaction and refund lifecycles.
Gave HSBC precise, auditable control over provider notifications without changing default behavior for existing integrations.
What I learned
Customer-facing technical ownership means carrying requirements, decisions, delivery follow-through, and communication together rather than treating them as separate workstreams.
A configurable platform feature is complete only when its defaults, audit trail, and upgrade path are as explicit as its runtime logic.