AI Transaction Authorization
GaelOne™ checks the payment an AI is about to send. If it no longer matches what was authorized, it stops.
Runs live against the checkpoint on this page. Nothing is pre-recorded.
Where GaelOne™ sits
The Gate
The Gate is how GaelOne™ draws the checkpoint. It is a picture of the decision, not a component in your stack.
AI agent proposes
Payment system executes
01 · AI agent
02 · GaelOne™
03 · Payment system
It proposes the payment. GaelOne™ does not run your AI and does not decide what it should buy.
It checks the amount, destination account and reference immediately before execution. ALLOW, ASK or STOP.
It moves the money, exactly as it does today — and is only ever asked to once GaelOne™ allows the payment.
GaelOne™ never moves the money. It holds no funds and replaces neither side. It answers one question, immediately before execution: is this still the payment that was approved?
Not the agent. Not the session. Not a budget. The amount, the destination account and the reference that are about to be sent — read from the transaction the payment system is about to execute, not from the proposal GaelOne™ was handed, and compared against what a person actually approved.
AI agent proposes
Payment system executes
At rest. Nothing is in flight.
Replay
ALLOW
This exact payment is authorized. The payment call is made.
ASK
This exact payment needs a person. Nothing executes until someone approves it.
STOP
This payment is not authorized. The payment call is not made.
Plate 01 The GaelOne™ Gate
Elevation · 1:1
Plate 02 One decision, recorded
Illustrative
STOP
The approval covered account •••• 8472. This payment was going to •••• 2291 — same amount, same payee, same reference, a different account. The approval does not cover it, so the payment system is never asked and $0 moves.
Press run. Every decision and every dollar below comes back from the checkpoint on this page — nothing here is pre-recorded.
Three amount bands, so a proposal has something to be measured against. They are how this demonstration is set up, not what GaelOne™ is: cases 01 and 02 are both refused with the amount sitting perfectly inside its band.
$0.00 – $250.00
ALLOW
Authorized automatically.
$250.01 – $5,000.00
ASK
A person must approve it.
Above $5,000.00
STOP
Not authorized at all.
The case that defines GaelOne™
Case 01Same amount. Same payee. Same invoice. A different account. This is what invoice redirection actually looks like, and it is the reason approving an agent is not the same thing as approving a payment.
Same invoice, same payee, same account. Only the amount moved after the approval was given, and the approval does not stretch to cover it — so the payment system is never asked.
The AI proposes $25.00 — at or under the $250.00 this demonstration authorizes without a person. Nothing has changed since, so the Gate opens and the money moves.
The AI proposes $2,500.00, which is above the $250.00 this demonstration authorizes on its own. GaelOne™ asks. The payment system tries to send it anyway and is refused — and then this one waits for you to approve it yourself.
A $25.00 payment is authorized and ready to execute. Then Emergency Stop is engaged. A stop that a small enough amount could reason past would not be a stop.
This is the shape of the record GaelOne™ creates for one decision: the payment it checked, the values it compared, the answer it gave, whether the payment call was permitted, and whether money moved. Durable, exportable, audit-grade record-keeping is not part of this proof — see what it does not include, below.
Plate 03 Authorization records
Illustrative · same invoice, one field apart
REC-01
The approved payment arrived unchanged
$2,500.00
Money moved
REC-02
A payment to another account arrived
$0
Money moved
An approval covers one exact payment, not the agent that proposed it. Change the amount, the destination account or the reference, and the approval no longer covers what is being sent.
When a person approves, GaelOne™ records the exact payment they approved — the amount, the destination account and the reference. At the execution checkpoint it reads those same three values from the transaction it is about to send, not from the proposal it was handed, and compares them. A changed amount or a changed account is a different payment, so the approval does not match it.
In-memory state, one global Emergency Stop, no expiry, no signatures, no multi-tenancy, and a simulated payment system that records what it was asked to move rather than moving it. Those are real simplifications. The check itself is not one — it runs the same implementation GaelOne™ ships to customer-side verifiers.
AI can decide. GaelOne™ decides if the money moves.
Nothing has been asked of the checkpoint in this session yet. Money moved: $0.