What it sells
The AI agent harness for payment teams
Business model breakdown
Buyer: who owns the budget?
Payment operations, risk, compliance and engineering leaders at payment companies and fintechs (payfacs, ISOs, processors).
Trigger: what makes them buy now?
AI rollouts stall between demo and first real queue; ops queues like chargebacks (e.g. VAMP dispute ratio thresholds) and bank RFIs need scalable handling.
Workflow: what inputs become what output?
Build agents from a prompt, give them tools (email, ledger, SFTP), deploy in Slack/Teams/email/SMS/voice; agents work queues such as RFIs, disputes and underwriting reviews with human approval before acting, and an audit trail.
Economics: what it saves and how it charges
UnverifiedEnterprise platform plus embedded engineering rollout and ongoing AI ops partnership; no prices published.
Distribution: how it reaches customers
Demo-led enterprise sales with forward-deployed AI engineers (no account executives); deploy in Runtime cloud, customer cloud (recommended for PCI) or self-hosted via Helm.
Funding history and coverage
| Round date | Stage | Amount | Investors | Source |
|---|---|---|---|---|
| — | Y Combinator Spring 2026 | — | Y Combinator | ycombinator.com |
Profiles summarize public reporting and company websites. Business-model notes are MaxBC's reading of that material, not confirmed facts; unknowns are left blank rather than guessed. Updated 2026-10-12.