Let Horos pay one of your invoices
Ten minutes of your time, two of them a phone call. It runs on Arc testnet, so the money is test money and nothing you do here can move anything real. What we are testing is whether the refusal is useful to you.
The short version is in ONBOARDING.md. This page is the same thing, and it is the one to send on.
Start here
The whole intake is three lines, and the link writes them for you: kiter2509@gmail.com.
No account, no integration, and no access to anything of yours. If you would rather watch it refuse something first, the two links at the bottom of this page need nothing from you at all.
What we are asking
Pay one real invoice — one you would otherwise pay by bank transfer — and tell us what the refusal felt like when we engineer one on purpose. No bank credentials, no ledger access, no integration.
What you get
A refusal you can point at. Most businesses have a policy that says "phone to confirm". That works right up until the email arrives with a voice note that sounds like your supplier. Horos has no policy to talk itself out of: it runs against a contract that cannot be told to pay a new address.
A public record of who you have paid. Every counterparty gets a page listing every account they have ever been paid at and the signatures behind each change. Send it to your accountant; so can anyone else.
The three steps
-
Tell us the vendor
Their name as it appears on invoices, the address you pay them at, and roughly what a typical invoice is for. That is the whole intake.
-
We register them, and the agent pays the first invoice
The first payment establishes the record, and it is the only one that is a real judgement call — from the second onward there is something to compare against.
You get a link to their public page and a decision card showing what the agent read off the invoice and why it decided what it did.
-
We engineer the attack, and you watch it refuse
This is the part worth your ten minutes. An invoice arrives from your vendor that looks right, reads right, and asks to be paid somewhere new — with the old account printed for credibility, urgency, and a request not to confirm.
The agent refuses it, and shows you which sentence gave it away.
See it before you decide
Neither of these needs an account.
The decision card, with three sample invoices that resolve to release, refuse, refuse.
A counterparty record, after a supplier genuinely changed accounts — two signatures, neither of them the recipient's.
kiter2509@gmail.com · Source · MIT
What we will ask you afterwards
Whether the refusal was legible. Whether you would have wanted it to escalate to you instead of refusing outright. Whether anything it flagged was actually fine — a control that cries wolf gets switched off, and then it protects nobody, so that answer matters more to us than the flattering one.