Runtime vs Casap
Casap is an agentic disputes, fraud, and collections platform for banks and credit unions. Runtime is an AI agent harness for banks, credit unions, and payment teams that runs in your cloud. Runtime vs Casap: where each fits, and how to choose.
TL;DR
Casap is the stronger choice for a bank, credit union, or fintech that wants opinionated, prebuilt dispute workflows that work the same way for every institution, with core banking integrations and the option of Casap's team running the queue. Runtime is the better fit for banks, credit unions, and fintechs that want agents built around their own procedures, running in their own cloud, across disputes, fraud, collections, compliance, and member or customer support.
| Feature |  Runtime |  Casap |
|---|---|---|
| What it is | RuntimeAgent harness for payment teams | CasapPackaged dispute, fraud, and collections agents |
| Reg E, Reg Z, and network dispute rules | RuntimeEncoded from your procedure | CasapBuilt in |
| Core and digital banking integrations | RuntimeAny API, database, file, or browser | CasapFiserv, FIS, Jack Henry, Q2, Alkami, Galileo, and more |
| Managed service option | RuntimeForward-deployed engineer builds with your team | CasapCasap staff can run intake and investigation |
| Workflows | RuntimeBuilt from your SOPs, changed when your procedure changes | CasapOpinionated and prebuilt, the same for every institution |
| Channels | RuntimeVoice, SMS, email, chat, Slack, Teams, and the dashboard | CasapVoice, text, and email for collections; digital dispute intake |
| Workflows beyond consumer disputes | RuntimeReconciliation, payouts, KYB, merchant risk, support, compliance | CasapFraud, collections, claims, account opening |
| Runs in your cloud | RuntimeYes, AWS, GCP, Azure, or self-hosted | CasapHosted by Casap |
| Who owns the agent logic | RuntimeYou: skills and scripts live in your repo | CasapCasap, configured to your policy |
| Bring your own models | RuntimeAny model, including open-weight | CasapNot published |
| Pricing | RuntimeBy request; free pilot for approved teams | CasapNot published |
Casap is an agentic disputes, fraud, and collections platform for banks and credit unions. It is the stronger choice if you want opinionated, prebuilt dispute workflows that work the same way for every institution, with core banking integrations already built and the option of Casap's own team working the queue. Runtime is the AI agent harness for banks, credit unions, fintechs, and payment teams: you build and own the agents from your own procedures, they run in your cloud, and they reach customers and members by voice, SMS, and email as well as your team in Slack, Teams, and the dashboard.
We make Runtime, so weigh our view accordingly. Casap facts come from casap.ai, its API docs, and its funding announcements as of November 2026.
Casap and Runtime at a glance
Casap calls itself "the agentic AI platform built to tackle the hardest work in financial services." It started with disputes and covers the full cycle: intake, investigation, provisional credit, chargeback filing, decisioning, and customer letters, with Reg E, Reg Z, NACHA, and card network rules built in. It also lists fraud investigations across cards, checks, ACH, and wires, collections outreach, insurance claims, and account opening. Institutions choose "Autopilot" or "Copilot" autonomy, or have Casap's team handle intake and investigation. It integrates with Fiserv, FIS, Jack Henry, Galileo, Q2, Alkami, Corelation, Visa, and Mastercard, among others. Casap raised a $56M Series B led by Base10 in October 2026, about $90M in total, and names customers including Synchrony, MoneyLion, Unit, and Suncoast Credit Union.
Runtime is one system for building and running many agents across a bank, credit union, fintech, or payment company. Disputes, fraud, collections, compliance, payment ops, and member or customer support turn their SOPs into agents. Agents work on isolated computers in your cloud, reach your tools through APIs, databases, MCP servers, and a browser, talk to customers by voice, SMS, and email, and wait for approval before money moves.
Different shapes. Casap is a dispute product with agents inside. Runtime is the harness your team uses to build the dispute agent, and the next ten.
How they differ
A product versus a harness
Casap ships the dispute logic, the scores, and the letters, configured to your policy. That is fast to adopt if your process looks like its model. Runtime agents are built from your procedure with a forward-deployed AI engineer, and the skills and scripts live in your repo. When your sponsor bank changes a requirement, you change the agent.
Prebuilt workflows versus your workflows
Casap's workflows are opinionated and generic by design: the same dispute flow, scores, and letters for every bank and credit union, configured to your policy. That is the fastest path if your process matches. Runtime suits institutions whose process does not: a credit union with its own member communication rules, a bank with a sponsor-bank program, a fintech whose disputes touch payouts and reconciliation. And the same harness covers BSA and AML reviews, collections, member support, settlement breaks, and KYB.
Hosted versus your cloud
Casap's Dispute API runs on Casap's hosts and tells your systems when to move money. Its site does not describe a customer-cloud or on-premise option. Runtime runs agent computers in your AWS, GCP, or Azure account or self-hosted, with any model, including open-weight models served in your cloud, so card data and account history never leave it.
Managed service versus your team
Casap can run intake and investigation for you, which suits a credit union without dispute staff. Runtime keeps the work with your analysts and makes each of them faster, with a full record of every query, tool call, and approval.
Where Runtime enters the picture
A disputed card charge at a fintech rarely stays a dispute. Support has the customer's messages, payment ops sees the transaction at the processor, finance books the provisional credit and the loss, risk checks whether this is a serial disputer, and the sponsor bank wants the file. A Runtime agent pulls all of it once, computes the Reg E and network deadlines, drafts the determination and the chargeback, and waits for an analyst to approve before credit moves.
- No single vendor to depend on. Multi-cloud, multi-sandbox with fallbacks, and multi-model across Claude, GPT, Gemini, and open-weight models, with harness routing across Claude Code, Codex, and OpenCode.
- Guardrails you set. Read-only by default, approvals before provisional credit, reversals, or letters, RBAC, masked credentials, card numbers and SSNs stripped from prompts and logs, and every run recorded for your examiner.
- Built for teams. Support, payment ops, finance, risk, and compliance share agents, templates, and one memory of every case.
- An engineer, not an account executive. A forward-deployed AI engineer with a payments background builds the first agents with your team.
Create a banking ops agent that handles RFIs, hold-harmless requests, and returns of funds from our partner bank, verifies against our ledger, and drafts replies for my approval.
bank-ops-agent
Tools picked from your prompt
Where Casap is stronger
- Dispute depth. Reg E, Reg Z, NACHA, and network rules, win scores, and first-party fraud scores come built in.
- Core banking integrations. Fiserv, FIS, Jack Henry, Corelation, Q2, Alkami, and other cores and digital banking platforms are already connected.
- Managed option. Casap's team can work the queue, which helps institutions without dispute staff.
- References. Synchrony and Experian invested, and Casap names more than ten banks, credit unions, and fintechs as customers, with published results on handling time and chargeback win rates.
Pricing
Casap: not published; sold through sales.
Runtime: by request, with custom pricing and self-hosting. Approved teams pilot it free on one real workflow first. Rain saved $750k in vendor and salary spend with Runtime, which it uses across technical payment support, fraud and risk transaction monitoring, compliance, cybersecurity, payment operations, engineering investigations, PR reviews, QA testing, and reporting.
Which should you choose
Choose Casap if
- Consumer disputes are the main queue and you want opinionated, prebuilt workflows that work the same for every institution
- You want Reg E and network rules, scores, and letters prebuilt
- You would like a vendor team to run intake and investigation
- Your core is Fiserv, FIS, Jack Henry, or another platform Casap already connects to
Choose Runtime if
- You are a bank, credit union, fintech, or payment company and want agents built around your own procedures
- Disputes are one queue among many: fraud claims, collections, BSA and AML, member support, reconciliation
- Agents should reach members and customers by voice, SMS, and email, not only your staff
- You want to own the agent logic and change it when your procedure changes
- Agents and data must stay in your cloud, with your models
- You want the same harness for reconciliation, payouts, KYB, support, and compliance
Frequently asked questions
What does Casap do?
Casap sells AI agents for financial services, starting with disputes: intake, investigation, provisional credit, chargeback filing, decisioning, and customer letters, with Reg E, Reg Z, NACHA, and card network rules built in. It also lists fraud investigations, collections, insurance claims, and account opening. It raised a $56M Series B led by Base10 in October 2026, with Synchrony and Experian as strategic investors, and names customers such as Synchrony, MoneyLion, Unit, and Suncoast Credit Union.
What are the best Casap alternatives?
Quavo for issuers that want an established dispute platform, FINBOA for credit unions focused on Reg E compliance, Justt or Chargeflow on the merchant side, and Runtime for teams that want to build and own dispute agents in their own cloud alongside other payment ops work. See our full list of Casap alternatives.
Can Runtime handle Reg E disputes?
Yes. A Runtime agent reads the claim, computes the Reg E and card network deadlines, pulls the transaction, authentication, and account history, and drafts the determination and the customer letter. Provisional credit, reversals, and letters wait for an analyst to approve. Our guide on automating Reg E dispute investigations walks through it.
Does Casap run in my own cloud?
Casap's site and API docs describe a hosted service, with SOC 2 and PCI DSS Level 1, and do not mention a customer-cloud or on-premise option. Runtime runs agents in your AWS, GCP, or Azure account, or fully self-hosted.
Is Runtime a fit for credit unions and banks?
Yes. Banks and credit unions use Runtime when they want agents that follow their own procedures and stay in their own cloud: Reg E dispute investigations, fraud claims, collections outreach by voice, SMS, and email, BSA and AML alert reviews, and member support. A forward-deployed AI engineer builds the first agent with your team. Casap fits better if you prefer prebuilt dispute workflows that are the same for every institution.
Is Runtime only for disputes?
No. Runtime is the AI agent harness for payment teams. Teams usually start with one workflow, such as disputes or reconciliation, then add agents for payment support, fraud and risk monitoring, compliance, KYB, and reporting on the same harness.