---
title: "Banking"
description: "Drex scores fraud alerts, suggests dispute reason codes and routes requests inside your network, so analysts start with the riskiest cases. Document Processing extracts the onboarding and credit files behind them."
canonical: "https://nace.ai/industries/banking"
updated: 2026-11-06
---

# Banking

> Drex scores fraud alerts, suggests dispute reason codes and routes requests inside your network, so analysts start with the riskiest cases. Document Processing extracts the onboarding and credit files behind them.

## Fraud alerts, disputes and requests, scored and routed.

Drex scores fraud alerts, suggests dispute reason codes and routes requests inside your network, so analysts start with the riskiest cases. Document Processing extracts the onboarding and credit files behind them.

Runs on: Drex (decides), Document Processing (reads).

| Value | Result | Source |
| --- | --- | --- |
| 90.0 | on BANKING77, routing requests to 77 intents. Jev 1.14: 79.7 | [Drex benchmarks](https://nace.ai/drex) |
| 85.7% | accuracy on 3,361 held-out finance decisions. Jev 1.14: 76.7% | [Drex for Finance](https://nace.ai/drex/finance) |
| <200 ms | model latency per decision, not end-to-end workflow time | [Drex benchmarks](https://nace.ai/drex) |

Trusted by: Mountain America Credit Union, Prosper.

## Analysts spend the day on alerts that turn out to be nothing.

Fraud queues, chargebacks and inbound requests grow faster than headcount. Drex scores each case with a probability you can set thresholds on, so analysts start with the cases that matter.

## Where Nace fits

Each workflow names the model that does the work.

| Workflow | What it does | Model |
| --- | --- | --- |
| Fraud alert scoring | Every alert scored on a risk scale you define, so the riskiest cases are worked first. | Drex |
| Dispute triage | A suggested chargeback reason from your list, and a score for whether the case needs a person. | Drex + Document Processing |
| Request routing | Each message classified by intent and routed to the right team. | Drex |
| Credit risk banding | Each applicant placed in a risk band from the file, with the spread across bands. | Drex + Document Processing |
| KYC and onboarding | IDs, articles and ownership forms extracted, each value tied to its page. | Document Processing |
| Back-office automation | Drex Max reads core banking and portal screens and picks the next click. | Drex |

## Card dispute, end to end

1. Dispute in: Customer claim and evidence
2. Document Processing reads: Receipts, statements and letters
3. Drex decides: Reason code and next step
4. Your analysts: Works only contested cases
5. Drex for Search finds: Any past dispute, cited to its page

What it reads: Account opening forms, Government IDs, Articles of incorporation, Beneficial ownership forms, Business financials, Tax returns, Dispute evidence, Scanned checks.

## Runs where your data already lives.

Same models and the same API at every tier. Only the boundary around your data changes.

- Managed Cloud: Our GPUs, our API, a key from Console.
- Dedicated Cloud: Your own cluster in our cloud, reached over private links.
- Your Cloud: Installs in your AWS or Azure account. Data stays inside.
- On-Prem & Air-Gapped: Your datacenter, your hardware, zero outbound.

SOC 2 Type II audited. [Visit the Trust Center](https://trust.nace.ai).

## See it on your own files.

Send us a file and the decision you make on it. We'll show you the result on your own documents.

- [Get started](https://console.nace.ai/?utm_campaign=industries&utm_content=industry-banking_md&utm_medium=website&utm_source=nace.ai)
- [Talk to sales](https://nace.ai/contact?source=industry-banking)

Related industries: [Insurance](https://nace.ai/industries/insurance) · [Mortgage lending](https://nace.ai/industries/mortgage-lending) · [Accounting](https://nace.ai/industries/accounting)

## For agents

- [Drex API guide](https://nace.ai/drex.md): the decision model: request shape, question types, benchmarks and deployment, as markdown
- [Decision endpoint](https://console.nace.ai/v1/systemone): POST with model "drex-latest", a state string and typed questions (choice, noul, score); https://console.nace.ai/v1/models lists checkpoints
- [Document endpoints](https://console.nace.ai/v1/documents/{parse|split|classify|extract|ground}): POST a source (a public URL, an uploaded workspace file or a finished parse job) and poll GET https://console.nace.ai/v1/documents/jobs/{id}; the same key and credit as decisions
- [Console](https://console.nace.ai): API keys, the playground, usage and billing; send `Authorization: Bearer $NACE_API_KEY` on every request
- [Console docs](https://console.nace.ai/docs): quickstart, question types, the document routes, errors, limits and pricing
- [Nace Document Processing](https://nace.ai/perception.md): the Perception series: parse, split, classify, extract and ground any file type with a location on every value
- [Drex for Search](https://nace.ai/drex/search.md): Drex for Search: decision-powered retrieval for agents, Drex finds the page, cited search through the CLI, SDKs, MCP and REST, and the public benchmark ranks
- [Industries](https://nace.ai/industries.md): Nace by industry: the files Document Processing reads and the decisions Drex makes for accounting, banking, mortgage, insurance, legal, healthcare, government, construction, logistics and professional services
- [Developers](https://nace.ai/developers.md): The execution layer for agents: Perception, Decision and Search behind one key, the Drex Max frontier, install steps, a scripted agent session and the four deployment boundaries
- [Site index](https://nace.ai/llms.txt): every page on nace.ai; append `.md` to any page URL or send `Accept: text/markdown` for the markdown version
