integrations
AI Agents for Unit Banking Operations
How fintech ops teams use AI agents on Unit: KYC and KYB application reviews, ACH returns and payment reviews, card authorizations, disputes, and account freezes, with read-only tokens and approvals.
AI agents can take the investigation work on a Unit embedded banking program: reviewing applications stuck in AwaitingDocuments or PendingReview, explaining ACH returns and payments held for review, answering card decline questions, tracking disputes, and preparing account freeze or close decisions. They read through Unit's API and webhooks with a read-only token and hand a person a drafted action to approve. Runtime is the AI agent harness for payment and fintech teams, and it is where those agents run with guardrails and a full record.
Unit, at unit.co, calls itself a financial infrastructure platform: accounts and wallets, money movement, card issuing, and capital on its own ledger, with banking services from partner banks. Who does which ops job depends on your model. On Unit's Managed Solutions, Unit operates compliance, fraud, disputes, and end-customer support. On the Unit Platform, more of that sits with your team and your bank. This guide is for the work that sits with you.
The ops work on Unit that agents can take
| Queue | What the agent does | What stays human |
|---|---|---|
| Applications (KYC/KYB) | Reads AwaitingDocuments and PendingReview applications, lists missing or rejected documents, drafts the customer request | Approving, denying, or canceling an application |
| ACH returns and received payments | Traces a returned or dishonored ACH, received payments marked for return, and the account balance impact; drafts the customer reply | Returning, advancing, or reprocessing a payment |
| Payments in review | Explains why an originated ACH went to PendingReview (for example, over the soft daily limit) and gathers context for the reviewer | Releasing or canceling the payment |
| Card authorizations | Explains a decline: your programmatic authorization response, a 2-second timeout, card status, or account status | Changing authorization logic or limits |
| Disputes | Tracks dispute status (InvestigationStarted through ResolvedWon or ResolvedLost) and keeps the customer updated | Any decision on the dispute outcome |
| Account and card actions | Assembles the fraud or bank-request evidence behind a freeze, close, or lost and stolen report | Freezing, closing, or reopening the account or card |
| Partner bank requests | Pulls transactions, statements, and application history the bank asked for | Sending the response to the bank |
How agents connect to Unit
API. Applications, customers, accounts, cards, authorizations, payments, received payments, check deposits, stop payments, disputes, and statements are API resources, following JSON:API. Unit publishes an OpenAPI spec, Postman collections, and SDKs.
Webhooks. Unit signs webhook payloads with HMAC-SHA1 in the X-Unit-Signature header and publishes its sending IPs. In at-least-once mode, events are batched and retried with backoff, so an agent should dedupe on the event ID. Application, document, card, payment, and dispute events let an agent start work the moment a case appears.
Statements and reports. Unit generates monthly statements for deposit accounts as HTML or PDF, which agents can pull when a customer or bank asks for records.
Sandbox. Unit's sandbox is described as a full replica of production, with simulation endpoints for approving applications, card purchases, ACH clearing, check deposits, wires, and dispute outcomes. Every workflow should be built and tested there first.
Browser. For tasks only available in the Unit Dashboard, an agent can use a dedicated login with limited access.
Least privilege. Unit org API tokens take explicit scopes, with separate read and write scopes per resource, an expiration, an optional source IP allowlist, and optional limits to specific accounts, cards, or payments. Give each agent its own token with read scopes only. Scopes that move money are marked sensitive, and they should stay off agent tokens until a workflow has an approval step in front of it. Unit does not publish an MCP server today.
Workflow: application review
Find every business application that has been in AwaitingDocuments or PendingReview for more than two business days. For each, list which documents are missing, rejected, or pending, and what the evaluation flags say. Draft a short, plain-language request to the customer for what's missing. Don't approve, deny, or cancel anything; post the list to #onboarding.
Workflow: ACH return investigation
A customer says $2,400 disappeared from their account. Check for returned or dishonored ACH transactions on their account in the last 10 days, any received payments marked for return, and the current balance. Explain what happened in plain language, with the return reason, and draft our reply. If the account is now negative, flag it for the risk team. Don't move any money.
Workflow: partner bank request
Our partner bank asked for the account opening details, last three statements, and all wires over $10,000 for this business customer. Gather them from Unit, summarize the account activity in one paragraph, and put the package in the bank-requests folder for review. Don't send anything to the bank.
Guardrails
- Read-only tokens. Agents start with read scopes only, an expiration, and a source IP allowlist.
- Approvals before anything changes. Approving applications, freezing or closing accounts, returning payments, and sending wires wait for a named approver. Unit notes wires are final and cannot be disputed.
- Know who owns the decision. On Managed Solutions, Unit handles disputes, fraud, and compliance; on the Unit Platform, your contract decides what is yours, Unit's, or the bank's. Agents prepare work only for the owner.
- No SSNs or card numbers in prompts or logs. Strip them from what the agent sees.
- Record every run. Keep the trigger, every API call, the evidence, the approval, and the result, so the bank can see how a case was handled.
Where Runtime enters the picture
Unit runs the banking infrastructure. It doesn't run your team's investigations across the rest of your stack. An ACH return on a Unit account touches support (the customer), ops (the payment), finance (the negative balance and the recon line), and compliance (whether the pattern needs review, and what the bank asks next). Runtime is the AI agent harness for payment and fintech teams: one agent works the case across Unit, your help desk, and your internal systems, and every team sees the same record. Runtime has no official Unit integration or partnership; agents use Unit's public API, webhooks, and Dashboard with tokens you control.
- No single vendor to depend on. Agent computers run in your AWS, GCP, or Azure account or fully self-hosted, on the sandbox provider you choose, with Claude, GPT, Gemini, or open-weight models and harness routing across Claude Code, Codex, and OpenCode, with fallbacks when a provider goes down.
- Guardrails you set. Agents start read-only, freezing an account or returning a payment waits for approval, access follows roles, credentials are masked, SSNs and card numbers are stripped, and every run is recorded for your partner bank or examiner.
- Built for teams. Ops, support, finance, risk, and compliance share agents, templates, and one memory, so a return and the ticket behind it are worked once.
- An engineer, not an account executive. A forward-deployed AI engineer who built payment infrastructure at Hulu's payments team at Disney, Finix, Modern Treasury, and BlackRock maps your Unit queues and 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
A realistic timeline
| Stage | Time |
|---|---|
| First read-only agent against the Unit sandbox | Minutes on Runtime; days if you build the infrastructure yourself |
| Application review agent on production, read-only | One to two weeks, mostly agreeing on the request templates |
| ACH return and decline investigations answering tickets | Two to three weeks, including the reply review loop |
| Partner bank request packages | Two to four weeks, depending on which systems hold the history |
| Write actions behind approvals | After the read-only versions have earned the team's trust |
Frequently asked questions
Can AI agents work with Unit?
Yes. Unit exposes a JSON:API REST API, signed webhooks, statements, and a sandbox that simulates applications, cards, ACH, checks, wires, and disputes. An agent with a scoped token can read applications, accounts, payments, cards, and disputes, then draft the next step for a person to approve. Runtime is the AI agent harness for payment and fintech teams that runs those agents with approvals and an audit trail.
Does Unit have an MCP server?
We found no MCP server or AI agent tooling published by Unit as of October 2026. Agents connect through Unit's API, webhooks, and Dashboard instead. Unit's docs do offer a Copy for LLM button on each page, which helps when building an agent.
Can I give an agent a read-only Unit token?
Yes. Unit org API tokens take a list of scopes, and each resource has separate read and write scopes, so a token with only read scopes is read-only. Tokens also support an expiration, a source IP allowlist, and limits to specific resources. Scopes that move money are marked sensitive.
Is Unit still operating in 2026?
Yes. Unit describes itself as a financial infrastructure platform, not a bank, with banking services provided by partner banks. It offers the Unit Platform (APIs and components) and Managed Solutions for Banking and Bill Pay, where Unit operates compliance, fraud, disputes, and end-customer support.
Where does Runtime fit next to Unit?
Unit is the banking infrastructure and ledger behind your product. Runtime is where your ops team builds and runs agents that work Unit queues alongside your help desk, internal systems, and partner bank requests, read-only by default, with approvals before money moves and a record of every run. Runtime does not have a native Unit integration; agents use Unit's public API, webhooks, and Dashboard.
Put an agent on your Unit queues
Start with one queue, like application reviews or ACH returns. Runtime runs the agent read-only, in your cloud, with approvals before anything changes. Spin one up yourself, or talk with the founders about your program.