Loading
KYC exceptions and payment repairs on Temporal + Vercel AI SDK + MCP — maker-checker Signals, PII redaction, zero double-posts on core retries.
The Problem
A mid-market bank’s payments and onboarding ops drowned in exception queues. Analysts toggled core banking, payment hub, KYC vault, and email for each case. Retries after timeouts sometimes double-posted repairs. Checker sign-off lived in Slack screenshots.
The Solution
We shipped an Intake / Case / Control / Judge AI ops layer: Vercel AI SDK for structured intents, MCP tools into bank systems as Temporal Activities, and maker-checker as durable Signals before any live post or customer outbound.
The brief was queue clearance with dual control — not FAQs. Models classify and draft; Temporal owns durability; MCP owns the allowlist into CBS, payment hub, and KYC store. Money moves only after a checker Signal.
Intake Workflow turns queue events into typed intents. Case Workflow runs the durable agent loop via Vercel AI SDK. Write tools stage then submit. Control waits on maker_approved / rejected Signals mapped to bank IAM roles. Judge samples weekly for misclassification and override rates.
Activities redact PAN / government IDs before LLM calls. Full payloads stay in an encrypted case store in-region. Model path is VPC-routed where policy requires — no customer data used for training.
A failed outward remittance now yields a staged repair with fail-code rationale and evidence links. Checker approves in the bank UI. Crash mid-retry no longer duplicates the post. KYC gaps assemble into a policy-cited pack the officer can send after approval.
Business Impact
Ops owns speed; compliance owns evidence. Every write carries a Temporal history plus tool I/O digest Internal Audit can replay. Analysts review staged repairs and KYC gap packs instead of rebuilding the case from scratch.
Technical architecture write-upTech Stack
No. stage_payment_repair created proposals only. submit_payment_repair required a checker Signal above policy thresholds. Read tools ran ungated.
Temporal workflow history plus redacted tool digests export as the case file. Policy versions returned by fetch_policy_clause include document id and effective date.
Yes. MCP open_service_ticket writes into the bank’s ITSM or case system. We do not force a rip-and-replace of the case manager on day one.
Crypto / FinTech
Durable AI Ops Layer on Multi-Venue Exchanges
Desk copilots that turn natural-language intent into HITL-approved exchange orders — Vercel AI SDK, Temporal, and MCP — without YOLO trading bots.
Banking / FinTech
Conversational Rules Engine for Crypto↔Fiat Banking
Users set salary-day and balance rules in chat; Temporal workflows execute convert → transfer recipes with confirm cards and zero double-pays on webhook retries.
Insurance
Claims Intake Routing & Data Extraction
FNOL packs auto-classified and routed — adjusters cut intake from ~45 minutes to ~5–8 on standard claims.