Speed
Fintech
Bank Deposit Guardian
Real-time monitoring, alerting & analytics for bank virtual-account deposits.
THE CHALLENGE
Not Available
Fintechs issuing customer-dedicated virtual bank accounts receive ACH, wire and RTP deposits from many providers, each with its own webhook shape. Ops teams had no unified view: deposits landed in raw provider dashboards or JSON logs, reconciliation was manual, and suspicious activity (large deposits, duplicates, failed rails, unverified microdeposits) was only caught days later — if at all.
Who was affected
Ops & reconciliation analysts (daily manual work), compliance (delayed anomaly detection), finance (slow fee reconciliation), and end customers (funds visibility delays).
Previous process
Provider dashboards + exported CSVs merged in spreadsheets, ad-hoc SQL against raw webhook logs, Slack pings for anomalies, and manual KYC cross-referencing in a separate Sumsub console.
Cost of the problem
~15–20 analyst hours/week on reconciliation, 24–72h detection lag on failed/duplicate deposits, and recurring fee-leakage from unreconciled provider charges.
The solution
Not Available
Bank Deposit Guardian ingests every provider webhook through a single public edge function, stores the raw payload, and derives a normalized deposit stream the whole app is built on. Ops see a live dashboard of KPIs, rail mix and anomalies; analysts filter and drill into any deposit with the raw envelope one click away. Configurable alert rules (large, duplicate, failed, velocity) run server-side, microdeposit verification is tracked per bank account, and a KYC-enriched analytics view breaks deposits down by depositor age, country and status. Admins manage users, roles and raw webhooks; everything is protected by row-level security.
Key features
Integrations & tech stack
The platform is built on a modern React + TypeScript frontend, a Lovable Cloud backend with Postgres and RLS, and edge functions for secure, advisory-locked operations.
Frontend
React + Vite + TypeScript + Tailwind + shadcn/ui, Recharts, Lovable Cloud (Postgres, Auth, Storage, Edge Functions), Sumsub KYC API, provider webhook ingestion (ACH / WIRE / RTP), Google OAuth
Backend
Not Available, Not Available, Not Available, Not Available,
Integrations
Not Available, Not Available, Not Available, Not Available,
A single raw-first data model
Not Avilable
the app never assumes a provider schema. One receive-deposit edge function stores the raw JSON envelope, and every page (deposits, virtual accounts, customers, microdeposits, reconciliation, analytics) is derived on the fly via typed hooks. Adding a new bank provider is a payload-mapping change, not a schema migration.
Not Avilable
Provider dashboards + exported CSVs merged in spreadsheets, ad-hoc SQL against raw webhook logs, Slack pings for anomalies, and manual KYC cross-referencing in a separate Sumsub console.
Not Avilable
the app never assumes a provider schema. One receive-deposit edge function stores the raw JSON envelope, and every page (deposits, virtual accounts, customers, microdeposits, reconciliation, analytics) is derived on the fly via typed hooks. Adding a new bank provider is a payload-mapping change, not a schema migration.
Results & Impact
-