§ 01 · PAPHWEY · KNOW YOUR AGENT

The trust layer for software that acts on your behalf.

Paphwey lets a person grant an AI agent scoped access to their identity wallet — so the agent can complete a business challenge under authority the enterprise can rely on.

W3C DID SD-JWT VC OIDC4VP MCP Extends KYC / KYB
§ 02 · Four actors · One verifiable outcome Topology
SIGNS WITH SCOPED DELEGATION PRESENTS PROOF User ROOT OF TRUST Wallet device APPROVAL KEY AI agent SCOPED KEY Business RELYING PARTY ONE VERIFIABLE OUTCOME

Four actors. Four keys. One cryptographic chain from user consent to a result the business can act on.

§ 03 · How it works Four steps

The model

From quiet permission to a business outcome.

Four steps take a user from wallet consent to a result an enterprise can rely on.

  1. 01

    Identity wallet

    The user holds trusted identity and approval capability on their own device — not in the agent, not in the app.

  2. 02

    Authorize agent

    The user grants the AI agent scoped permission to use the wallet for a specific purpose or challenge.

  3. 03

    Agent acts

    The agent uses the approved access to complete onboarding, approvals, step-up checks, or other business actions.

  4. 04

    Trusted outcome

    The business receives a verifiable result with strong confidence around who approved the action and what the agent was allowed to do.

KYA extends KYC

KYC verifies the human.

Know Your Customer answers a one-time question: is this person real, and are they who they claim to be? It lives in your regulated vendor — Onfido, Persona, or whichever provider already holds the signal. Paphwey does not replace that work, and we are not a KYC vendor. We consume the KYC outcome your provider already produces.

KYA extends KYC

KYA verifies and constrains the agent.

Know Your Agent answers the per-action question: under what authority is this Non-Human Identity (NHI) acting, and is the action inside the user's delegation? Paphwey binds the agent to a scoped, revocable credential and emits a signed attestation the relying party can rely on — next to, not instead of, the KYC signal.

Built on standards

Your regulators already trust this stack.

  • W3CVerifiable Credentials · VC Data Model 2.0
  • IETFOAuth 2.1 · SD-JWT VC · RFC 9700
  • OIDFOIDC4VCI · OIDC4VP
  • EUPSD2 · Strong Customer Authentication
  • NISTSP 800-63 · Digital Identity
  • MCPModel Context Protocol
End-to-end latency < 2 seconds · Shipped · Production · v1
§ 04 · See it live Four stories

Live demos

The flow, told three different ways.

Next step

Give your agents authority your business can actually rely on.