Invoices your agents can actually pay.

The agent pays your routine supplier invoices. Anything that changes where money goes is held for two approvers who are provably different people — approving exactly what was requested, unchanged.

Built at ETHGlobal Lisbon 2026 · World · Hedera · 0G

app.invoiceguard.io/overview
Paid by agent990
Held for approval2
Settled volume€142,380
Human minutes0
Invoice Supplier Amount Status Handled by
INV-2026-0916 Águas do Sado €312.40 Paid Agent — no review needed
INV-2026-0915 EDP Comercial €1,840.06 Paid Agent — no review needed
INV-2026-0912 Padel Surfaces Lda €25,000.00 Held Bank account changed — 2 distinct approvers required
INV-2026-0914 CleanCourt Serviços €960.00 Paid Agent — no review needed
INV-2026-0910 Sport Import Iberia €4,118.75 Held First payment to this supplier — 2 approvers required
INV-2026-0913 NovaRede Telecom €214.90 Paid Agent — no review needed

How it works

Most invoices never needed a person. A few always will.

Today a human checks all one thousand, because the control cannot tell the difference. Remit routes each invoice from the payment identifier itself.

01 / FREEZE

Every invoice becomes an exact request

Supplier, bank account, amount, reference and expiry are locked into a single identifier. Change any detail later and it is a different request — every approval already given no longer applies.

02 / ROUTE

Routine invoices are paid by the agent

Known supplier, unchanged account, amount inside your limit: the agent settles it on Hedera and records the receipt. Nobody on your team is interrupted.

03 / HOLD

Risky changes wait for two real people

A new bank account, a first-time supplier, an unusual amount: held until two approvers who are provably different people — not two logins — approve exactly what was requested.

Refusals

The product is what it refuses.

These are not alerts for someone to review later. They are payments that cannot happen, by construction.

One character of the bank account is altered after approval Blocked A changed detail is a different request. The approvals given no longer apply to it, so nothing authorised exists to pay.
One person approves twice, from two different agents Counted once Approvers are verified as distinct people through World, not distinct accounts. Two approvals from one person never make a quorum of two.
An already-settled payment is submitted again Blocked Each request settles exactly once; the payable token is burned on Hedera at settlement. A duplicate cannot be paid, even with valid approvals.

Stack

Remove any layer and it stops working.

World

Proves two approvers are two people. AgentBook links each approving agent to a real, unique human — anonymously. Without it, dual approval only ever meant two accounts clicked a button.

Hedera

Moves the money, exactly once. The agent pays for verification and settles on Hedera with a public receipt; the payable token burns at settlement, so double payment is impossible on the ledger.

0G

Proves what the invoice said. Extraction runs in attested compute and the result binds to the request — you can prove which figures were approved and that nothing altered them in between.

What we don't claim

Remit guarantees the integrity of the approval and payment path. It does not claim to verify:

  • that an invoice is genuine, or that a supplier owns a bank account;
  • that an approver is honest, or that a verification service is truthful;
  • that a payment is legally or fiscally compliant.

Being precise about this boundary is why the guarantees inside it hold.