FAQ
Common questions
- Where is the data stored?
- Not decided yet, and we would rather say so than describe an arrangement we have not chosen. A pilot deployment is one per customer, and where it runs is part of what a pilot conversation settles.
- What we can say now is what the system holds: the payment details your integration sends, the invoice file it fetched, the decisions your reviewers made, and the signed records. It holds no funds and connects to no bank.
- What does a pilot actually involve?
- Sixty days. You point a gated tool at the SDK, we run a deployment for you, and your reviewers use the console. A pilot is scoped so the exposure is acceptable to you: shadow mode, where an approval moves no money and payments carry on through your existing process; a test account; or a payment ceiling enforced by your payment system.
- You supply the reviewers and the invoice data the comparison is made against. We do not review your payments.
- How is this different from an approval step in Slack or our ERP?
- An approval step records that somebody clicked. This records what they were shown: the record is signed over a fingerprint of the payment and a fingerprint of the exact invoice file that was put in front of the reviewer, so a later argument about which version of an invoice was on screen is settled by comparing fingerprints rather than by memory.
- Two other differences matter in practice. The checks that had to pass are part of the signed record rather than a separate audit log, and anyone can verify a record without us — including after a dispute has started, and without asking us for anything but the public key you already kept.
- Why do the package names say signetgate?
- Signetry is the company; SignetGate is the product your agent integrates with, and the name in every signed record. The letterhead and the imports are naming two different things.
- The names an integration depends on are frozen, whatever the company is called: the package names, the environment variables, the key endpoint and the error codes stay signetgate. Renaming them would be a breaking change to every deployment for a cosmetic reason, and it would also change what your existing records refer to.
- What happens to our evidence if you disappear?
- The records stay verifiable. They are signed with Ed25519 over a form anyone can reproduce, and the checker is a single page that works offline against a public key. Keep your own copy of that key and of your records from the day you start, and neither depends on us existing.
- The one thing that would be lost is the service itself: new payments would no longer be gated. That is a continuity question for the agreement, not a cryptographic one.