Skip to content
Portrait of Bharat Kumar AdhikariBharat Kumar Adhikari

Senior Full-Stack · Payments · Identity · Fraud · AI

I turn complex software into scalable, AI-powered products.

11+ years building production platforms across payments, identity verification, fraud detection, e-commerce, and AI.

System map

  1. Legacy
  2. API
  3. Modern UI
  4. AI
  5. Production

02 — Production domains

Where the work actually lives.

Payments, identity, fraud, commerce and AI — with the products and skills that sit in each domain.

11+ Years of experience
50+ Projects
  • Payments

    Six providers, one abstraction

    Money movement that keeps going when a vendor fails, changes state, or times out.

    • Stripe
    • Breeze
    • Checkbook / ACH
    • AptPay
    • Fiserv DDP
    • Prizeout
    • Webhooks
    • Failover
  • Identity / KYC

    Socure verification lifecycle

    The checks that decide whether a person can move money — wired into the product, not beside it.

    • DocV
    • ReSelfie
    • Deposit-threshold gating
  • Fraud

    SEON in the transaction path

    Fraud signals on the request that matters — across five transaction types.

    • SEON
    • Five transaction types
    • Risk decisions
  • eCommerce

    Storefronts and marketplaces

    Shopify, WooCommerce and custom commerce flows — catalog, checkout and the APIs behind them.

    • Shopify
    • WooCommerce
    • Laravel
    • Vue 3
  • Modernization

    Rebuild without a rewrite

    Keep the schema and the rules that already run the business. Replace one layer at a time.

    • CodeIgniter → Node
    • Schema-compatible APIs
    • JWT + legacy auth
  • AI infrastructure

    LLMs as a production path

    Routing, circuit breakers, cost and RAG — the same reliability patterns used on payments.

    • OpenAI
    • Gemini
    • Anthropic
    • pgvector
    • RAG
  • Semantic video

    Audio or text → planned MP4

    Meaning-based scenes, Remotion render, and providers labelled when they are mock or missing.

    • Remotion
    • Ontology
    • Express
    • Windows TTS
  • Content & engagement

    SEO, mentions, and chat that hands off

    AI inside WordPress, YouTube mention search, and a Gemini chatbot that captures out-of-scope leads.

    • OpenAI
    • Gemini
    • WordPress
    • YouTube transcripts

How the systems stay up

  • Webhook-driven state
  • Provider abstraction
  • Failover
  • Transaction workflows
  • API integrations
  • Reliability architecture

03Watch

A short walkthrough of the AI Transformation Blueprint.

Play the video, then download the free ebook if you want the full 7-step playbook.

The 7-Step AI Transformation Blueprint | Build with AI

Watch on YouTube (opens in a new tab)

04What I solve

I don't just build websites. I solve engineering problems.

  • 01

    Payments / Identity / Risk

    Production payments, identity verification, fraud detection and compliance — with provider abstraction and failover when vendors fail or change state.

    • Six payment providers
    • Socure KYC
    • SEON fraud
  • 02

    Legacy Modernization

    Modernize aging applications without throwing away the business logic and data that already work.

    • Codebase discovery
    • API extraction
    • Schema-compatible migration
    Foxlancer case study
  • 03

    AI Transformation

    Introduce LLMs, RAG and automation where they improve a real workflow.

    • LLM integration
    • RAG + pgvector
    • Workflow automation
    AxiomAI case study
  • 04

    eCommerce Engineering

    Build storefronts, APIs, integrations and customer-facing experiences designed around the commerce journey.

    • Shopify & WooCommerce
    • Storefront APIs
    • Commerce integrations
    Sunday Scaries

05Systems thinking

From legacy complexity to production-ready capability.

Modernization isn't one big move. It's a sequence of layers — each one reduces risk and unlocks the next. Select a layer to see what it solves.

What problem it solves

Business rules and years of data live in an aging codebase that nobody wants to touch — so every change is slow and risky.

Typical technologies

  • PHP
  • CodeIgniter
  • ThinkPHP
  • Laravel
  • MySQL

Why the layer matters

It already runs the business. Understanding it first is what prevents a rewrite from quietly dropping behaviour customers rely on.

06Featured work

Production systems across payments, identity, AI, and modernization.

Case studies you can inspect — each card opens a write-up built only from the repository and the public site.

  • AI Infrastructure

    AxiomAI

    One gateway between your applications and OpenAI, Gemini and Anthropic — with routing, failover, cost tracking and grounded retrieval built in.

    • Python 3.12
    • FastAPI
    • Pydantic
    • SQLAlchemy
    • Alembic
  • Legacy Modernization

    Foxlancer

    A Node.js and React rebuild of a CodeIgniter freelancing marketplace that keeps the existing MySQL database and business rules intact.

    • Node.js
    • TypeScript
    • Express
    • mysql2
    • JWT
  • AI Product · Semantic Video

    VidzAI

    An audio/text → visual-story platform that understands meaning, plans scenes, matches assets and renders captioned MP4s with Remotion.

    • React 19
    • TypeScript
    • Vite
    • Express.js
    • Remotion 4
  • AI Product · Media Intelligence

    AdMention AI

    A full-stack platform that takes a YouTube video and an advertiser name and returns timestamped mentions, transcript context and a link that opens at that exact moment.

    • React
    • TypeScript
    • Vite
    • Tailwind CSS
    • Python 3.12
  • AI Product · WordPress

    Vantage SEO

    A WordPress plugin that scans content on publish, scores SEO health and suggests fixes with OpenAI — inside a monthly budget and with human approval.

    • PHP
    • WordPress
    • WooCommerce
    • OpenAI API
    • Google Search Console API
  • AI Product · Lead Generation

    LeadGenie

    A Gemini-powered website chatbot that answers from site context and turns out-of-scope questions into captured leads with instant Telegram alerts.

    • Python
    • Flask
    • Google Gemini
    • Telegram Bot API
    • WSGI
  • AI Product · Browser Extension

    WebSumm-AI

    A Chrome extension and mobile web app that summarizes webpages and YouTube videos with Gemini — right where the reader already is.

    • JavaScript
    • Chrome Extensions (MV3)
    • Google Gemini
    • PWA
    • CSS
  • eCommerce · Shopify

    Sunday Scaries

    Shopify storefront engineering for a live consumer brand — customer-facing commerce work in production.

    • Shopify
    • Liquid
    • JavaScript
    • CSS

07Flagship case study · AxiomAI

A production control plane for AI applications.

One gateway between your applications and OpenAI, Gemini and Anthropic — with routing, failover, cost tracking and grounded retrieval built in.

Designed request path

01 / 06

Application. A client sends a chat request over HTTP. It never talks to a vendor SDK.

Problem

Applications that call LLM vendors directly inherit every vendor's outages, pricing and SDK quirks. Keys leak into services, costs are invisible until the invoice arrives, and there is no single place to enforce limits or ground answers in company knowledge.

Architecture

Applications never talk to model vendors directly. Every request passes a linear, individually testable pipeline before a deterministic router chooses a provider adapter.

Engineering decisions

Modular monolith, not microservices
One engineer can run, test and demo the whole system locally, and requests, usage and cost stay transactionally consistent. Services split only when a real scaling or team boundary appears.
Provider adapters behind one protocol
Routing, cost and auth code never import a vendor SDK, so adding or removing a provider does not touch business logic.
Deterministic routing before any ML router
Predictable, debuggable behaviour comes first. Fallback only runs for errors where retrying elsewhere makes sense — never for invalid requests or content filters.
Pricing as data
Model prices live in a model_pricing table rather than hard-coded rates, so cost per request stays correct when vendors change prices.
Fake providers for tests
80+ pytest cases run against fake chat and embedding providers, so CI never spends live credits and failure paths can be reproduced on demand.

08Modernization story · Foxlancer

Modernizing a legacy marketplace without throwing away the business.

A Node.js and React rebuild of a CodeIgniter freelancing marketplace that keeps the existing MySQL database and business rules intact.

Strangler migration

schema stays · modules move

Existing MySQL. serv_* tables stay. Both stacks read and write the same data.

The approach

A working freelancing marketplace — jobs, bids, hiring, wallets, milestones, escrow and disputes — ran on an aging CodeIgniter codebase. A big-bang rewrite with a new database would put years of data and business rules at risk.

The legacy application is left untouched as the reference implementation. The new stack reads and writes the same MySQL tables, so both can be compared side by side while modules move across.

Engineering decisions

Keep the existing MySQL schema
The data and the rules encoded in it are the business. Reusing the serv_* tables removes a whole class of migration risk and lets the old and new apps run against the same data.
Layered API: routes → controllers → services → repositories
Controllers stay HTTP-only, business rules such as hire status transitions live in services, and SQL against legacy tables is isolated in repositories.
JWT with legacy password compatibility
Users keep their existing credentials: the API verifies legacy password hashes and applies the same account gates, while issuing modern bearer tokens.
Zod validators mirroring legacy messages
Behavioural parity includes the error messages users already know, not just the happy path.
Separate marketplace and admin frontends, one API
Mirrors the legacy split so operational workflows do not change while the stack does.

Migrated to the new stack

  • Auth, profiles, jobs, bids and the hire flow
  • Messages and notifications
  • Wallet, transactions, wire and withdrawal requests
  • Milestones with escrow, release and disputes
  • Memberships, reviews, portfolio and job Q&A
  • Admin: members, projects, finance approvals, CMS and settings

Still in progress

  • Live PayPal IPN
  • Hourly tracker
  • Social login
  • Deeper admin tooling

Gaps are listed in the public migration tracker so progress is not mistaken for completion.

Foxlancer live marketplace homepage
The live legacy marketplace at foxlancer.com — the system being modernized.

09AI application engineering

AI is most useful when it changes a workflow.

Four moves: understand the material, attach it to systems you already run, automate one step, then operate it like production software.

Understand

Ground the model in text that belongs to the business, then retrieve only what the next step needs.

10Engineering capabilities

A stack organized by the job it does.

Not a logo wall. These are the languages, systems and domains that show up in the work above.

  • Backend

    • Python
    • FastAPI
    • Flask
    • PHP
    • Laravel
    • ThinkPHP
    • CodeIgniter
    • Node.js
  • Frontend

    • React
    • Next.js
    • Vue 3
    • TypeScript
    • Tailwind CSS
  • Data

    • PostgreSQL
    • MySQL
    • MongoDB
    • Redis
    • pgvector
  • Infrastructure

    • Docker
    • GitHub Actions
    • Render
  • AI

    • OpenAI
    • Gemini
    • Anthropic
    • RAG
    • Embeddings
    • Vector search
    • Remotion
  • Domains

    • Payments
    • Identity / KYC
    • Fraud
    • Compliance
    • eCommerce
    • Legacy modernization
    • AI infrastructure
    • Semantic video
    • SEO
    • Media intelligence

11How I think

Good engineering starts before the code.

  1. 01

    Don't rewrite what you don't understand.

    The running system is the specification. Read the data and the rules before you replace a line.

    Foxlancer keeps the legacy app as reference
  2. 02

    Don't add AI where it doesn't solve a problem.

    A model earns its place only when it changes a specific workflow — support, content, leads, retrieval.

    LeadGenie turns out-of-scope questions into leads
  3. 03

    Don't ship a feature you can't operate.

    If you cannot see hops, failures and cost, you do not have a product. You have a demo.

    AxiomAI persists usage, cost and every provider hop
  4. 04

    Don't optimize before measuring.

    Search and traffic numbers come from the source system. Models do not invent them.

    Vantage SEO reads Search Console, never generates it
  5. 05

    Don't confuse a prototype with production.

    Fake providers, limits and a human approval step are how a local project stays honest.

    AxiomAI's 80+ pytest cases run on fake providers

12How I work

A sequence, not a big-bang rewrite.

Understand the system, map the seams, modernize behind a contract, add intelligence to one workflow, then operate it.

  1. 01

    Understand

    Read the existing system: the tables, the rules, and the behaviour customers already rely on.

  2. 02

    Map

    Find the seams. Separate what must stay from what can move, module by module.

  3. 03

    Modernize

    Replace one layer at a time behind a stable contract. Keep the database when it is the business.

  4. 04

    Add intelligence

    Attach a model to one workflow, grounded in your data, with a human where judgement matters.

  5. 05

    Operate

    Limits, failover, cost and isolation come before calling it production.

Free resource

13 — AI Transformation Blueprint

From Legacy to AI-Powered

The 7-Step AI Transformation Blueprint

A practical guide for eCommerce teams looking to modernize legacy systems, introduce AI and improve workflows without unnecessary rewrites.

The 7-Step AI Transformation Blueprint by Bharat Kumar Adhikari

14Open source

Code you can inspect.

Public repositories for the systems on this site. Read the case study when you want the decisions; clone the repo when you want the implementation.

  • One gateway between your applications and OpenAI, Gemini and Anthropic — with routing, failover, cost tracking and grounded retrieval built in.

    A local-first control plane: routing, failover, cost tracking and cited retrieval in one place.

    • Python 3.12
    • FastAPI
    • Pydantic
    • SQLAlchemy
    • Alembic
    Case study
  • An audio/text → visual-story platform that understands meaning, plans scenes, matches assets and renders captioned MP4s with Remotion.

    Audio or text becomes a meaning-planned visual story — Remotion renders it, unconfigured providers stay labelled.

    • React 19
    • TypeScript
    • Vite
    • Express.js
    • Remotion 4
    Case study
  • A full-stack platform that takes a YouTube video and an advertiser name and returns timestamped mentions, transcript context and a link that opens at that exact moment.

    Timestamped advertiser mentions in long-form YouTube — captions first, Whisper only if needed.

    • React
    • TypeScript
    • Vite
    • Tailwind CSS
    • Python 3.12
    Case study
  • A WordPress plugin that scans content on publish, scores SEO health and suggests fixes with OpenAI — inside a monthly budget and with human approval.

    AI-assisted SEO inside WordPress — with a monthly budget and a human approval step.

    • PHP
    • WordPress
    • WooCommerce
    • OpenAI API
    • Google Search Console API
    Case study
  • A Chrome extension and mobile web app that summarizes webpages and YouTube videos with Gemini — right where the reader already is.

    Summarization where the reader already is: a Chrome sidebar and a mobile web app.

    • JavaScript
    • Chrome Extensions (MV3)
    • Google Gemini
    • PWA
    • CSS
    Case study
  • A Gemini-powered website chatbot that answers from site context and turns out-of-scope questions into captured leads with instant Telegram alerts.

    Website-grounded answers; out-of-scope questions become captured leads.

    • Python
    • Flask
    • Google Gemini
    • Telegram Bot API
    • WSGI
    Case study
  • A Node.js and React rebuild of a CodeIgniter freelancing marketplace that keeps the existing MySQL database and business rules intact.

    A strangler migration that keeps the existing MySQL schema and business rules.

    • Node.js
    • TypeScript
    • Express
    • mysql2
    • JWT
    Case study
  • A Flask application on PostgreSQL, deployed to Render with render.yaml and runnable locally with Docker Compose.

    A small Flask service whose deployment is described in code.

    • Python
    • Flask
    • PostgreSQL
    • Docker
    • Render
    Case study

15About

Senior Full-Stack Engineer with AI expertise.

11+ years building production platforms across payments, identity verification, fraud detection, e-commerce, and AI — not a single vertical.

I am a full-stack engineer who ships production software, then applies the same reliability patterns to AI. The work lives where money, identity, fraud, storefronts and models meet real business logic.

My work spans the Socure identity verification lifecycle — DocV, ReSelfie, and deposit-threshold gating — SEON fraud detection across five transaction types, and integrations with six payment providers: Stripe, Breeze, Checkbook/ACH, AptPay, Fiserv DDP, and Prizeout.

Production depth

  • Identity

    Socure verification lifecycle

    DocV, ReSelfie, and deposit-threshold gating — the checks that decide whether a person can move money.

  • Fraud

    SEON across five transaction types

    Fraud signals wired into the transaction path, not a dashboard sitting beside it.

  • Payments

    Six providers, one abstraction

    Stripe, Breeze, Checkbook/ACH, AptPay, Fiserv DDP, and Prizeout — routed so a vendor outage does not freeze the product.

Core stack

  • Python
  • FastAPI
  • Flask
  • PHP
  • ThinkPHP
  • Node.js
  • Vue 3
  • React
  • TypeScript
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Docker
  • GitHub Actions
  • LLMs
  • RAG

What I bring

Not an AI researcher. Not a prompt engineer.

What differentiates me is the combination of production depth in payments, KYC/identity verification, fraud, and transaction systems with hands-on experience building and deploying AI applications and LLM infrastructure.

I'm an engineer who builds systems where AI meets real-world business logic, integrations, compliance, and reliability.

Build intelligent systems. Engineer for reliability. Design for scale. Ship for real-world impact.

Full story
Portrait of Bharat Kumar Adhikari

16Contact

Have a complex system to modernize?

Let's understand the problem first, then choose the technology.

Email bk.digitalservice@gmail.comPhone +91 98309 82129