Runtime as featured inForbesRead the article

The AI agent harness for payment teams

Anyone on your team can securely create AI agents that work like teammates, running in your cloud with your approvals and a full audit trail.

Book a demo
Start for free

Trusted by teams running mission-critical operations.

RainNixtlaMonoLineLeap
Search Payments, Inc.
risk-ops
MRDKPS14 Huddle
MessagesCanvasFiles
Today
MR

Maya 9:12 AM

re-review Harbor Vape Supply, dispute ratio spiked overnight

APP 9:13 AM

Dispute ratio is 1.4%, above the 0.9% VAMP threshold. KYB still matches, but the website changed owners on Sep 22 and 61% of disputes are "not received".

Recommend a 25% rolling reserve. 14 queries, 3 sources.

Approval needed

Apply 25% reserve to Harbor Vape Supply

👀 2🙌 1

DK2 repliesLast reply today

DK

Dev 9:15 AM

Can you check their two sibling MIDs too?

Message #risk-ops

Aa

Digital teammates, built by anyone on your team

Describe the job in plain English. Your agent gets its own computer, inbox, and phone number, follows your procedures, and asks before it acts.

How Runtime works

1

Describe the agent

Anyone on the team can describe a job in plain English. Add your procedures and the points where a person has to approve.

New agent

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.

Describe the agent you want
Agent ready

bank-ops-agent

Tools picked from your prompt

EmailLedgerStripe
2

Connect your existing tools

Give it the systems it needs, with role-based access that sets what each agent and teammate can read and do.

Tools and access · bank-ops-agent

Approved systems and permissions for this agent.

Bank emailRead requests
LedgerRead-only
Returns of fundsNeeds approval

Sensitive actions wait for your team’s approval.

3

Put it to work

Call it from Slack, Teams, email, or phone, or trigger it from an alert or schedule. It works on its own computer and carries out the steps you allow.

Runtime session · bank-ops-agent

Column flagged a transfer on account 4417 and is requesting a return of funds. Can you take it?

Looking into it. Reviewing the request:

Parsedcolumn-rfi-4417.pdf from the bank email
Queriedledger.transactions for account 4417
CheckedKYC file and counterparty history
Scanninglast 90 days for the same pattern

Every step visible while it runs. Cost so far: $0.19

4

Review and approve

Approve sensitive actions and inspect the evidence, activity, and outcome of each run.

Approvals
Money movementNeeds approval

Return $12,400 to the originating bank for the flagged transfer, with a drafted reply to Column and the evidence file attached.

ApproveView run
Run stored with every step, query, and cost
Evidence packet filed for compliance

Run sensitive payment data inside your own cloud

Every agent works on an isolated computer you control, with human approval on the actions that matter.

How we handle security
AuditedSOC 2Compliant

Computers in your cloud

Provision agent computers in your own AWS, GCP, or Azure account, or self-host the whole platform. PCI data stays inside your environment.

Keep card data out of the model

Agents use masked credentials and never see raw secrets. Hooks and filters you configure keep card numbers and PII out of prompts and logs.

Role-based access

SSO for the whole team. Each agent and teammate gets only the tools and data their role allows, and money movement waits for approval.

SOC 2 compliant

Independently audited against the AICPA Trust Services Criteria. Encrypted at rest and in transit. We never train on your data.

A system of intelligence for payment teams

Runtime is the system of record for the work your agents do and the system of action that does it. Every run is stored, and every run makes the next one cheaper and faster.

The request, every query and tool call, the approvals, the cost, and the result. Your agentic system of record, ready when compliance, an auditor, or your partner bank asks.

Run #1047

Re-review Harbor Vape Supply against VAMP thresholds

Tool calls

14

Duration

4m 02s

Cost

$0.31

Pulled 30 days of disputes and KYB records
Found an ownership change on Sep 22
Reserve recommended and approved by Maya

Stored, searchable, and exportable.

Agents learn from resolved cases and propose updates to their own skills, so your runbooks improve as your team works.

merchant-re-review · skill

Learned from the last 40 resolved cases:

Run #983Ownership change preceded dispute spike
Run #1012Reserve approved at 25% for vape MCC
Run #1029Checked sibling MIDs before closing

Suggested skill update

Add step 4: check sibling MIDs before closing a re-review.

Runtime is a neutral provider that works with any model and any harness. Evals find the smallest model that still passes each skill, so you stop paying frontier prices for routine work.

Model routing · last 30 days
Alert enrichmenteval pass 98%
Opus 4.7GLM-5.3 Flash-86%
Dispute evidenceeval pass 96%
Opus 4.7Sonnet 4.6-62%
Merchant re-revieweval pass 97%
Opus 4.7Opus 4.7kept

Cost per run vs. the original model. Illustrative.

Better skills mean fewer steps, smaller models mean fewer dollars, and sandboxes pause when idle and boot from snapshots. See token and compute cost by agent, team, and run.

Agent runsLast 30 days
Runs
1,247
Spend
$2,184
Teams
12
SK
Fix login timeout bug
$0.12
JM
Refund duplicate charge
$0.08
AL
Reconcile Q2 payouts
$0.21
RM
Draft replies for open tickets
$0.04

Every run stored, searchable, and auditable

A partner for your AI agent rollout

Our forward-deployed engineers work with your team to map processes, build the first agents together, and set up guardrails, so your team can build the rest. We’ve built payment infrastructure and AI systems at companies like these.

How we work with payment teams
Modern Treasury
Finix
BlackRock
Y Combinator
Hulu
Yahoo
Berkeley
University of Michigan

Frequently asked questions

Who is Runtime for?
Payment companies on both sides of the transaction: issuers and program managers, acquirers, processors, gateways, ISOs, and payfacs, plus the banks and fintechs that run payment programs. Payment ops, underwriting, risk and fraud, compliance, and support teams use it for case work, and engineering uses the same platform for its own agents.
Does card data or PII ever reach the model provider?
It does not have to. Agent computers can run inside your own cloud account, so PCI data stays in your environment. Agents use masked credentials and never see raw secrets, hooks and filters strip card numbers and SSNs from prompts and logs, and you can serve open-weight models from your own cloud for the most sensitive work.
Can we run Runtime in our own AWS, GCP, or Azure account?
Yes. Most payment teams run agent computers in their own cloud account, set up with Terraform or CloudFormation, while we manage the control plane. Teams that cannot send anything outside their network can self-host the whole platform with a Helm chart. Runtime never needs access to your cloud role.
We already built internal bots. Why not build this ourselves?
Most teams we talk to have tried. The agent is the easy part; the harness around it is not: isolated computers, scoped credentials, role-based access, approvals, an audit trail, evals, and model routing. Runtime gives you that harness so your team spends its time on the agents, and it works with the tools and bots you already have instead of replacing them.
Will it work with our existing and legacy systems?
Yes. Agents reach tools through APIs, CLIs, SDKs, and MCP servers, and can use a browser for internal systems that have no API. Common connections include Salesforce, Splunk, Datadog, Zendesk, Jira, Snowflake, Postgres, and your processor or core banking platform. Agents are called from Slack, Microsoft Teams, email, SMS, or a schedule.
How do approvals and the audit trail work?
You choose the steps that need a person, like applying a reserve, releasing a held payment, or sending a reply to a partner bank. The agent pauses and asks in Slack, Teams, or the dashboard. Every run is recorded end to end: the trigger, every query and tool call, what each returned, the approvals, the cost, and the result. When an auditor or your sponsor bank asks how a case was handled, you export the run.
Which models can we use, and how do you keep costs down?
Runtime is neutral. Use Claude, OpenAI, Gemini, or open-weight models from Bedrock, Vertex AI, or your own cloud, in harnesses like Claude Code, Codex, or OpenCode. Evals test each skill against real cases and route routine work to the smallest model that still passes, and agents reuse what worked before, so each run gets cheaper and faster.
What does a pilot look like?
We start with one SOP, such as transaction-monitoring triage, proof-of-authorization requests, or merchant re-reviews, and agree on the success measure up front. Our forward-deployed engineers build the first agent with your team, set up guardrails with security, and train your admins so your team can build the next ones. Many teams start on non-PCI work, then expand.

See Runtime in action

See how agents work your payment operations and risk queues inside your own cloud, with your team approving what matters.

Book a demo
Start for free