Consortium AISign in

Product

Frequently asked questions

What exactly does the confidence gate check?

Every critical field of an extracted invoice (supplier, buyer, amount, currency, date, and so on) carries its own confidence score. Each score must meet or exceed your node's threshold. A missing score counts as 0.0 and fails. The overall extraction confidence is never consulted — a high overall score can never mask one weak field. All failing fields are reported, not just the first.

What data leaves my bank's node?

Identifying fields (names, addresses, references) leave the node only as SHA-256 hashes. Amount, currency, and date pass through in clear so the consortium can score risk across banks. Nothing is shared at all until a transaction passes the gate or is approved by a reviewer.

Who can approve or reject a queued transaction?

Only a registered, active reviewer. Decisions by unregistered or deactivated reviewers are refused and the item stays queued. Reviewers can be given their own logins — then decisions in their name are only accepted from their own signed-in account. Every decision is attributed and recorded in an append-only audit trail, including whether the identity was authenticated by a login.

Can the AI extraction model auto-approve a transaction?

No. Document text entering the model is delimited and treated strictly as data, with hard length caps. The model's output is defensively normalized and then re-gated by the same fail-safe gate as manual input. The model has no path to grant approval.

What happens if the consortium submission fails?

The transaction is persisted in a SUBMISSION_FAILED state before the error is surfaced, and can be retried. Nothing is silently dropped.

What is in the Free plan?

Manual transaction gating, the review queue, reviewer accounts, and the audit trail. Pro adds AI document extraction and higher daily limits — see Pricing.

Is this a shared database of customer data?

No. Each bank runs its own node and its own database. The consortium sees hashed identifiers and clear risk-scoring fields only. There is no central store of customer identities.

Something not covered here? Contact us.