Ivan Katkov
Selected work/Case 06

Enterprise banking · Secure workflows · Jul 2020 — Dec 2020

Engineering controlled document and payment workflows for corporate banking

I developed React banking interfaces, automated browser-based document signing with cryptographic hardware, and contributed to a shared enterprise UI Kit.

6 modelivery engagementActive banking product development
Cryptohardware integrationBrowser-based document signing
SharedUI KitReusable banking patterns
CASE / 06 SYSTEM ONLINE
VTB Online · OTRSecurity-sensitive workflows for VTB corporate banking

IMAGE PLACEHOLDER · Replace through public/images/cases and the case-study data file.

01 · Executive summary

The shortest honest version.

Situation

Corporate users needed reliable document, payment and service workflows inside a security-sensitive banking environment.

Intervention

I implemented React flows with explicit state orchestration and connected browser actions to hardware cryptographic signing.

Result

The product gained production-ready workflow interfaces and reusable UI patterns within controlled enterprise delivery processes.

02 · Context

Why the engineering work mattered.

VTB Online for legal entities handles business-critical documents, payments and corporate services.

Frontend behavior had to align with security, documentation and controlled deployment requirements.

03 · System design

A clear path from signal to production.

01Banking UI

Documents, payments and business-service screens.

02State machine

Redux and saga orchestration for multi-step flows.

03Signing bridge

Browser interaction with cryptographic hardware.

04Shared UI Kit

Consistent banking patterns across teams.

05Controlled release

OpenShift, Kubernetes and Nexus delivery.

Constraints that shaped the solution

  • Security-sensitive signing behavior.
  • Hardware cryptographic integration.
  • Complex multi-step business states.
  • Controlled enterprise release and documentation requirements.

04 · Decision ledger

The trade-offs behind the implementation.

DecisionReasonTrade-offOutcome
Make async states explicit

Signing and payment flows had multiple recoverable and failure states.

More verbose orchestration logic.

Complex workflow behavior stayed observable and reviewable.

Contribute common patterns to the UI Kit

Banking teams shared interaction and compliance needs.

Components required broader API discipline.

Product teams could reuse consistent interface behavior.

05 · Change

Before and after.

BeforeManual or fragmented signing steps

AfterBrowser-driven signing scenario

BeforeRepeated banking UI patterns

AfterShared UI Kit components

BeforeImplicit async behavior

AfterExplicit Redux-Saga orchestration

06 · Outcomes

Technical change translated into team value.

Technical
  • Implemented document, payment and business-service interfaces.
  • Integrated browser workflows with hardware cryptographic systems.
  • Contributed to a shared React banking component system.
Organizational
  • Worked within strict documentation and delivery controls.
  • Supported reuse across enterprise product teams.
  • Built experience in security-sensitive frontend engineering.

07 · Evidence boundary

Precise claims build more trust than inflated ones.

  1. The case avoids claims about transaction volume or bank-wide outcomes.
  2. Security implementation details are intentionally generalized.
  3. The work described is limited to direct frontend and integration responsibilities.

08 · Reflection

What the project changed in my engineering judgment.

What worked

Explicit state modeling was essential when browser behavior crossed into hardware-backed signing.

What I would improve next

I would formalize workflow statecharts and contract-test the signing boundary.

What this demonstrates

Reliable frontend engineering under security and controlled-delivery constraints.

Next case · 07An end-to-end AI content product for the Russian market