Novaheim AI
Book a discovery callBook a call
Payment Ops Desk · for fintech, payments and stablecoin teams

Every payment break, owned.

Novaheim matches processor, bank, ledger and on-chain records every day, and puts a dollar figure, an owner and a deadline on every exception. Read-only, inside your cloud.

Book a discovery callSee a sample exception summary
  • Runs in your own cloud
  • Read-only keys
  • No custody
  • Card · ACH · Wire · Stablecoin
Background ledger · synthetic data
The problem

Processor, bank and ledger never agree on Monday.

R01 and R10 look alike. Their deadlines don't.

A return lands in the bank feed as a code and an amount. Each code runs on its own clock, and a spreadsheet doesn't keep time.

Nobody owns the unmatched credits

A bank credit with no reference sits in suspense. Without an owner and a due date, it just ages.

Month-end is a week of spreadsheets

Processor, bank, ledger and chain exported and matched by hand. Failed payouts and fee deltas left as unexplained lines.

Your processor's dashboard isn't a reconciliation. When volume grows, a new rail launches, or the person who knows the spreadsheet leaves, breaks age unowned until a deadline passes or the partner bank asks.

The thresholds are on the record. Nacha sets return-rate limits of 0.5% unauthorized, 3% administrative and 15% overall. And since Synapse's trustee estimated a $65–95M shortfall, partner banks ask for ledger detail sooner.

How it works

Code matches. AI explains. Your ops team resolves.

Five steps run every day inside your cloud account. Only the last one needs a person.

  1. 01
    Read-only
    Read-only data
  2. 02
    Code
    Match
  3. 03
    Code
    Classify
  4. 04
    Code + AI
    Route to owner
  5. 05
    Your ops team
    Ops team resolves

The AI never decides a match. It explains only what the rules couldn't, with every record cited, so each exception arrives with a cause, an owner and a due date.

See how we work, stage by stage
Sample exception summary

Every break gets a dollar figure, an owner and a deadline.

$318,420
open across 23 exceptions
17
due in the next 48 hours
23 / 23
exceptions with an owner and a due date
Daily exception summary · Nov 6 · 12,406 records matchedSynthetic
01 · Found
EX-1042 · ACH funding returned R10
Processor
4,820.00 funding settled
Bank
−4,820.00 returned R10
Ledger
4,820.00 still marked funded
Chain
4,820.00 USDC payout sent
At risk$4,820.00
02 · Why

The customer's bank returned the ACH debit as unauthorized after the USDC payout had already gone out. The ledger still shows the funding as good.

↳ Return R10 · trace …4417↳ Payout PO-2291
03 · Owner and fix
Owner
Risk ops
Due
Nov 18

Hold the account, open recovery on the payout, and reverse the funding entry. JE-1042 drafted.

Awaiting ops sign-off
What you get
No break without an ownerDaily

Every exception gets an owner and a due date the day it appears.

No missed deadlineDaily

ACH return windows and dispute evidence dates are watched for you.

A backlog that shrinksMonthly

The dollar backlog readout shows open money by age, every month.

Runs in your cloud · read-only keys · no custody, no way to move money · access you can revoke · AI on your own model endpoint

Getting started

Size it in dollars first. Then a working queue in 10 business days.

01 · Start here

Payment Ops Review

We run last month's data and size every break and exception category in dollars, with a fix plan for each. Credited in full against the build if you go ahead within 30 days.

02 · Then

Build

A working queue in 10 business days. The desk goes live on your data, in your cloud account, from one install template. Connectors built, rules tuned, and an owner and due date set for every exception type.

03 · Every month

Monthly desk

A named person keeps it tuned: connectors kept current as processors, banks and chains change, rules updated, and the dollar backlog readout every month.

What we need from you: read-only keys for your processor and bank feed, ledger and ERP read access, wallet addresses if you pay out in stablecoins, one approved cloud account and one hour with your engineer. No platform migration.

Built for teams with three or more money sources or rails, breaks worked in spreadsheets, and no payment ops engineer. Not for a single processor at low volume, teams with their own data engineering, or anyone who needs Novaheim to move, approve or release money.

Named commitment

The 3-Break Review

If the Payment Ops Review doesn't size at least three break or exception categories in dollars, each with a fix plan, the review fee is refunded in full.

Named commitment

The 10-Day Start

If the desk isn't producing a working exception queue within 10 business days of read-only access, the first month of the retainer is free.

Named commitment

The 2-Day Fix

If a connector breaks and we haven't restored it within 2 business days of being told, that month's retainer is credited.

Prefer someone to run it with your team for six months? Ask about the Embedded Desk.

Book a discovery callSee how it works
Two new reviews a month
FAQ

Questions ops, finance and security ask first.

Anything not answered here is what the discovery call is for.

Bradley Behan
Founder · Novaheim

Bradley builds every desk and is the named person who keeps yours tuned each month.

Does our data leave our cloud?
No. The desk runs inside your own cloud account. Data, keys and readouts stay there. Novaheim hosts nothing and holds no copy; we see only job-health metadata, such as whether a run finished and how many exceptions it found.
What access do you need?
Read-only API keys for your processor, bank feed, ledger and ERP, plus chain data if you pay out in stablecoins, created in your name and stored in your secrets manager. Plus a scoped, logged maintenance role you can revoke at any time. No custody, and no way to move money.
Does AI decide what gets matched or posted?
No. Fixed rules do every match. The model only explains the exceptions the rules couldn't, and drafts a journal entry for review. Your team resolves and posts every one.
We already have reconciliation software. Why this?
Most platforms need a migration and still leave the exceptions to a spreadsheet. The desk works on the systems you already run, covers card, ACH, wire and stablecoin in one view, and a named person keeps it tuned every month.
Why not hire a payment ops engineer?
A hire still needs tools, and when they leave the knowledge goes with them. The desk runs on code in your account. If you want a person too, ask about the Embedded Desk: six months inside your team, then handed over.
Which rails and systems do you support?
Card processors, ACH and wire through your bank feed, and stablecoin payouts on major chains. Your specific processors, banks and ledger are confirmed during the payment ops review.
Do you make Nacha, BSA/AML or accounting calls?
No. The desk tracks return rates and deadlines so your team sees them early. Your team and your partner bank make every one of those decisions. We are not a CPA firm or a law firm, and we give no legal, tax or accounting opinions.

Have the answer before the partner bank asks.

Start with a payment ops review on last month's data. You'll see at least three break categories in dollars, each with an owner and a fix plan.

Three founding clients lock their terms for 12 months in exchange for a case study and a reference call. Slots close January 15, 2027.

Book a discovery call