Protocol Hub / FHP · 1.0

Fiduciary Handshake Protocol

Establishes trust between brand, agent, and settlement rail.

Abstract

FHP enforces fiduciary obligations at the moment of autonomous purchase. It defines the handshake process that authenticates an agent's authorization to spend on behalf of a human user.

1. Purpose and Establishment of Trust

The Fiduciary Handshake Protocol (FHP) establishes the foundational trust parameters between the merchant, the autonomous agent, and the settlement rail. FHP strictly enforces fiduciary obligations at the exact moment of autonomous purchase, defining the handshake sequence that authenticates an agent's authorization to spend capital on behalf of a human user.

2. The Cryptographic Handshake Mechanism

FHP operates as a secure, bi-directional handshake mechanism executed prior to the commit phase of any transaction. It requires the autonomous agent to present a cryptographically signed verifiable credential proving its identity, session validity, and the explicit consent policies attached to its current operation.

3. Fiduciary Boundaries & Spending Limits

A core function of FHP is the enforcement of user-defined constraints. FHP interrogates the agent's payload to verify that the proposed transaction falls within the established spending limits, category restrictions, and temporal authorization windows. Transactions exceeding these boundaries are automatically rejected with a specific FHP error code.

4. Liability and Indemnification

By establishing clear fiduciary boundaries, FHP protects both the merchant platform and the end-user. Merchants are indemnified against chargebacks originating from "rogue agent" behavior, provided the FHP handshake was fully validated. Conversely, users are protected against agent overspending, as FHP acts as a hard gatekeeper enforcing their pre-set financial parameters.

5. Audit Trails and Compliance

Every successful FHP handshake generates an immutable audit receipt containing the agent's signature, the merchant's acknowledgment, and the timestamp of authorization. This audit trail is retained in accordance with financial compliance regulations and is accessible for dispute resolution or user review.