Sent€0.000 payments recorded

Waiting for you0Changed details held for a person

Refused attempts0Payments the approval did not cover

Agent runs0Invoices the agent handled

Take the walkthroughFive steps, about a minute: a supplier changes bank details, and you decide.

What happened to each payment

Every run in this workspace, by outcome

Show as a table

Money moved and held back

Simulated euros: sent after approval, against payments refused or still waiting

Show as a table

Needs your decision

Recent runs

All runs

Payments the agent wanted to make that its approval did not cover. Approve the exact amount and account, or decline.

Every invoice the agent has handled, newest first.

Payments the executor recorded. Each uses one approval once.

Exact match

A payment runs only if supplier, account, amount and currency equal an approval.

Changed details wait for a person

A new account, a new amount or a new supplier is held for review. The agent keeps working on everything else.

One approval, one payment

An approval is used once. A retry or replay of a paid invoice is refused.

The agent proposes, it cannot approve

The agent reads documents and calls tools. Approval comes only from the review screen.

What this workspace stores, what the agent can do, and what it cannot.

Synthetic data only

Suppliers, invoices, accounts and amounts are made up. Do not enter real names, account numbers or codes.

No real money moves

Payments are rows in a simulated ledger. No bank or payment service is connected.

Keys stay on the server

The model provider key is never sent to the browser, and replies are checked so the key cannot be echoed back.

The agent cannot approve

It reads documents and proposes payments. Approval needs the review screen, a session cookie the page cannot read, and your confirmation of the exact values. The review screen does not verify who you are.

What is stored

Runs and their events sit in one database on the server. Model traces are held in memory only. Sample photos are fixed files; nothing you upload is kept.

Strict browser rules

No third-party scripts, analytics or trackers. A content security policy limits the page to its own files. The only cookie is the review session.

AI acts. Keep the receipt.

Your agents already prepare payments, refunds and record changes. Seal checks each action against what a person approved, before it runs, and keeps a signed record your customer’s reviewer can check without us.

1
Evidence review
Thirty minutes, free. We look at one workflow and the questions your customers already ask about it.
2
Proof of value
Seal on a copy of one real workflow in a few working days, ending with an evidence pack your reviewer can assess.
3
Annual licence
Priced by the workflows in scope, the retention you need, and how quickly you need an answer about a past decision.

For teams building AI for regulated industries: payments, lending, insurance and healthcare.

Book an evidence review Request sandbox access

New account.
Old approval.

Let the agent handle the invoice.
You decide the change.

Harbour PrintExample documents

A change to the payment details

Please pay €250,000.00 EUR to DE00-TEST-0000-1289.

Original approvalDE00-TEST-0000-1280

Requested accountDE00-TEST-0000-1289

The amount stays the same. The destination changes.

AgentChecking model…

What happens next?

Connect the local model to begin.

Same invoice. Different account.

Inspect evidence Tools, approvals and scope

Model tool calls

Run a workflow to inspect its actual calls.

Current approval

No workflow started.

Executor events

[]

Reference journal

This local reference key is separate from the production Seal key and ATTESTATION-v1. It does not establish who approved a change or whether every event was captured. Model traces are held in server memory.

One local SQLite ledger. Records are unsigned. No production Seal or bank connection. The local review screen does not establish real-world identity. Verifying a supplier’s account remains a separate business check.