SafeGate v5.4.1 / API Key Lifecycle Freeze / Public Review

Merchant API Key Lifecycle Freeze Index

This page freezes the current merchant API key lifecycle mock before SafeGate moves into the next merchant integration stage.

SafeGate principle:
Payment is the trigger. Trust is the product.

Boundary: This is a public freeze index. It is not a production API key system, not a production public API, does not expose real API keys, does not expose backend secrets, and does not claim Pi Mainnet settlement proof.

1. Frozen Lifecycle Page

v5.4 Merchant API Key Lifecycle Mock

Public mock for merchant API key lifecycle: create, activate, rotate, revoke, rate limit simulation, key preview only, and audit boundary.

Open v5.4 Merchant API Key Lifecycle Mock →

2. Frozen Lifecycle Scope

{
  "frozenStage": "v5.4.1",
  "lifecyclePage": "/merchant-api-key-lifecycle-mock.html",
  "scope": [
    "Merchant ID input",
    "Environment selector",
    "Create Mock API Key",
    "Activate",
    "Rotate",
    "Revoke",
    "Simulate Rate Limit",
    "Key preview only",
    "No raw key exposure",
    "Merchant/API-key scoped rate limit",
    "Lifecycle audit events"
  ],
  "productionApiKeySystemClaim": false,
  "productionPublicApiClaim": false,
  "realApiKeyExposure": false,
  "backendSecretExposure": false,
  "piMainnetSettlementProofClaim": false,
  "currentEvidence": "Pi Testnet controlled post-payment trust flow",
  "nextStage": "v5.5 Merchant Integration Request Mock"
}

3. Confirmed Lifecycle Behavior

MERCHANT_API_KEY_CREATED returns ok:true.
MERCHANT_API_KEY_ACTIVATED returns ok:true.
MERCHANT_API_KEY_ROTATED returns ok:true.
MERCHANT_API_KEY_RATE_LIMITED returns ok:false with statusCode 429 by design.
MERCHANT_API_KEY_REVOKED returns ok:true.

4. Frozen Security Rules

No real API key is created or exposed.
No backend secret, service role, access token, or wallet passphrase is exposed.
Only key preview is shown in public mock responses.
Future production should store only hashed or derived key material server-side.
Rate limiting should be scoped by merchant and key, not only by IP.
Revoked or rotated keys must fail closed in future production design.
Lifecycle changes should generate durable audit events.

5. Why This Freeze Matters

SafeGate now shows a complete public path from payment evidence to receipt verification, API contract, merchant console, and merchant authentication lifecycle design.

Reviewer takeaway: SafeGate is not exposing secrets or claiming production API readiness. It is showing the architecture path required for future safe merchant integration.