hegl for fintech

Handle more cases without adding more reviewers.

hegl runs the case work your team does by hand, on top of the systems you already use.

Book a demo

Onboard your agent

Claude Code

/plugin marketplace add Katch-AI/hegl-plugin
/plugin install hegl

Codex

codex plugin marketplace add Katch-AI/hegl-plugin

Then install hegl from /plugins. Codex asks you to authorize it in your browser on first use.

Quick start

Start with "list my Hegl organizations", then:

/hegl:build [agent]
Start building an agent, or pick up where the build stopped.

/hegl:feedback [agent]
See what people complained about and improve the agent on it.

/hegl:fix-errors [agent]
Find out why runs are failing and fix it.

In Codex and OpenCode, ask in words, e.g. "fix the errors on my agent".

Any other MCP client: add the MCP server https://app.hegl.ai/mcp
Read the full guide
  • Works with the systems and data sources you already run
  • Tested on cases you already closed before it touches a live one
  • Escalates to a person when it is not sure, and logs every decision

Use cases

What fintech teams run through hegl

Fintech runs on cases. An application, an alert, a dispute, an exception. Each has a policy behind it and a judgment call in front of it. hegl handles the ones that follow the pattern and brings a person the rest.

Onboarding and verification review

Documents, checks and data read together before anyone decides.

hegl assembles the case, applies your policy, and drafts the decision with reasons.

Credit and underwriting support

Applications with income, bank and business documents behind them.

hegl reads them and hands whoever signs off a completed file.

Fraud and AML alert triage

Alerts that mostly clear, each needing a written disposition.

hegl does the first pass and escalates the ones that need a person.

Disputes and chargebacks

Evidence assembled against a deadline, in a format the other side accepts.

hegl builds the response from your records and routes it for approval.

Exceptions and reconciliation

Settlements, payouts and ledger items that do not match.

hegl clears the routine ones and brings you the rest, work attached.

Periodic review and refresh

Scheduled re-verification across a book of customers or partners.

hegl runs the cycle and surfaces only what changed.

Complaints and regulated correspondence

Responses that must be accurate, on time and on the record.

hegl drafts from the account history. A named person approves.

Support with account context

Requests that need a lookup and a policy call before anyone answers.

hegl resolves what fits policy and routes the rest with context.

  • Document review
  • Sanctions hit review
  • UBO tracing
  • Income verification
  • Bank statement reads
  • Adverse media
  • Reason-code matching
  • Case narratives
  • Policy exception memos
  • Refund decisions
  • Limit changes
  • Duplicate account checks
  • Payout holds
  • Settlement breaks
  • Audit evidence pulls

Your systems

Nothing to rip out

hegl runs on top of your case tool, your email, your document storage, your data sources. Nothing moves and nothing gets replaced.

No migration.

Your data stays in your systems. hegl reads and writes through the access you approve.

No engineers.

An operations lead describes the work. We connect the systems with you on a call.

No new vendor to replace.

hegl works with the checks, data and tools you already pay for.

The fit

Why this work fits

Same path every case. A different catch every case.

Cases follow the same route from open to closed. What changes is the thing that does not fit policy cleanly. Software could always handle the route. hegl learns the catch from your team, one case at a time.

Your policy is written down. Your judgment is not.

The manual covers the standard case. Your most experienced reviewer covers the rest. hegl captures that judgment and turns it into behavior you keep.

You already have the answer key.

Every closed case is a worked example with a known outcome. hegl is tested against them before it goes live and after every change.

When it is unsure

What happens when it is wrong

It asks.

When a case does not match what it has seen, it stops and asks the person who owns it. It does not guess.

It remembers.

Every answer becomes a permanent test. Accuracy goes up with use, not down.

It shows its work.

Every decision carries its inputs, its reasoning, and who overrode what. The audit trail is built in.

Proof

Support and refund handling at Enhancv

Enhancv
I built an automation that handles refund tickets in an afternoon without pulling engineers off the roadmap. What used to be handled by 1 FTE is now done in a couple of minutes.
Volen Vulkov, Co-founder at Enhancv
Volen VulkovCo-founder @ Enhancv

80%+

of refund requests
auto-resolved

30h+

saved every month
for the team

Getting started

How you start

  1. Describe the work.

    An ops lead talks the workflow through. hegl writes the spec.

  2. Test on your files.

    hegl runs against cases you already closed. You see where it agrees with your reviewers.

  3. Go live on your call.

    It runs alongside your team, escalating when unsure. You widen it when ready.

FAQ

Frequently Asked Questions

No. It works with the results those tools return, handling the reading, chasing, writing and routing that comes after.

The reasoning that runs your organization
should be an asset you own.