Security

PayReality is early-stage. This page describes what's actually implemented today, in both the website and the platform, and states plainly where the current limits are. We don't hold any third-party security certification (SOC 2, ISO 27001, or otherwise), and we won't imply that we do.

Encryption in transit

This website, the PayReality platform, and its API are all served over TLS. Certificates are issued and managed by our hosting providers; nothing is served over plain HTTP in production.

Signed intents

Every action an AI agent submits to the platform is signed with an Ed25519 key generated on the agent's own side. The private key is never transmitted to us; only the public key is registered. We verify the signature against that registered key before evaluating the request. A timestamp window plus a uniqueness constraint on each request's nonce prevent a captured request from being replayed later.

Certificate rotation

An agent's signing certificate can be rotated or revoked at any time. Rotating immediately invalidates the old certificate for new requests. Because we never hold an agent's private key, a rotation generates a genuinely new keypair on the agent's side. We can flag an agent for rotation, but can't rotate its key for it. Decisions and Evidence already recorded stay valid and explainable against whichever certificate was actually active when they were created.

Signed evidence

Every Decision and its Evidence record is independently signed, separately from the intent that produced it. Each signature is checked against the specific signing key that was active at the time it was made, not just whichever key happens to be active now, so rotating the evidence signing key doesn't invalidate verification of anything signed under a previous one.

Access control

The platform enforces role-based permissions server-side (not just hidden in the interface), across six roles (Owner, Governance Administrator, Agent Administrator, Reviewer, Auditor, Executive), each with a fixed set of allowed actions.

Current limitations

We'd rather state these plainly than let you assume otherwise:

• At this stage, a single shared operator credential can act with full administrative authority across an organization, on top of the role-based permissions described above. It is not yet a scoped, per-user credential. Narrowing this is ongoing work.
• We don't currently implement encryption at rest beyond whatever our database hosting provider applies by default. There's no PayReality-specific at-rest encryption layer today.
• We don't hold SOC 2, ISO 27001, or any other formal third-party security certification.

Reporting a security issue

If you find a security issue, please tell us directly at sean@aisecurewatch.com rather than disclosing it publicly. We'll respond directly.